Difference between revisions of "QATrack"
(Whole process) |
m (Fixes) |
||
| Line 6: | Line 6: | ||
The tool automatically maintains a status page, which summarizes | The tool automatically maintains a status page, which summarizes | ||
the status of every build, and specialized subpages. It assists | the status of every build, and specialized subpages. It assists | ||
| − | in every step of the QA process | + | in every step of the QA process. |
The original design and history of QATrack is at [[Release QA Tracking Tool]]. | The original design and history of QATrack is at [[Release QA Tracking Tool]]. | ||
| − | + | == Get a QATrack account == | |
| − | For the time being, you will need to get a separate QATrack account, different | + | For the time being, you will need to get a separate QATrack account, different from the ones you use to login to the OpenOffice.org website or to TCM. |
| − | Native Language project leads can e-mail dev@qa.openoffice.org to get a QATrack account. Please specify the language code for you NL project. | + | Native Language project leads can e-mail dev@qa.openoffice.org to get a QATrack account. Please specify the language code for you NL project when appplying. |
| − | + | == Find your builds == | |
QATrack lists available builds from many providers. You will be automatically be notified by e-mail and RSS when a new build in your language is available. | QATrack lists available builds from many providers. You will be automatically be notified by e-mail and RSS when a new build in your language is available. | ||
| Line 23: | Line 23: | ||
If you build OOo yourself, please ask for "Build provider" status in QATrack so that you can upload builds as soon as you make them available. | If you build OOo yourself, please ask for "Build provider" status in QATrack so that you can upload builds as soon as you make them available. | ||
| − | + | == Mark builds as "IN QA" == | |
You can edit the build status for builds in your language. When you start TCM testing, please set the status to <tt>INQA</tt> for the builds being tested. | You can edit the build status for builds in your language. When you start TCM testing, please set the status to <tt>INQA</tt> for the builds being tested. | ||
| Line 31: | Line 31: | ||
You can delegate QA for a build to other QATrack users from your NL project. They will appear in the QA Contact field in the information box for that build. | You can delegate QA for a build to other QATrack users from your NL project. They will appear in the QA Contact field in the information box for that build. | ||
| − | + | == Test! == | |
Run the QA tests your NL projects uses (TCM tests or other). Get the final approval or rejection. | Run the QA tests your NL projects uses (TCM tests or other). Get the final approval or rejection. | ||
| − | + | == Update the status page == | |
| − | + | === If the build is rejected === | |
Just mark it as <tt>REJECTED</tt> in the status page. | Just mark it as <tt>REJECTED</tt> in the status page. | ||
| − | + | === If the build is approved === | |
* Mark it as <tt>APPROVED</tt> in the status page. | * Mark it as <tt>APPROVED</tt> in the status page. | ||
* Open an issue to request distribution to mirrors. | * Open an issue to request distribution to mirrors. | ||
* Check that status changes to <tt>DISTRIBUTED</tt> (or change it yourself) once the build is distributed as stable. | * Check that status changes to <tt>DISTRIBUTED</tt> (or change it yourself) once the build is distributed as stable. | ||
Revision as of 13:12, 17 December 2006
QATrack helps the OOo community during all steps of the QA
process for localized builds.
The tool automatically maintains a status page, which summarizes the status of every build, and specialized subpages. It assists in every step of the QA process.
The original design and history of QATrack is at Release QA Tracking Tool.
Contents
Get a QATrack account
For the time being, you will need to get a separate QATrack account, different from the ones you use to login to the OpenOffice.org website or to TCM.
Native Language project leads can e-mail dev@qa.openoffice.org to get a QATrack account. Please specify the language code for you NL project when appplying.
Find your builds
QATrack lists available builds from many providers. You will be automatically be notified by e-mail and RSS when a new build in your language is available.
If you cannot see the build you wish to QA even though it has already been available for some days, e-mail dev@qa.openoffice.org with your request.
If you build OOo yourself, please ask for "Build provider" status in QATrack so that you can upload builds as soon as you make them available.
Mark builds as "IN QA"
You can edit the build status for builds in your language. When you start TCM testing, please set the status to INQA for the builds being tested.
You can optionally specify a closing date for your tests. This does not affect QATrack operation, it will just be displayed in the information box for that build.
You can delegate QA for a build to other QATrack users from your NL project. They will appear in the QA Contact field in the information box for that build.
Test!
Run the QA tests your NL projects uses (TCM tests or other). Get the final approval or rejection.
Update the status page
If the build is rejected
Just mark it as REJECTED in the status page.
If the build is approved
- Mark it as APPROVED in the status page.
- Open an issue to request distribution to mirrors.
- Check that status changes to DISTRIBUTED (or change it yourself) once the build is distributed as stable.
