Hi Bernd,
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.
We tried it for some month this year, but it seams to be impossible with the complex code of OOo. When you start OpenOffice.org and open one document, nearly 80% of all libraries are touched and the results we collected with some tooling (I do not know what was used) on code lines wasn't very useful. So we stopped this project. So we think a full automated mechanism on code base isn't possible. But based on modules can help. But then the complexity of the OOo is still there, and do you know somebody who know all dependencies? ;-) So our idea is to identify test cases for features. E.g. group all test cases which are testing OLE objects, group other tests which test tables in Writer. Then the tooling should give the possibility to select such groups. Thorsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
