Hi Stefan, in the hope of not hijacking the thread too much ...
> Summarized: > Autotests are our best weapon against regressions. > But only if the right ones get written and run. And if - they are reliable and reproducible - run in reasonable time Please allow me my slight doubts that all of our autotest-frameworks (and we have at least 5: cwscheckapi, complex test cases, testtool, performance tests, confwatch tests) fulfill both requirements. (And yes, some of them don't even fulfill the "they're run" requirement you named.) If we all agree that auto tests are highly useful, and an important line of defense against bugs creeping into a release branch, then I wonder why we invest so little resources into making our QA frameworks fulfill those 3 basic and essential requirements. I'd *love* to see that changed. Heck, I'm a developer, writing tests is as boring as anything :), but it could even be *fun* writing UI tests (like currently done with testtool scripts) if it would happen in Java, with a decent IDE ... Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
