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....