Ubuntu Quality

Quality

The Quality team is the oil that lubricates the cogs of the engine that is Ubuntu. As a team, we help ensure that the work of many different teams is showcased in a good way. The Quality team believe things should “just work” when someone chooses one of our flavours, or one of the applications available from the archive.

If you are new to the ubuntu community, Quality is a great place to start. You will experience and interact with many different teams that Quality liaise with. We will encourage you to follow your interests and participate in these different teams that make Ubuntu “happen”.

As a member of the team you can choose when and how to be involved. Team members write testcases, execute tests, report bugs, give instructional presentations, and encourage best practices for Quality. Much of the work is driven from the same release schedule everyone else is driven by; however, testing activities are flexible enough to allow participation from anyone — the skills you need can be learned while participating.

If you enjoy solving problems, getting access to cutting edge software and fresh content, the Quality team is the place for you. If you have ever questioned the way your desktop worked (or perhaps didn’t work) you can contribute actively to make it work better.

Get started

  • Get connected with us! Subscribe to the Ubuntu Quality mailing list and join the Launchpad QA Team.
    • Introduce yourself! Send an introductory email to the mailing list and let us get to know you.
    • Pick an area of testing you would like to get involved with! You need to start somewhere, and picking something you like is a good place to start. Check out this getting involved page for help.
      • If you’re unsure of where to start, going through a testing walk-through is a good place to familiarize yourself with how to test and use the qatracker. For example, execute image tests against a daily image via testdrive by following this guide.
  • Submit your results! You’ve tested, perhaps found a problem; maybe even solved it. Tell the team what happened by submitting the results to the tracker.
  • Write new tests! See the need for an application to have more testcases? Perhaps it’s missing tests altogether ;-( Help fix that by writing some testcases for the Quality team to run in the future. As a team, we have two projects that hold our testcases; Ubuntu Manual Tests for manual testcases, and Ubuntu Autopilot Tests for automated testcases.

Documentation resources

  • The Ubuntu Quality Blog getting involved page guides you through the opportunities you have available to you as part of the team.
  • The Testing trackers records the results of testing by the team. This page documents how to utilize the tracker(s).
  • The Activities Page on the Ubuntu QA Team wiki contains instructional information on how to undertake the different activities available to you as part of the team. It also holds the schedule(s) and work items for the team. .

Where to find help

  1. ubuntu-quality mailing list at ubuntu-quality@lists.ubuntu.com
  2. #ubuntu-quality IRC channel