Differences between revisions 2 and 3
Revision 2 as of 2012-07-25 20:15:21
Size: 2955
Editor: nskaggs
Revision 3 as of 2012-07-25 20:16:04
Size: 2957
Editor: nskaggs
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
Line 28: Line 29:
Line 29: Line 31:

Interested in helping test during a call for testing? Great! This will be a quick walkthrough to help you understand how to use the QAtracker and submit a result.


First, make sure you understand what the QATracker is, and you are able to login to the Package Tracker.

Package Tracker

The Package Tracker is where we will get information about how to test, how to report a bug, and submit our results. The call for testing should have given you a specific link to a testing milestone (or event). Clicking on the link should take you to a page showing the packages to be tested, each with their own set of testcases. Be sure you login using the ‘login’ button located on the left-hand side as well. Otherwise you won’t be able to submit a result for the test! The images and descriptions below describe how a call for testing should look inside the tracker, and how to particpate.



This page shows the testcases to perform for the selected package.


In addition, you can see 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. This will typically have you installing a package from the repository or a ppa. Also notice that uninstallation instructions are given, should you wish to remove the package after testing.


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 you report bugs found properly. If you find a bug while testing, you’ll need to refer to this.

Executing the testcase

Select a testcase and you’ll land on a page containing instructions to follow to execute the test. The testcase is considered to have passed as long as all the expected results occur. If everything if ok, you can submit a passed result. If you encounter an error, refer to how to report a bug and report it. You’ll need it to submit your failure result.

Submitting results

If everything went well, you can submit a ‘passed’ result.


If you encountered trouble, file a bug, and note the bug number to record in the result submission. This will link the bug with your result and is important for tracking purposes to record.


Viewing Results

Once you’ve recorded your result you should see your name, bugs if any reported, and comments on the same screen you submitted your testcase results.


Testing/CallforTesting/Walkthrough (last edited 2013-04-01 21:34:29 by nskaggs)