Difference between revisions of "NLC/localizedQA"
(wiki link) |
(Info about Scenario and issue template for approval) |
||
| Line 1: | Line 1: | ||
| + | [[Category:Quality Assurance]] | ||
| + | |||
'''Testing your localized builds''' | '''Testing your localized builds''' | ||
| Line 8: | Line 10: | ||
The testing is required if you want the localized builds to be distributed on OpenOffice.org mirrors worldwide. The workflow is as follows: | The testing is required if you want the localized builds to be distributed on OpenOffice.org mirrors worldwide. The workflow is as follows: | ||
| − | * The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. | + | * The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. (At least the "Release Sanity" scenario should be assigned once per platform). |
* The testers make the tests, and enter the results in the TCM. | * The testers make the tests, and enter the results in the TCM. | ||
* The lead enters the status of the testing to the [http://www.qatrack.org/204/index.php QAtrack] | * The lead enters the status of the testing to the [http://www.qatrack.org/204/index.php QAtrack] | ||
| − | * After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. | + | * After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. Use |
| + | [http://qa.openoffice.org/issues/enter_bug.cgi?comment=following%20builds%20of%20%3Cversion%3ERC%3Cnr%3E%20%3Clocalization%3E%20have%20passed%20QA%20and%20should%20be%0D%0Adistributed%20to%20the%20mirror%20network%20as%20stable%20builds%3A%0D%0A%3Curl1%3E%0D%0A%3Curl2%3E%20%0D%0A%0D%0A...;issue_type=TASK;rep_platform=All;op_sys=All;priority=P3;subcomponent=www;component=qa;version=OOo%202.0;short_desc=Distribute%20%3Cversion%3ERC%3Cnr%3E%20-%20%3Clang%3E%20localization%20as%20final;form_name=enter_issue this link] as template. | ||
* Then you update your project page to announce the availability of your localized builds :) | * Then you update your project page to announce the availability of your localized builds :) | ||
| Line 19: | Line 22: | ||
''Resources and links'' | ''Resources and links'' | ||
*[[Test Case Management(TCM) explained]] | *[[Test Case Management(TCM) explained]] | ||
| − | *[ | + | *[[Test Case Management]] |
*[http://qa.openoffice.org/localized/index.html QA Process for Localized builds] | *[http://qa.openoffice.org/localized/index.html QA Process for Localized builds] | ||
Revision as of 17:45, 15 December 2006
Testing your localized builds
Each Localization team or Native-Language project should, regardless of its resources, time and manpower, run some QA (Quality Assurance) tests on its localized builds.
OpenOffice.org has a project dedicated to Quality Assurance. You do not need to participate in the QA tests of the software itself, although your contribution is welcome. But you are requested to test your localized builds. The QA project has several tools both inside and outside the OpenOffice.org website.
The testing is required if you want the localized builds to be distributed on OpenOffice.org mirrors worldwide. The workflow is as follows:
- The lead of the NL project registers users (testers) in the TCM and assigns them various test scenarios. (At least the "Release Sanity" scenario should be assigned once per platform).
- The testers make the tests, and enter the results in the TCM.
- The lead enters the status of the testing to the QAtrack
- After the tests have been done, you update the status page and file an issue in IssueZilla, stating that the build is ready for distribution. Use
this link as template.
- Then you update your project page to announce the availability of your localized builds :)
Note: for all builds (RC1, RC2...., RCN) the tests are the same in TCM. Simply update the status of bugs in the current release.
Resources and links
