This page is undergoing a large review and will be copied to the QATrack tool's website for comfortability soon.
QATrack is the OpenOffice.org Communitys build management system. It provides the primary information spot for builds and supports the OpenOffice.org Community in all steps of the QA and release processes.
- 1 Get an OpenOffice.org website account
- 2 General set up
- 3 First Page
- 4 View Status
- 5 Submit Builds
- 6 Users
- 7 Languages
- 8 Show Build
- 9 Managing QA
- 10 Status of QA
- 11 Find your builds
- 12 Mark builds as "IN QA"
- 13 Test!
- 14 Update the status page
Get an OpenOffice.org website account
While all information in QATrack is publicly available without the need to log in, having an account gives you the ability to change user interface language, and gain more access are you get more involved.
Get an OpenOffice.org account
Your can get an OpenOffice.org account here:
Get an OpenOffice.org Account
Send an e-mail to firstname.lastname@example.org to request permissions to the QATrack system. Please specify the languages that you would like to get access to.
Read more about roles here.
General set up
When you have the permissions that you need, you are ready to log in to QATrack.
If you have another primary language than English, you might be interested in any of the languages that QATrack is localized in. Click Account Preferences in the upper right corner of the header, and change your interface language.
The first page serves as a dashboard and gives you an overview of the latest builds that are interested for you.
It displays your languages' latest builds on the left with the Int Id, Version, Platform and Status of each build. In the middle latest English (United States) builds are displayed with the Int Id, Version, Platform and Status of each build. You can click on any builds Int Id to get to the build's page.
On the right messages posted by the portal's administrators are shown with the latest message first. It also gives you the latest news from the RSS feed.
For more information about builds, click here.
The View Status page provides an advanced search feature to query the database for the status of a specific version, language, platform, status and more.
The field Version is required to limit the preassure on the QATrack system and must contain at least 3 characters, e.g 2.4. The field Available for last specifies the days since the build was added (provided) to the system. If a field is not filled in, all possible values are implied.
The search engine provides two views, Overview view, and Detailed View The Overview view displays an overview of all the builds returned by the result. Each build has the color associated with its current status, and an initial letter of its current status. The Detailed View displayes a detailed view of the builds returned by the result. Each build has the color associated with its current status, and displayed the version of the build. Each build in this view also has an advanced tooltip displaying the builds Build Id, Version, Status, Responsible, Created and Filename fields of the build.
The search result URL can easily be copied and sent to another individual as the URL contains the search parameters specified.
This page allows users to provide builds to the QATrack build management system.
The builds that you can submit here largely dipends on the global role and languages that are associated by your account. Administrators and Build Providers can submit builds for all languages. Other users can only submit builds for the languages that are associated with your account.
The process is divided into 3 steps defined below.
Step 1 - provide one build
- Enter the build URI in the field Build URI.
- Click Analyze Builds.
Step 1 - provide several builds
- Enter the build URI for one of the builds in the field Build URI.
- Select Check that the files are available on server (recommended) if you would like QATrack to check the availability of each build URI.
- Select the languages that you would like to add for this build. The build submission engine will automatically parse the URI and create a table of builds by mixing the Build URI and the languages. Use Select all languages, Unselect all languages and Select Sun languages or by clicking on the language names to select languages.
Tip: You can click on a language name to select the language. You do not have to click on the checkbox.
- Analyze the result of the analyze. The interface informs you about duplicates and builds that were not available. Duplicate builds and unavailable builds are never added to QATrack.
- If everything is OK, click Register Builds. If something is wrong, click your browsers Back button to review Step 1.
The builds are added in accordance with your request. A Build Submission Report is displayed which you can save as a receipt.
An email for each build is sent to all users which are associated with that build's language.
An entry is added to the RSS feed with all the builds added.
The first item (Manage) takes you to a page where you can assign QA-responsible people to different builds, and edit the QA status of those builds. This information will appear on the Status page.
The Manage page lists all builds currently available for QA in your project. The drop-down menus allow you to make different choices.
You will notice that you now have a toolbar at the top of the page. This will appear on top of both the Manage and the Status pages, allowing you to switch between these views, login, logout etc.
If this toolbar is not showing, you have probably become logged out. Check the link at the bottom of the page. If it says you need to login to edit, click on that link, and you will be taken back to the login page.
Click on the toolbar link View QA status, to go to the Status page.
Status of QA
Now you see an even larger table, listing all the localized builds. The list is shown in alphabetical order, but language with no current builds fall to the end of the list.
You can filter this list by status and type, using the drop-down menu at the top of the page. You will find this table very handy for keeping track of QA for your builds. As is stated on the login page, you can also subscribe to an RSS feed to monitor these changes.
The table provides a column for each architecture, so you will need to scroll sideways sometimes, unless you have a very wide screen.
Hover your mouse over the download link for a build, to see its current information from the Manage QA table. This feature makes the Status page a fairly complete overview of build QA status.
The table also uses colours and styles to label status.
- Black, crossed-out builds have been REJECTED, due to lack of quality
- Red builds are UNTESTED as yet
- Yellow builds are INQA, currently being tested
- Green builds are APPROVED after complete QA
- White builds have been DISTRIBUTED due to approval, after logging the appropriate issue with the issue tracker
Good luck with your QA: may all your builds be green! :)
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 email@example.com with your request.
If you build OOo yourself, please ask for "Build provider" role in QATrack so that you can upload builds as soon as you make them available.
From January 2007, all registered users can submit builds, so you no longer need a "Build provider" role.
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.
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.