Automated testing of branch OOO320 up to release

With availability of Milestone m1 on branch OOO320 (OpenOffice.org 3.2) automation team - as always on a way to a release - starts to test each milestone based on a matrix.
Autotests were made more stable in the past weeks and are now prepared to run 'Greenstate' for this release. In case of errors found by test scripts beginning with m1 they have to be close analyzed as they may be failures in OpenOffice.org. Please contact script owners if an error was found and you need help to analyze. For all potential errors in test scripts a CWS will be created to fix them and have fixes available in following milestone. Of course main goal is to assure OpenOffice.org remains free of issues for QA automation purposes.
All results of automated tests are collected in QUASTe[1] and are available to everyone to see what has been tested. An overview of what should be tested one can take a look on the matrix[2]

English installsets are tested with automated tests of category 0 by SUN automation team[3] with tests of Category 1-3[4] by module owners[3] on selected platforms and languages.

All community members are invited to run automated tests on platforms and languages of their choice. This should be tests of category 0 at first. See matrix what selection fits best to you.

If you have any questions please contact dev@qa.openoffice.org or responsible testers.

Thanks for your support.

1 http://quaste.services.openoffice.org

2 http://wiki.services.openoffice.org/wiki/OOoAutomationReleaseTestMatrix

3 http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationResp.html

4 Category tests

tags: automated_tests qa