Information

Background

• Previous session at UDS-M

• Previous session at UDS-N

• Laptop Testing page

Summary

"Laptop Testing" is a community-driven project started with Lucid Lynx Alpha 3. Our goal is get Ubuntu working great on as many different makes and models of laptops as possible, mainly (but not only) testing point releases of the development cycle to help devs in triaging bugs. This could be done both in all the Community and LoCos, sharing hardware info about Laptops and trying to attract as many new contributors as possible.

Project has a Testing Team on launchpad. It uses the QA Mailing List and IRC channel #ubuntu-testing. In the Testing Team Wiki page this project is reported under Activities along with an English page.

In this session we would like to present goals reached and some suggestions to improve the project.

Activity

Lucid Cycle Data

• Tests here

Maverick Cycle Data

• Tests here

Natty Cycle Data

• Tests here (Wiki)

• Tests here (Laptop Tracker)

* N.B. testcases here stand for "case-id" to compare them with wiki data (e.g. tracker has 18 testcases but most of them contain more than one case-id)

Mixed reports, filed using wiki until Alpha 3, with Laptop Tracker from Beta 1.

• Laptop tested (Natty only, the tracker has also 7 for Maverick and 4 for Lucid).
  • 8+33 = 41 Wiki method + Laptop tracker
  How many people filed a report (dev and stable releases):
  • 49 people out of 73 members of ubuntu-laptop-testing team in Launchpad.
  How results have been reported (natty):
  • 4 reports with test results marked as failed but bugs not reported to Launchpad (all using wiki method)
  • 45 ok

Graph (dev cycles)

Laptop Tracker

• Blueprint on Launchpad

• Website: laptop.qa.ubuntu.com

How it works

• Profile setup

  • 

• Main page

  • 

• Testcases

  • 

• Report example

  • 

• Laptops summary

  • 

Thoughts

• Sensible increase in partecipants/tests performed.
• A consistent drop of errors in filing a report, using wiki the most common were:
  1. Various kind of typos, in some cases lack of important info,in others lots of unnecessary/unstructured or not properly formatted one etc...
  2. Tests marked as "Failed" without opening a bug or linking the bug on the page.
  3. Laptop report done not added in the Reports summary page.

Achievements

1. Much more easy and quick for a user to report a results.
2. Reports are structured and data validated and can be aggregated or filtered.
3. Testcases are grouped by category (Audio, Video, I/O etc.)
4. Users can be easily contacted via tracker/launchpad and milestone and can be notificated by email when a new milestone is available.

What's next

1. Extend the actual iso-testing tag system implementing a tag scheme specific for laptop (Audio-Video-I/O etc)
2. Add more testcases.

3. Try to automate the testing process using tools like kernel-qa script (using USB live disks for example).

4. Patches are welcome!

---

CategoryHomepage