TouchTesting

Differences between revisions 1 and 3 (spanning 2 versions)
⇤ ← Revision 1 as of 2013-09-16 12:24:41 →
Size: 2578
Editor: jibel
Comment:
← Revision 3 as of 2013-09-16 13:24:29 → ⇥
Size: 2844
Editor: jibel
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
 * '''Mailing List''' - The quality mailing list [https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality|ubuntu-quality@lists.ubuntu.com] is used to coordinate testing activities with all participants.  * '''Mailing List''' - The quality mailing list [[https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality|ubuntu-quality@lists.ubuntu.com]] is used to coordinate testing activities with all participants.
Line 73: Line 73:
}}}
Line 74: Line 75:
3. Wait until data collection is done.

4. At the question:

{{{
Line 76: Line 82:
  V: View report
[...]
Line 80: Line 87:
3. On your local machine, click on the link or copy/paste it into your browser. 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.

Warning /!\ W.I.P. Warning /!\

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.

Test coordination

  • Mailing List - The quality mailing list ubuntu-quality@lists.ubuntu.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.

Test process

TODO

Reporting a bug

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.

Test Activities

Describe here any specific test activities.

TODO

* Add link to reference documentation (how to flash, specific testing like MIR, how to troubleshoot, ...)

QATeam/TouchTesting (last edited 2015-01-22 17:18:23 by xdsl-83-150-81-40)