• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Writing tests

For each part of an application there are 2 level of testing:

• unit testing - comprehensive testing, including cornerstone cases
• smoke testing - critical functionality

1. Model

1. Unit testing

   • Files locate in lib/lp/<application>/scripts/tests

2. Smoke testing

   • Files locate in lib/lp/<application>/doc

1. View

1. Unit testing

   • Files locate in lib/lp/<application>/browser/tests

2. Smoke testing

   • Files locate in lib/lp/<application>/stories

   • More details: PageTests

1. Javascript

1. Unit testing

   • More details: TestingJavaScript JavascriptUnitTesting

2. Smoke testing

   • Files locate in lip/lp/<application>/windmill (if written in Python) and lib/canonical/launchpad/windmill/jstests

(if written in JS)

• More details: Windmill

1. Scripts

• Files locate in lib/lp/<application>/scripts/tests

Testing Your Launchpad Changes

This page is very much still in progress.

The normal pattern for testing your changes is to run the tests you think will be affected locally, and then (possibly just before submission) run all the tests in the cloud before landing your changes on trunk.

To run the tests, you run the ./bin/test script, which is produced by make build.

You can see all the options you have by running ./bin/test --help, but usually you will run ./bin/test -vvct $pattern where $pattern is a regular expression that is used to filter the tests that will be run.

CategoryTesting