With availability of milestone and RC OOO310m11 as previously announced all automated tests (Cat0-3) will be started

With availability of Milestone m4 on branch OOO300 (OpenOffice.org 3.0) automation team - as always on a way to a release - starts to test each milestone based on a matrix.
In the past 2 weeks automation team was employed with fixing all their automated tests and with integration of CWS 'greenstatever2' we expect to have most of automated tests with non-failure results. In case of errors found by test scripts beginning with m4 they have to be close analyzed as they may be failures in OpenOffice.org. Please contact script owners if an error was found. For all potential errors in test scripts a CWS will be created to fix them and have fixes available in following milestone.
All results of automated tests are collected in QUASTe ¹ 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 ²

The way of testing available builds has been modified a little against previous releases.
English and German installsets are tested with automated tests of category 0 (English version by MWS testers ³, German version by German community members) while other languages are tested with tests of Category 1-3 ⁴ by module owners ⁵ 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.

But the great success on testing a release branch this time: QA members of the german community are running required automated release tests continuous on each milestone starting with m1. Once the tests are finished they will upload their results to QUASTe to share it. This was made possible due to close collaboration with QA-Automation-team and OpenOffice.org Community members. A big applause.....

It is done and the first public beta of QUASTe has been released and is now available for all interested in quality-status of OpenOffice.org Builds.

It has been found out it was too optimistic to launch it in February as announced in my previous blog. There was still a lot of work to do to get this done. Gerd Weiss from Local IT and Bernd Eilers from Tooling gave big support to help bringing the server finally to work and here we are :-)

Please read Wiki pages related to QUASTe to understand how it works (see links below)

First steps:
http://wiki.services.openoffice.org/wiki/QUASTe_-_First_steps

FAQ:
http://wiki.services.openoffice.org/wiki/QUASTe

QUASTe-Home:
http://quaste.services.openoffice.org

All pages are currently still under development and may be incomplete or have issues. If you find some issues please add them to list of known issues found here:
http://wiki.services.openoffice.org/wiki/QUASTe#Known_issues

If you have questions you can of course contact me directly or visit the QUASTe-channel on IRC with the following address:

Server: irc.freenode.net
Channel: #quaste.openoffice.org

Have fun !

Some might have heard about the 'Statuspages' we use here at Sun Engineering. On OpenOffice.org Conference 2007 in Barcelona 'Joerg Sievers' and me had a workshop where a short overview of these pages were shown. Some time ago it was announced on dev@qa.openoffice.org also, that it was decided to make this tool available on OpenOffice.org.

The history

When I started working at Sun Engineering I already worked for more than 10 years as a QA-Engineer in industry. Documentation of test- and measuring results was taken for granted but as I begun to start automated testing at Sun - at the end of a day I had these huge amount of testresults. I was asking me how to evaluate these most efficient and provide me, my colleagues and managers a quick valuable overview of these results. It should be possible to archive these results and recall them whenever I wanted. The resultfile-output from testtool was not valuable to get this done and so the idea of 'Statuspage' was born. The 'Statuspage' should give an opportunity to get an easy overview about the results of automated tests running on a specific Office-Version depending on the Build-ID, platform and language. Easy access to number of completed tests, due tests and links to documentation of all tests specified for any application. All these results should have been collected from testtool resultfiles and send to 'Statuspages' automatically. First draft was a simple html-page with a huge table that showed all tests on all platform in all languages.

Illustration 1: first draft in 2002

Meanwhile (5 years later) these pages are a big database-driven project with 1000's of lines of code. And currently this project here at Sun Engineering is accepted as a helpful tool for daily work.

The plan

More than once announced I'm working on a release to have it on OpenOffice.org available. Still working hard to get this done and hopefully finally announced at the end of February. It's quite a lot of work for me to do and I hope this date can be held.

The status

Due to some severe issues I was thrown back some time but currently I have the most features implemented and working on the final Features and issues. I decided to rename this project from Statuspage to QUASTe (Quality Assurance Statuspage) to have a cool name for this :-) (Quaste is german for 'tassle' so I found this name adequate as here 'all strings run together')

The features

Here is a first list of features in QUASTe (incomplete for sure):

• Overview what tests shall run on a specific build / release

• Overview of testresults created by automated tests grouped by platform / language / category up to detailed view of a testcase

• Separate overview of results created in Childworkspaces (CWS)

• Compare testresults of Master-Workspaces (MWS) and CWS to avoid regression

• creating and managing of 'test case specifications'

• Documentation of automated tests and 'test case specifications'

Stay tuned for QUASTe....