From Apache OpenOffice Wiki
Jump to: navigation, search



What is '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. QUASTe has been developed by Helge Delfs in programming language PHP consisting of components and modules for the OpenSource Content-Management-System Joomla

What means 'QUASTe' ?

QUASTe is the abbreviation for 'Quality Assurance Statuspage'. but the word 'Quaste' as a meaning is german for 'tassel' so this name found out to be adequate as here 'all strings run together'. (See entry on Wikipedia about Quaste or tassel).

What license 'QUASTe' uses ?

As QUASTe Modules and Components are written for Joomla CMS they will be available for download under GPL License soon.


There is a chat channel available where you can get support for QUASTe or to discuss features or bugs.
Server: irc.freenode.net
Channel: #quaste.openoffice.org

For QA-Represenative

How to submit CWS's quality status to EIS

Normally if all required autotests created by VCLTesttool are finished and the results added QUASTe it then will sent its allover status (green or red) to EIS application. If it is necessary to re-run complete automated tests or parts of them for this CWS currently the status is not updated automatically in EIS. Therefor the QA-Representative must be logged in to QUASTe and has to update the status manually.

  • Login to EIS application (http://eis.services.openoffice.org)
  • follow the links to *your* CWS
  • on overview page => choose 'Tests'
  • in row 'status' click' select the link for TestName: 'AutomationCAT0'

Quaste eis link.jpg

you will then be forwarded to 'QUASTe Analyze page'

  • here the current details of automated tests compared to MWS are shown
  • check current quality status and choose if you've decided the results are 'ok' or 'failed'
  • By click on the relative button the status is submitted to EIS

Quaste eis status.jpg

The buttons (sent status 'green' or 'red' to EIS) give the possibility to overide the status in EIS or to sent a status manually if it could'nt be sent automatically due to e.g. network or other problems. Only the QA-Representative has the possibilty to submit this status (login required) that's the reason why it isn't visible to all browsing QUASTe.

For Users

Definition of "Release Test"

Release tests are those which must run on every build. These tests should finish without any failure on every build and of course on every Child workspace

Definition of "Required Test"

Required tests are those which must run on a specific build. It depends on the category model what test are required.

Definition of "Optional Test"

Optional tests are those test must not run on a specific build depending on the category model.

Errors / Warnings / QAErrorlogs

The Errorlog is generated by testtool if a general error occured. It is a possible hint to a crash, undeclared or not-found control. Errorlogs are red coloured.
A warnlog is a hint to a failure or bug occured in office. It is generated during a testrun by VCLTesttool if f.e. a feature does not work as expected by automated test. It is shown in orange color.
This is a string generated in Logfile to show specific problems like:

1. a bug has been found, issue has been written but it will not be fixed in currently tested version.

2. a reference to a condition that should be fulfiled to run test correctly. (Empty directorys in some case or a specific path or whatever)

Category model

Meanwhile there are a lot of automated tests available. With this number of tests it would last nearly 1 week to test 1 build completely. After all automated tests passed the testers have to verify the results...this will take also some time. Because of this conditions the QA Automation Team decided to create a test cycle that covers a meaningful number of tests run on each build. The outcome of this category's are 4 in numbers

  • 0 : Tests run on all builds and releases
  • 1 : Tests run on the first build (plus tests from category 0)
  • 2 : Tests run on the second build (plus tests from category 0)
  • 3 : Tests run on the third build (plus tests from category 0)

To make it easy for all involved the rules what type of test is included in what category is not strict documented. Except category 0 which holds all automated tests required for release testing (mostly resource or update-tests). For all other 3 category's it should be observed they have the approximate duration. This model shortens a test cycle for each build to a maximum of 2,5 days. A list of all automated tests and its category's can be found here => All current tests

Note: This is not to be used on release-workspaces. Those are using another matrix that can be found in the OOoAutomationReleaseTestMatrix

What is the understanding of VTTDI?

See VTTDI-Page for further details on VTTDI

How do I publish my testresults ?

Before you add some testresults created by VCLTesttool on your local machine it is a good idea to check what testresults are missing. The best way to test a specific build would be to organize testing within your team to avoid double work. If you want to know what test for what platform is missing see 'Testresults grouped by application' page.

If you aren't familiar with automated testing please visit Home of automation Team and learn more about automated testing with 'VCL Testtool'

Assuming you've downloaded a 'VCL Testtool Binary' and checked out the qatesttool-project we can start.

1. Once an automated test has been finished its extracts for creating results on QUASTe will be found in the errorlog-directory in the form of txt-files.

2. Simply put these files in a zip-Archive

3. goto QUASTe webpage

4. Log in with your OpenOffice.org username and password

5. Once logged in, you find some menu entrys on right part of QUASTe webpage

6. Click menu entry 'Upload my testresults'

7. Browse for previously created zip-file and press 'Upload' button

8. Wait.....

Once all files have been successfully added to QUASTe Database you will receive a message. If you find some error-messages please visit QUASTe-FAQ to get some help about these messages.

How do I remove testresults ?

One can only delete testresults initially created by himself but of course testresults submitted by other users can be viewed.

Hint: Currently only testresults with errors occured can be removed.

If you want to remove your testresults from QUASTe-Database you must be logged in. Once logged in goto page 'Testresults grouped by application. This page now shows 2 additional columns by comparison if not logged in. First additional column holds the username who created the testresults and the second shows a checkbox. If you now want to remove a testresult check this checkbox and click the 'red-cross-icon' at the end of the page. If you want to remove more than one testresult simply check more than 1 checkboxes and click the 'red-cross-icon' After confirmation the testresults will be removed !

Possible errors

Error while adding testresults for testplan: xyz.bas

This is either because you are owner of this autotest or you were running this autotest and there some errors while adding the testresults to QUASTe database. Take a look into the content of this mail and see if you can find out some details about this error.

There is a testrun already available

'You can only update current testrun if you restart as user: '<username>' on machine: '<machinename>

If a testrun has been finished and is written into database there are some dependencies.

  • If there is no similar testrun found the testrun will be added.
  • If there is already a similar testrun it will be updated, but:
    • only if the autotest was started on the same milestone depending on language, Machine and User. If these parameters not match the testresults will not be updated nor written to database. The tester will receive an errormail about this.

This behaviour found to be the best solution because testresults will not be overwritten by another tester. This avoids multiple testresults and saves space in database. Notice: On distributed testing one has to know what should be pass next and which test is already passed. This saves time.....

Incomplete testruns only allowed if complete previous testrun exists

Before it is possible to submit an incomplete testrun there must always exist a complete testrun in database. A complete testrun means all testcases belong to a test and checked in to QUASTe have to be run and submitted to QUASTe. Afterwards it is possible to start incomplete tests (e.g. contain only a collection of testcases) to submit changes in a test (see also There is a testrun already available). Normally QUASTe recognizes if a testcase has been renamed or removed from a test but in some cases the developer of a test has to fix changes via QUASTe-Backend. If you encounter problems with a test please contact the owner of a test.

Testcase: XYZ not found in resultfile but in database

This message could have different reasons, but it is easy to fix. If you have this testcase enabled for multiple autotests and f.E. excluded for this autotest you must 'disable' this testcase for this autotest in 'QUASTe Autotest-Mananger'. See 'How to disable testcases or tests for a specific Masterworkspace' (to be done) The other case could be that this testcase isn't called by bas-file. See if this testcase is excluded either in bas-file or in inc-file. If so and this testcase isn't needed anymore you have to remove this testcase from includefile and run 'Update test information' in 'QUASTe Autotest-Manager': How to update autotest information in QUASTe' (to be done) If you are not registered to QUASTe or you are not the owner of the file please contact file owner to commit these changes.

No valid mail-address or machine-name found

If you're starting automated tests and want them to be added to QUASTe it is required that you submit the name of the testing machine and a valid mail-address. Both are part of the testtool.ini (on unix .testtoolrc) Please check your testtool.ini (found in your home-directory) if the following entrys are filled with details:




ReturnAddress={valid mail-address}

If these values not exist it is mandatory to create them.

Hint: If you don't want to re-run your tests you can edit the result-extracts (.txt-files) in your errorlog-directory and add your details to the following lines:


username={valid mail-address} => normally your Openoffice mail-address (username@openoffice.org)

Simply re-zip the changed files and upload again !

QA-Representative: If you want to update previous testresults please click link 'Retry'

You will receive this email if you are going to add some testresults to QUASTe database if there are previous testresults already. This previous testresults will not be updated automatically by QUASTe if they were added by some other tester. However in this mail you receive is a link that leads you to a webpage were those results are listed in detail and you as a QA-representative can decide if previous results shall be updated with you data or should be leaved in the database.

No testcases found for testplan. Please contact script owner.

This email will be sent by QUASTe if there is a resultfile that seems to contain a full testrun but there are no testcases found for this autotest in QUASTe-database. Possibly it is a severe problem in original autotest-file. Please contact the owner of the script to investigate this problem. A list of responsibilities for testscripts can be found here.

Test Cases Specification (TCS), Test Cases (TC) and TCS Tool

QUASTe also hosts the test cases specifications database.

To learn more about how to create, edit and find test cases, please read the QUASTEe TCS Tool Tutorial.

See also:

Helpful links

- the homepage of the QA project on OOo : http://qa.openoffice.org
- the mailing list of the QA project : http://qa.openoffice.org/servlets/SummarizeList?listName=dev
- query for existing bugs in IssueTracker : http://qa.openoffice.org/issues/query.cgi
- writing a new issue in IssueTracker : http://qa.openoffice.org/issue_handling/pre_submission.html
- the QA category on OOo wiki : Quality Assurance

Known issues

- Errormails about existing testresults send to CWS-Owner
If current tested Workspace is as CWS and someone wants to add results to database for a test that already exists the CWS Owner gets a mail in which he can decide whether testresults are updated or not !

- Possibility to compare results of cws/cws
It should be possible to compare testresults of 2 CWS'se like comparing of MWS and CWS testresults.

- Response-file for automated script update
If sourcetree is updated automatically there should be a response file created telling if there were errors or not !

- Handle testcase specifications
QUASTe should be able to handle Testcase specifications. Generating, viewing, editing of testcase specifications and evaluating of testresults should be possible

Personal tools
In other languages