Frank Schönheit - Sun Microsystems Germany pisze:
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 ...
Heh, if that IDE would somehow fit with JUnit, then even non-core
developers could start contributing tests... But I'm pretty pessimistic
about it, as it's barely possible to test Swing UIs with Java right now.
Having such a UI framework, similar enough to JUnit, would be just
great. You could even start creating some tests in prototyping phase
based on specification.
Just dreaming.
Regards
Marcin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
