Hi there!
Jörg Jahnke wrote:
Hi Hennes,
Hennes Rohling schrieb:
...
But don't make everything mandatory. If I change a string in the setup
or change platform dependend code for systemintegration I don't want
to do a mandatory test that tests whether all dialogs in the Calc
still work.
- Hennes
The problem with not having the tests mandatory is that this will lead
to regressions being found only on the MWS where the tests are also run.
There the cost for hunting down the root cause of the failed test is
much higher than on the CWS.
But I agree that there are cases where a full set of regression test is
not necessary. I am quite confident that the OOo developers are able to
decide when they can make an exception.
Regards,
Well I also think it´s save to apply common sense here and have the
option to not run the tests if the CWS for example did only introduce
minor changes in the build environment or did only change some strings
etc. where it´s just unlikely that these changes would introduce a
regression.
For the not needing to test Calc dialogs if the CWS did only change code
in Writer and similar problems what about the following idea:
Analyse code coverage of each and every test and than compare to modules
added to the CWS and than when running the tests automatically just run
those which cover modules added to the CWS? We would just need a table
in some database somewhere where individual tests are assigned to a list
of modules to be able to automate something like this.
Jörg
Kind regards,
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
