Difference between revisions of "Testing"
| Line 2: | Line 2: | ||
= Testing [[OpenStack]] Projects = | = Testing [[OpenStack]] Projects = | ||
| − | Unit tests are available for each project, and testing also involves installing and running | + | Unit tests are available for each project, and testing also involves installing and running OpenStack Compute or Object Store and reporting any oddities you see. |
== Running Swift Tests == | == Running Swift Tests == | ||
| Line 10: | Line 10: | ||
== Running Nova Tests == | == Running Nova Tests == | ||
| − | To run tests, run the run_tests.sh script in the Nova source code directory. Nose tests in Nova will not work in the Austin release but will work in the Bexar release. | + | To run tests, run the run_tests.sh script in the Nova source code directory. Nose tests in Nova will not work in the Austin release but will work in the Bexar release. Look at ./test/functionalnosetests/swift_testing.py for an explanation on how the test script decides whether functional tests are skipped or not based on the availability of configuration information. |
Revision as of 15:15, 13 December 2010
Testing OpenStack Projects
Unit tests are available for each project, and testing also involves installing and running OpenStack Compute or Object Store and reporting any oddities you see.
Running Swift Tests
Swift has functional tests, functional nose tests, and unit tests available in the source in the test directory. At Rackspace we test several environments including a staging area with 36 storage nodes.
Running Nova Tests
To run tests, run the run_tests.sh script in the Nova source code directory. Nose tests in Nova will not work in the Austin release but will work in the Bexar release. Look at ./test/functionalnosetests/swift_testing.py for an explanation on how the test script decides whether functional tests are skipped or not based on the availability of configuration information.
