Tester
Summary
Thank you for your interest in helping ubuntu quality! This page will cover the basic setup and workflow for the tester role within the ubuntu quality team.
Setup
Before undertaking any of the work below you must first ensure you have installed the version of ubuntu that is currently in development.
Activities
After you have installed the development version of ubuntu, the following activities are available to you in order to help ubuntu. Pick one and help us today! We appreciate your test results, verification, and bug reports and triage activities!
=== Triage bug reports == In addition to filing bugs you find while running the development release, you can also help confirm and triage existing bug reports. See this wiki page for a full explanation of the triage process.
Provide Test Results
Ready to do some hands-on testing? You can help us by testing the applications and images
ISO Testing
Help submit results for the ubuntu images! Everything install/upgrade ok on your machine using today's image? Check out the isotracker for a list of testcases to perform against the images.
Here's a guide to using the Testdrive tool and submitting your first iso testcase result.
Ubuntu Touch Testing
Got a supported phablet device? Help us by running and reporting bugs you find within in the ubuntu touch images. Check out this page for full details to get ubuntu touch on your device and help test the images!
Application Testing
Want to help out by testing an application? We have manual testcases for the default applications and more inside ubuntu. Checkout the packages tracker for a list of testcases you can perform using your ubuntu installation.
Here's a guide to using the tracker and submitting an application testcase.
Hardware Testing
Perform SRU Verification
Other activities
Calls for Testing
During the cycle you may also see notifications asking for testing against a specific package or piece of software. Make sure you are signed up to the ubuntu quality mailing list and social media to ensure you receive the call for testing. Follow the directions given as part of the call to participate.
Report a bug
While you are running the development release and using it on a regular basis you may encounter a bug.
If the bug occurs because of a crash, follow the apport prompts to file the bug and add the proper logs along with it. See this page for full details on writing a proper bug report and for using apport to help report your crash. 'Note, apport is not turned on in the development release until around the alpha 1 milestone'.
If the bug isn't the result of a crash or if apport has not been turned on yet for the development release, file the bug manually using this guide.
Remember to provide enough information to allow a developer to reproduce your bug if possible!