launchpad development|
Size: 762
Comment: Expand a bit.
|
Size: 664
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| Obviously, you've already tested your changes manually and confirmed that they do what you expect. | 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 [[EC2Test|in the cloud]] before landing your changes on [[Trunk|trunk]]. |
| Line 7: | Line 7: |
| But how do you know they don't do anything you ''don't'' expect? | To run the tests, you run the {{{./bin/test}}} script, which is produced by {{{make build}}}. |
| Line 9: | Line 9: |
| Hence the test suite :-). The test suite runs remotely, in Amazon's EC2 computing cloud. ''TODO: we need to set up some way to give EC2 time to non-Canonical developers. Our internal instructions for testing on EC2 are not well-suited to external contributors.'' Basically, it's going to look something like this: {{{ $ cd my_bugfix123_branch ### for some reason this is necessary $ /path/to/lp-dev-utils/ec2test.py -f bugfix123-ec2test.out -b lp:~my_username/launchpad/bugfix123 }}} |
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. |
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.
