Links to QA Documentation

This page contains links to documentation you might find useful.

DEP-8 / adt

DEP-8 is a standard format for describing test suites in both debian and click packages. autopkgtest is a test runner that understands DEP-8 and can run tests in a number of a different backeds (schroot, qemu, ssh etc). By separating these two concerns, we get more reproducible builds, a clearer definition of tests, and a more explicit list of test requireents.

• Intro how to add an autopkgtest to a Debian package and run it like in Ubuntu CI

• DEP-8 test descriptions for click packages

• DEP-8 test descriptions for Debian packages

• How to run DEP-8 tests with adt-run

• How to run click package tests on Touch with adt-run

• How to Make a new virtualisation backend for autopkgtest

Autopilot

• The latest autopilot documentation can be found here

• How to architect your autopilot code using the Page Object Model

Releasing Autopilot

• CI Train in a nutshell

QA Best Practices

From time to time the Ubuntu Engineering QA department will make recommendations to other teams around what test helpers are needed. These proposals will appear here. They may be useful to get an idea of what is expected for new feature QA acceptance criteria.

QAKit

A repository for Ops-related and useful tools, including:

• Trello silo-card creation, interface to CI Train.

• PractitTest tracking.

• Metrics.

Recommended Tools & Libraries

A list of recommended tools & libraries.

• Autopilot for Functional & User acceptance tests.

• Use the Subunit v2 format for all test results. Avoid junitXML please. (Autopilot supports subunitout-of-the-box).

• Use testscenarios to add scenarios to tests. Be careful though, as this can make tests less readable. If in doubt, ask a QA engineer.

• Use testtools to test python projects where autopilot is not available.

• Use testresources to maintain expensive resources across multiple tests.