TouchTesting

Differences between revisions 60 and 61
Revision 60 as of 2014-07-15 17:07:49
Size: 3705
Editor: nskaggs
Comment:
Revision 61 as of 2014-07-15 17:27:04
Size: 4125
Editor: nskaggs
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
= 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.
= Testing ubuntu touch =
Welcome! This page contains the information you need to know to test ubuntu touch. Follow the steps outlined to keep your device updated and your testing relevant.
Line 8: Line 8:
== Test coordination ==
 * '''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.
 * '''IRC''' - join the Ubuntu QA in `#ubuntu-quality` and and Ubuntu Touch `#ubuntu-touch` IRC channels on freenode.
== Setup ==
You should subscribe to the phone mailing list, and keep in mind the following IRC channels for help.
Line 12: Line 11:
== Test process ==
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.
 * '''Mailing Lists''' - The [[https://launchpad.net/~ubuntu-phone|ubuntu phone mailing list]] provides constant updates about what is happening on the phone images.
 * '''IRC''' - join the Ubuntu QA in `#ubuntu-quality` and and Ubuntu Touch `#ubuntu-touch` IRC channels on freenode if you need realtime help.
Line 15: Line 14:
== Daily Image Testing ==
=== Install the current stable image ===
You also need to flash your phablet device with the last development proposed image.

=== Install the current development image ===
Line 18: Line 18:
{{{
  $ ubuntu-device-flash
}}}
In order to wipe clean and start fresh with the latest current image:
{{{
  $ ubuntu-device-flash --no-backup
}}}
Line 31: Line 24:
== Test process ==
This describes the daily process of testing. We will flash our devices, read what's changed, and look for bugs.
Line 32: Line 27:
==== 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.
== Step 1, Update ==
You need a phone or tablet with the latest development proposed image. If needed, install the current development image now by flashing or using the OTA update feature.

=== Perform a system update ===
Once you are running the ubuntu image you may perform a system update from the device itself. The images now prompt and even autoupdate if allowed. To manually update, select the 'system-settings' application, then click update. Once the download completes, press the install and restart button.
Line 39: Line 37:
=== Check to see what's changed ===
A list of changes between stable images can be [[http://people.canonical.com/~ogra/touch-image-stats/current/|found here]]. The list contains the list of changing packages.
== Step 2, Check to see what's changed ==
A list of changes between stable images can be [[http://people.canonical.com/~lzemczak/landing-team/|found here]]. The list contains the list of changing packages.
Line 42: Line 40:
Use these changes to drive exploratory testing below. Use these changes to help you understand what is new, so you can check it for bugs.
Line 44: Line 42:
=== Test === == Step 3, Test ==
Line 47: Line 45:
* Perform smoke testing on a specific packageset of the phone.

* File bugs against any issues encountered
* Use the device as you normally would as you go about daily activities.
Line 53: Line 49:
=== Report Bugs ===
See the [[QATeam/TouchTesting/BugReporting|Reporting a Bug page]] for details.
== Step 4, Report Bugs ==
Report any bugs you found while testing. See the [[QATeam/TouchTesting/BugReporting|Reporting a Bug page]] for details.

== Step 5, Review Bugs ==
Review bugs found. If nothing new found, seek to confirm existing bugs via triaging. You can also flag bugs as good candidates for tests to prevent future regressions.

=== Confirm an existing bug ===
Not finding any bugs yourself? Look at [[QATeam/TouchTesting/BugReporting#Triaging|Triaging]] and confirm bugs others have found.
Line 63: Line 65:
=== Confirm an existing bug ===
Not finding any bugs yourself? Look at [[QATeam/TouchTesting/BugReporting#Triaging|Triaging]] and confirm bugs others have found.


Testing ubuntu touch

Welcome! This page contains the information you need to know to test ubuntu touch. Follow the steps outlined to keep your device updated and your testing relevant.

Setup

You should subscribe to the phone mailing list, and keep in mind the following IRC channels for help.

  • Mailing Lists - The ubuntu phone mailing list provides constant updates about what is happening on the phone images.

  • IRC - join the Ubuntu QA in #ubuntu-quality and and Ubuntu Touch #ubuntu-touch IRC channels on freenode if you need realtime help.

You also need to flash your phablet device with the last development proposed image.

Install the current development 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.

To test with the proposed image:

  $ ubuntu-device-flash  --channel=devel-proposed

Test process

This describes the daily process of testing. We will flash our devices, read what's changed, and look for bugs.

Step 1, Update

You need a phone or tablet with the latest development proposed image. If needed, install the current development image now by flashing or using the OTA update feature.

Perform a system update

Once you are running the ubuntu image you may perform a system update from the device itself. The images now prompt and even autoupdate if allowed. To manually update, select the 'system-settings' application, then click update. Once the download completes, press the install and restart button.

Visual Walkthrough of updating

Example of no updates found

Step 2, 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 help you understand what is new, so you can check it for bugs.

Step 3, Test

* 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.

* Use the device as you normally would as you go about daily activities.

* Remember this is exploratory testing, so try and break things!

Step 4, Report Bugs

Report any bugs you found while testing. See the Reporting a Bug page for details.

Step 5, Review Bugs

Review bugs found. If nothing new found, seek to confirm existing bugs via triaging. You can also flag bugs as good candidates for tests to prevent future regressions.

Confirm an existing bug

Not finding any bugs yourself? Look at Triaging and confirm bugs others have found.

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;

  1. Remove the touch-needs-autopilot tag from the original bug

  2. Open a new bug against the same project, tagged with qa-touch-automated

  3. Assign yourself to the bug and update progress as usual. When you release the test, close the bug with fix released.

Tips and Tricks

Check out these handy tips to help you while testing.

QATeam/TouchTesting (last edited 2015-01-22 17:18:23 by knome)