Information

Background

• Previous session at UDS-M

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 testing point releases of the development cycle. This could be done both in all the Community and LoCos, sharing hardware info about Laptops to avoid duplicates and trying to attract as many new contributors as possible.

Project has been started by the Italian LoCo Testing team on launchpad. It's organized at moment with Wiki pages, a Mailing List and an IRC channel #ubuntu-it-test. In the Testing Team Wiki page this project is reported under Activities along with an English page.

In this session we would like to discuss how to improve this project.

Activity

Lucid Cycle Data

• Laptop tested.
  • 49
  How many people filed a report:
  • 40 people (7 of them are also active members of the Italian Testing Team).
  How results have been reported:
  • 17 of them useless (for various reasons: bugs not reported to Launchpad, tests never done or results never reported etc.)
  • 20 ok.
    • → 54% ok

Maverick Cycle Data

• Laptop tested.
  • 24
  How many people filed a report:
  • 21 people (7 of them are also active members of the Italian Testing Team.)
  How results have been reported:
  • 7 useless (for various reasons: bugs not reported to Launchpad, tests never done or results never reported etc.)
  • 15 ok.
    • → 71,4% ok

* Counted as done even tests performed in "useless" reports (those marked as such because test failed but a bug have not been reported). Tests done several days after the final release have not been considered.

Thoughts

• Less people have partecipate in Maverick so less testcases have been performed.
• A large part of this decrease is due to a significant drop of wrong/useless reports.
• Number of testers from the Italian testing team (moderated) has been stable .
• List of common error found in reporting:
  1. Testcase marked as "Failed" without opening a bug or linking the bug on the page

  2. Laptop report not added in the Reports page

  3. Laptop report linked wrong in the Reports page (typos)

  4. Name/nick of tester not added with the @SIG@ macro (users can't be identified if the nick is different or has typos)

  5. Due to the open structure of wiki pages, some people add lots of unnecessary/unstructured or not properly formatted info
  6. A script to import Laptop testcases in checkbox is available but is useless without a plan to use/integrate checkbox database

How to improve

• Dedicated ISO Tracker. This would resolve a lot of issues and advantages are listed below:
  1. Users needs to be registered and providing the launchpad nickname are recognizable
  2. Reports are structured and data validated and can be aggregated or filtered
  3. Really easy to report a test result
  4. No more failed test with bugs not linked
  5. Tag system already implemented
• ISO Tracker / Checkbox integration

---

CategoryHomepage