QUASTe - Quality Assurance Statuspage

Main Menu

Home
Help

MWS testresults

CWS testresults

Testcase Specifications

List Testcase Specifications Create Testcase Specification

Autotests

Autotests overview
Home
Welcome to QUASTe

Welcome to Quality Assurance Statuspage - QUASTe

QUASTe is collecting, validating and comparing all testresults created by VCL-Testtool while testing OpenOffice.org builds and creates easy to read resultspages. Everyone interested in quality of a specific build of OpenOffice.org has the ability to check the results of automated and of course manual tests.
If you are familiar in running/writing automated tests you should create an account in QUASTe to administrate your tests or upload testresults of your personal testruns of a specific build.
If you want to learn more about QUASTe and how it works you'll find a QUASTe-FAQ in Wiki

If you want to join the QA-Team and help the community of OOo you may visit the Quality Assurance pages

For a quickstart please choose on the left side if you either want to view testresults of a CWS (Childworkspace) or an MWS (Masterworkspace). Simply select an entry from the list.

 
 
Friday Feature No. 10

Today 'Friday Feature' #10 is announced. Again with this update some changes and several fixes come along.

CHG: CWS owner can update testresults
Now if tests are run by the CWS owner (identified by it's mail address) existing testresults can be updated by 'em. Even if they were not started by himself. This was already possible by QA-Representative now also by CWS-Owner.


CHG: Incomplete testresults are allowed to update a complete testrun if made by same user on different machine.
If incomplete testresults are added to QUASTe (derived from 2nd testrun for validation f.e.) and a previous testrun already exists ( depending on minor, language, platform and user ) previous testresults can be updated even if testresults came from another machine but from the same user


CHG: QA-Rep is able to add an issue id to a testcase found by testtool on analyze page:
On a CWS if you're checking the 'Analyze page' for different errors compared to an MWS you now have the possibility to add an issue id to the testcase failed on CWS. This is to document issues in testcases. If an error is occured on MWS and testcase holds an issue id it is not editable on CWS page.


CHG: Known issues can be added to testcases on MWS overview for easier analyzing.
One now has the possibility to add known issues to warn- or errorlogs to testcases in MWS view

FIX: There was an issue in showing the test durations on overview pages.

Further on some minor fixes.

 

Have fun with this new update !

 

 
 
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 This e-mail address is being protected from spam bots, you need JavaScript enabled to view it or responsible testers.

Thanks for your support.