|Deletions are marked like this.||Additions are marked like this.|
|Line 27:||Line 27:|
|''Need more detailed list of what is actually changing''|| * Changes in current: http://people.canonical.com/~j-lallement/touch/changes/current/
* Changes in pending: http://people.canonical.com/~j-lallement/touch/changes/
|Line 42:||Line 45:|
|Once testing is completed, review the list of reported bugs with the needs-autopilot-test tag. [[https://wiki.ubuntu.com/Touch/CoreApps/Testing/ContributeAutopilotTestcase|Automate a testcase using autopilot]] that fixes the bug to ensure the same bug doesn't reappear.||Once testing is completed, review the list of reported bugs with the [[https://bugs.launchpad.net/bugs/+bugs?field.tag=needs-autopilot-test| needs-autopilot-test tag]]. [[https://wiki.ubuntu.com/Touch/CoreApps/Testing/ContributeAutopilotTestcase|Automate a testcase using autopilot]] that fixes the bug to ensure the same bug doesn't reappear.|
|Line 45:||Line 48:|
|All bugs filed should use the ???? (need to decide) tag. Omer has made available a tool to help with the process of filing a bug report||All bugs filed should use the touch-swat tag. Omer has made available a tool to help with the process of filing a bug report.|
|Line 48:||Line 51:|
|File against the ubuntu source package for the failed component.||File against the ubuntu source package for the failed component. [[https://wiki.ubuntu.com/QATeam/TouchTesting/BugFiling|See this page]] for a full broken out list of components.
== List of Reported Bugs ==
[[https://bugs.launchpad.net/bugs/+bugs?field.tag=touch-swat|All touch-swat bug reports]]
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 until the release of Saucy, check back frequently.
Mailing List - The quality mailing list email@example.com 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.
$ phablet-flash ubuntu-system
Alternatively, once you are running the ubuntu image you may perform a system update from the device itself.
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.
Changes in current: http://people.canonical.com/~j-lallement/touch/changes/current/
Changes in pending: http://people.canonical.com/~j-lallement/touch/changes/
* 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 section below for details.
Add a testcase for reported bugs
Reporting a bug
All bugs filed should use the touch-swat tag. Omer has made available a tool to help with the process of filing a bug report.
What package should I file against?
File against the ubuntu source package for the failed component. See this page for a full broken out list of components.
List of Reported Bugs
Filing the Bug
Using Omer's tool
There is a crash file in /var/crash
If the bug is a crash and there is a crash file in /var/crash, you can report it with apport.
1. Connect to the device with adb
$ adb shell
2. Check for any crash file in /var/crash
3. Report a bug with apport:
$ apport-cli /var/crash/name_of_crash_file.crash
4. Follow the instructions
5. To the question "What would you like to do? Your options are:", answer "S: Send report"
6. Wait for the upload to proceed
7. Upon upload you'll be presented with a prompt like:
*** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/upstart-app-launch/+filebug/<UUID> You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel
8. Copy the URL to a browser running on your desktop/laptop, it is more convenient than running a browser on the phone to report bug and proceed with the bug reporting process in launchpad
9. Then follow the usual tagging plan and triaging process
There is no crash file
1. Connect to the device with adb
$ adb shell
2. Find the right package (TODO: Document difference between preinstalled dpkg based packages and click package)
$ ubuntu-bug maliit-framework
3. Wait until data collection is done.
4. At the question:
What would you like to do? Your options are: S: Send report (4.3 KB) V: View report [...] https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+filebug/<UUID>?
Press 'S' or 'K' if you want to copy the report to another machine (for example if networking is not enabled on the device).
3. If you're reporting from the device, on your local machine, click on the link or copy/paste it into your browser.
Describe here any specific test activities.
* Add link to reference documentation (how to flash, specific testing like MIR, how to troubleshoot, ...)
* Add link and information on omer's testing tool
* See if popey's scripts might be useful and add them
* Need better list of what's changing between images
* Add list of who's testing which feature sets / areas
* Need to expand how to file bugs against which packages