openstack/nova
Code Issues Proposed changes
Files
ea8323eca4f16e4af39d42ac28227aaa5e681d00
nova/doc/source/devref/unit_tests.rst
Joe Gordon 3a2e65c4bf Shrink devref.unit_tests, since info is in wiki. 
Don't keep a copy of the run_tests.sh flag list here since it
inevitably will get out of sync with the real list.

No need to go into detail on how unit testing is set up, since we already have a wiki
on how to run tests that applies for all OpenStack projects. Keep
section with tox examples since that is the most commonly used command.

Change-Id: Ia8eb059be164d9df3edfd69aedcebfd028da45ff
Related-Bug: 1219040
2014-05-04 20:14:38 -07:00

1.5 KiB
Raw Blame History

Unit Tests

Nova contains a suite of unit tests, in the nova/tests directory.

Any proposed code change will be automatically rejected by the OpenStack Jenkins server1 if the change causes unit test failures.

Preferred way to run the tests

The preferred way to run the unit tests is using tox. See the unit testing section of the Testing wiki page and Nova's HACKING.rst for more information. Following are some simple examples.

To run the Python 2.6 tests:

tox -e py26

To run the style tests:

tox -e pep8

You can request multiple tests, separated by commas:

tox -e py27,pep8

Running a subset of tests

Instead of running all tests, you can specify an individual directory, file, class, or method that contains test code.

To run the tests in the nova/tests/scheduler directory:

tox -e py27 nova.tests.scheduler

To run the tests in the nova/tests/virt/libvirt/test_libvirt.py file:

tox -e py27 test_libvirt

To run the tests in the CacheConcurrencyTestCase class in nova/tests/virt/libvirt/test_libvirt.py:

tox -e py27  test_libvirt.CacheConcurrencyTestCase

To run the ValidateIntegerTestCase.test_invalid_inputs test method in nova/tests/test_utils.py:

tox -epy27 test_utils.ValidateIntegerTestCase.test_invalid_inputs

Footnotes

  1. See jenkins.↩︎