Hi Thorsten, Issues for automated tests are from now on handled the same way like all other issues and if an autotest breaks in a CWS it is a must to fix it within this CWS with the same policies. CWS must be set to 'new' then and after fixing again to 'ready for QA'. Currently you don't have to run autotests prior to state 'ready for QA' but if you are not sure if your changes might break an autotest it is a good idea to get a script developer involved (responsibilities are named in my blog). Of course there are tests required to run/pass on each CWS (currently done by QA) known as release ore 'Category 0' tests. These are basic tests ( open and close all known dialogs) without any deeper functional testing. However you might run these tests by yourself and it is of course acceptable to fix these tests if required. It is possible to upload results of automated tests to 'Quality Assurance Statuspage' aka QUASTe for documentation. See wiki-pages for more info if needed: http://wiki.services.openoffice.org/wiki/QUASTe
A list of tests required running on a CWS based on a specific milestone can be found here: http://quaste.services.openoffice.org/index.php?option=com_quaste&task=tests_overview As I said 'Cat 0' tests are required running. CWS policies will be updated soon.... Hope this helps! Best Regards Helge Am 09.10.08 15:01, Thorsten Behrens schrieb: > Hi Helge, fellow devs, > > reading this > > http://blogs.sun.com/GullFOSS/entry/fixing_or_adapting_automated_tests > > I think the rules (and maybe the hurdles) for CWS have changed > substantially, but I cannot seem to find > > http://wiki.services.openoffice.org/wiki/CWS_Policies > > updated - so, as a dev, what _specifically_ do I have to do for my > CWS now? Run all automated tests after every code change, to notice > if they break (or are the tinderboxen running autotests)? Run them > all prior to setting Ready for QA state, and calling in a test writer > only then? Is it acceptable if I fix the tests myself? Is there a > list of tests that _must_ pass, and what kind of functionality do > they cover? > > (this http://blogs.sun.com/GullFOSS/entry/test_code_on_it_s list > might contain a few answers, but is IMO still far away from an > executable "do this, do that, then done" explanation) > > Sorry for being ignorant, > > -- Thorsten -- =============================================================== Sun Microsystems GmbH Helge Delfs Nagelsweg 55 Quality Assurance Engineer 20097 Hamburg OOo Team Lead Automation http://qa.openoffice.org mailto:[EMAIL PROTECTED] http://wiki.services.openoffice.org/wiki/User:Hde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
