launchpad development|
Size: 1770
Comment:
|
Size: 2858
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<tablestyle="width: 100%;" colspan=3 style="background: #2a2929; font-weight: bold; color: #f6bc05;">This page is an introduction to writing and running test. All pages dedicate to testing can be found in CategoryTesting. || ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
|
| Line 42: | Line 46: |
| 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. | You can see all the options you have by running {{{./bin/test --help}}}. 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. You can use '!PATTERN' to match all expression not matching that patter. Ex, to run all test, except the one at Windmill layer you can use: {{{ ./bin/test -vvc --layer '!Windmill' }}} Since Librarian and MemCache does not change often and they take a long time to be started and shutdown, ./bin/test can leave them started by using this command: {{{ LP_PERSISTENT_TEST_SERVICES=1 ./bin/test PATTERN }}} You can kill them using {{{ ./bin/kill-test-services }}} When running tests written in python files, and you only want to test a file, you can speed up the test by specifying the full path to the python file: {{{ LP_PERSISTENT_TEST_SERVICES=1 ./bin/test PATH/TO/PYTHON/TEST/FILE.py }}} |
This page is an introduction to writing and running test. All pages dedicate to testing can be found in CategoryTesting. |
Writing tests
For each part of an application there are 2 level of testing:
- unit testing
- comprehensive testing, including cornerstone cases
- written in python files (no doctest)
- smoke/functional/integration testing
- testing normal use cases, simple or comples
- written using doctest format
1. Model
- Unit testing
Files locate in lib/lp/<application>/scripts/tests
- Smoke testing
Files locate in lib/lp/<application>/doc
1. View
- Unit testing
Files locate in lib/lp/<application>/browser/tests
- Smoke testing
Files locate in lib/lp/<application>/stories
More details: PageTests
1. Javascript
- Unit testing
More details: TestingJavaScript JavascriptUnitTesting
- 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
1. API
Files located in lib/lp/<application>/stories/webservices
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.
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.
You can use '!PATTERN' to match all expression not matching that patter. Ex, to run all test, except the one at Windmill layer you can use:
./bin/test -vvc --layer '!Windmill'
Since Librarian and MemCache does not change often and they take a long time to be started and shutdown, ./bin/test can leave them started by using this command:
LP_PERSISTENT_TEST_SERVICES=1 ./bin/test PATTERN
You can kill them using ./bin/kill-test-services
When running tests written in python files, and you only want to test a file, you can speed up the test by specifying the full path to the python file:
LP_PERSISTENT_TEST_SERVICES=1 ./bin/test PATH/TO/PYTHON/TEST/FILE.py
