This page will walk through participating in a call for testing. It will demonstrate how to use the QAtracker and submit a result.
Video Screencast of Tutorial
A video version of this tutorial can be seen on youtube.
- Launchpad/Ubuntu SSO account
Make sure you understand what the QATracker is -- read that page first!
The Package Tracker is a tool containing information about how to test, how to report a bug, and submit results. As part of the call for testing a specific link or product name has been provided that links to a testing milestone (or event). Clicking on the link to a page showing the packages to be tested, each with their own set of testcases.
Logging in to the package tracker
Open a browser and navigate to http://packages.qa.ubuntu.com/
Click the login link located on the lefthand side of the page
- Enter your ubuntu sso account information
This page shows the testcases to perform for the selected package.
In addition, the notice board at the top that might contain information about what’s new in this version of the package.
Installing the package
Notice the link to the page for installation instructions. These instructions will typically require installing a package from the repository or a ppa. Also notice that un-installation instructions are given, for removing the package after testing if desired.
Reporting a bug
Additionally, there is a link to the bug reporting instructions. This page will detail how to report a bug and/or provide a link to help report bugs found properly. If a bug is found while testing, refer to that link for instructions on reporting.
Executing the testcase
Select a testcase and a page containing instructions to follow to execute the test will appear. Most of the testcases follow a simple format - perform an action, and then expect a result. A step in this format is shown below.
Alternatively the testcase may appear as the form of yes/no questions, where the expected result is a generally a yes.
For more information on the testcase formats, have a look at testcase formats page.
Go through each step of the testcase and follow the instructions. Perform the action, and ensure the expected result occurs. If something different occurs, note it as a bug, but continue the testcase.
Preparing to submit a result
While performing the test, if an expected result does not occur, note it as a bug. Follow the bug-reporting instructions for the product you are testing, and report it once the test has ended. A bug can be attached to a 'passed' or 'failed' result, and testcases can have multiple bugs.
If a bug was encountered, check the “Bugs” section above the submit form to see if the bug is a duplicate of one already reported against the testcase.
The list contains previously encountered bugs found during testing this testcase. Roll the mouse over the bug icon to see the information, or click to be taken to the report on launchpad. If the bug is found to be a duplicate, note the number of the bug and use it during your report. If the bug was not a duplicate and a new bug needs to be reported, follow the instructions found under the 'Link to bug reporting instructions' for the iso.
Determining the result
A testcase can have unexpected results, but still pass. Generally a passed result can be issued whenever each step in the testcase is able to be executed (even if the results don't match the expected result) and the final result matches the intent of the testcase. If in doubt of whether or not the bug in question represents a testcase failure, report the bug and file the testcase as 'failed' with a comment regarding the confusion. Ask for help on the mailing list for confirmation from someone else on the team.
Submit a result
An example of a failure result submission. Note that a bug number is required to submit a 'failed' result.
An example of a passed submission.
Congratulations, the result has been submitted! After submitting the result should appear in the list below the testcase.
If editing is needed, select the 'pencil' icon in the row of your submission to edit the testcase or delete it.
Further testcases can now executed and reported against. Explore other testcases and submit results. If unable to understand or execute a testcase, seek help on the mailing list. Happy Testing!