openstack/nova
Code Issues Proposed changes
Files
b127d03b9feb6a047cccf224c39417faaabc980c
nova/doc/source/devref/unit_tests.rst
Matthew Gilliard 8654f948da Doc: minor fixes to unit testing devref 
The unit testing devref had a bit of inconsistent formatting, and a reference
to HACKING.rst which could have been linkifed.  This patch fixes both of those,
and additionally the examples have been updated to reflect the recent split
into functional and unit tests.

Change-Id: I15129808d0d1271c1223e7ab8d8532f8cb2f7293
2014-12-09 12:04:37 +00:00

1.6 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 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/unit/scheduler directory:

tox -e py27 nova.tests.unit.scheduler

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

tox -e py27 test_driver

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

tox -e py27  test_driver.CacheConcurrencyTestCase

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

tox -epy27 test_utils.ValidateIntegerTestCase.test_invalid_inputs

Footnotes

  1. See jenkins.↩︎

View Git Blame Copy Permalink