it's not primarly the matter of running the regression-suite before
QA approval but to have a small set of meaningful regression tests
available ?
The problem with such tests not being mandatory is that, sooner or
later, some tests would break. That again would lead to a state where
the user of the tests could not be sure whether a broken test-case
means that he introduced a bug or whether he just encountered an old
problem that broke the test-cases before. He would have to start a
tedious search to find out the cause of the problem - just like the
testers have to do nowadays. And then people would simply not use the
tests because the efforts are too high...
I still think that making a test mandatory is not the first step in the
process. I would like to name these requirements with this priorities:
1. Test should be repoducible and generate easy to read and unambigious
logs with clear error codes.
2. Test should be run within approx. 1 hour.
3. Test should cover 20% of the functionality of each application
(typically used function)
4. Test should be mandatory.
IMHO we don't need to care about 2.) if we know that we cannot address 1.)
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
