QUASTe

From Apache OpenOffice Wiki
Revision as of 10:08, 18 February 2008 by Hde (Talk | contribs)

Jump to: navigation, search

- Page under construction -


- QUASTe FAQ -


FAQ for QUASTe.


What is "QUASTe" ?

QUASTe is the abbreviation for 'Quality Assurance Statuspage'. The word 'Quaste' is german for 'tassle' so this name found out to be adequate as here 'all strings run together'. (See entry on Wikipedia about 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

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?

xyz


Warnlogs?

xyz


Where can i get some information about QA Errorslogs?

xyz


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

What is the meaning of VTTDI?

xyz


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

Personal tools