Hi Thorsten, Thorsten Ziehm wrote:
as you are directly answering to me I assume that your mail should also address me but you completely missed my point. Though my hope was that I had made my standpoint clear it seems that I failed to do so. I hope I get it through this time. I don't want to continue this discussion but I want to be quoted correctly. > most of you want to find regressions in less than an hour. These tooling > doesn't exists for a complex program like OpenOffice.org. Christoph > wrote that all API-tests will run more than 4 hours. And API testing is > one of the quickest tests which exists. I don't want to find all regression in less than one hour, you should read the mails you reply to more carefully. Especially in my last mail I pointed out in a very detailed manner what I'm still missing. So again: I want to get a good compromise between effort (hours to run) and result (coverage of code that is known to be prone to regressions). So before I can agree to any regression testing I must know if this testing really investigates the parts of the code that are known to be prone to regressions. This has to been proven for the tests you seem to suggest. I have not made up my mind about how long I think would be bearable - but that isn't necessary anyway until it is shown that the suggested tests qualify for regression testing in the way described above. I think it was Marting who talked about "one hour" but I think this is an exaggeration. I have my hopes that it can be a small number of hours in most cases though and that we don't make any test mandatory for all CWS (as that would be exaggerated also). Also again: I don't want to execute just a bunch of arbitrary test cases just because they are the only ones we have that run reliably (that's a condition sine qua non for me) and that test "main functionality" and resource files and the like(*). I want to have tests that test the "dark areas". Yes, and indeed these tests shouldn't run for ages. But if I was convinced that the tests investigate what we need I wouldn't complain about one hour more or less. And also again: let's stop this discussion (and especially allegations obviously caused by misunderstandings) until we have got information about what the tests cover exactly and if this is what we want. Ciao, Mathias (*) testing resource file integrity, file formats etc. (everything that does not need interactivity) is something that much better and much faster could be tested by code, not by a GUI test tool. But resource file integrity and the like should be tested on the master. -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
