Mathias Bauer wrote:
[...] Anything else would be insane. I took that for granted. But I also want to believe that running several hours of tests for e.g. automatic styles would be worth the effort. This is a good example where I suspect that possible regressions would stay unnoticed by automatic GUI testing. But of course that's open for debate. And exactly this debate is what I want to see happening. So let's wait until the proposed test cases are published and until we have verified that they run reliably. Then the QA and development engineers of the different teams can investigate them and decide if they make sense or if we can create other tests that serve the desited purpose better. *Then* we can decide whether we wanted to run the tests more frequently or even make them mandatory.
Yes, that seems the way to go. Improve test tool and test cases, and in a kind of pilot phase test them on a subset of childworkspaces. Do those test not only by QA automaters, do it in teams of QA and developers. When by those tests you get the feeling (or 'evidence') that they are really helpfull, come here again anad let's discuss whether and how to make it mandatory for everyone.
Rüdiger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
