|Deletions are marked like this.||Additions are marked like this.|
|Line 54:||Line 54:|
|See the [[QATeam/TouchTesting/Reporting_a_bug|Reporting a Bug page]] for details.||See the [[QATeam/TouchTesting/BugReporting|Reporting a Bug page]] for details.|
|Line 64:||Line 64:|
|Not finding any bugs yourself? Look at [[QATeam/TouchTesting/Reporting_a_bug#Triaging|Triaging]] and confirm bugs others have found.||Not finding any bugs yourself? Look at [[QATeam/TouchTesting/BugReporting#Triaging|Triaging]] and confirm bugs others have found.|
Touch Test SWAT
Welcome to the testing page of the Touch Testing SWAT. These pages provide up to date information of current testing activities for Touch.
Mailing List - The quality mailing list firstname.lastname@example.org is used to coordinate testing activities with all participants.
IRC - join the Ubuntu QA in #ubuntu-quality and and Ubuntu Touch #ubuntu-touch IRC channels on freenode.
This describes the daily process of testing. We will flash our devices, look for bugs, then look to write autopilot tests for any fixed bugs to prevent that bug from re-occurring.
Daily Image Testing
Install the current stable image
Flash your phone to the latest stable image (note: we want the "current" image of touch_ro). If you have not yet bootstrapped or unlocked your phone's bootloader, see the install page for more information.
In order to wipe clean and start fresh with the latest current image:
$ ubuntu-device-flash --no-backup
To test with the proposed image:
$ ubuntu-device-flash --channel=devel-proposed
Perform a system update
Alternatively, once you are running the ubuntu image you may perform a system update from the device itself. To do this, select 'system-settings' application, then click update. Press the download button, and once the download is completed, the install button.
Check to see what's changed
A list of changes between stable images can be found here. The list contains the list of changing packages.
Use these changes to drive exploratory testing below.
* Run through the list of new features and changed areas of the phone, paying specific attention to spot regressions and verify the features are working.
* Perform smoke testing on a specific packageset of the phone.
* File bugs against any issues encountered
* Remember this is exploratory testing, so try and break things!
See the Reporting a Bug page for details.
Add a testcase for reported bugs
Once testing is completed, review the list of reported bugs with the touch-needs-autopilot tag. Pick a testcase to automate using autopilot that tests the bug to ensure the same bug doesn't reappear. So we can track work happening on these bugs, follow this process while writing the test;
Remove the touch-needs-autopilot tag from the original bug
Open a new bug against the same project, tagged with qa-touch-automated
- Assign yourself to the bug and update progress as usual. When you release the test, close the bug with fix released.
Confirm an existing bug
Not finding any bugs yourself? Look at Triaging and confirm bugs others have found.
Tips and Tricks
Check out these handy tips to help you while testing.