OpenStack Compute (Nova)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Balazs Gibizer edeeaf9102 Add late server group policy check to rebuild 5 years ago
api Merge "log test: use fixtures.StandardLogging in setUp" 5 years ago
cells Merge "Add instance action record for snapshot instances" 5 years ago
cmd Update nova-status and docs for nova-compute requiring placement 1.14 5 years ago
compute Add late server group policy check to rebuild 5 years ago
conductor Add late server group policy check to rebuild 5 years ago
console Fix accumulated nits 5 years ago
db Merge "archive_deleted_instances is not atomic for insert/delete" 5 years ago
image Merge "Handle images with no data" 5 years ago
network make unit tests compatible with os-vif 1.8.0 5 years ago
notifications Transform instance.resize_prep notification 5 years ago
objects [placement] Fix resource provider delete 5 years ago
pci Address nits in I46d483f9de6776db1b025f925890624e5e682ada 5 years ago
privsep Start moving users of parted to privsep. 5 years ago
scheduler Merge "placement: using the dict format for the allocation in claim_resources" 5 years ago
virt Merge "libvirt: don't attempt to live snapshot paused instances" 5 years ago
volume Add support for getting volume details with a specified microversion 5 years ago
README.rst Do not monkey patch eventlet in unit tests 5 years ago Make BlockDeviceMapping object support uuid 5 years ago Add access_url_base to console_auth_tokens table 5 years ago Add Flavor.description attribute 5 years ago fake_notifier: Refactor wait_for_versioned_notification 5 years ago Don't persist could-be-stale InstanceGroup fields in RequestSpec 5 years ago Enable reset keypair while rebuilding instance 5 years ago Do not setup conductor in BaseAPITestCase 5 years ago Drop support for the Cinder v2 API 5 years ago Cleanup mount / umount and associated rmdir calls 5 years ago Get auth from context for glance endpoint 5 years ago Use ksa adapter for keystone conf & requests 5 years ago Nits from Ic3ab7d60e4ac12b767fe70bef97b327545a86e74 5 years ago Merge "conf: Remove 'vendordata_driver' opt" 5 years ago Remove dead code of api.fault notification sending 5 years ago Fix update_cell to ignore existing identical cells 5 years ago Add microversion to allow setting flavor description 5 years ago Follow up on removing old-style quotas code 5 years ago Make TestRPC inherit from the base nova TestCase 5 years ago Fix test_rpc_consumer_isolation for oslo.messaging 5.31.0 5 years ago Fix NoneType error when [service_user] is misconfigured 5 years ago Fix test_rpc_consumer_isolation for oslo.messaging 5.31.0 5 years ago Use method validate_integer from oslo.utils 5 years ago Move test_uuid_sentinels to NoDBTestCase 5 years ago Make ConductorTaskTestCase run with 2 cells 5 years ago


OpenStack Nova Testing Infrastructure

This README file attempts to provide current and prospective contributors with everything they need to know in order to start creating unit tests for nova.

Note: the content for the rest of this file will be added as the work items in the following blueprint are completed:

Test Types: Unit vs. Functional vs. Integration


Writing Unit Tests


Using Fakes



The TestCase class from nova.test (generally imported as test) will automatically manage self.stubs using the stubout module and self.mox using the mox module during the setUp step. They will automatically verify and clean up during the tearDown step.

If using test.TestCase, calling the super class setUp is required and calling the super class tearDown is required to be last if tearDown is overridden.

Writing Functional Tests


Writing Integration Tests


Tests and Exceptions

A properly written test asserts that particular behavior occurs. This can be a success condition or a failure condition, including an exception. When asserting that a particular exception is raised, the most specific exception possible should be used.

In particular, testing for Exception being raised is almost always a mistake since it will match (almost) every exception, even those unrelated to the exception intended to be tested.

This applies to catching exceptions manually with a try/except block, or using assertRaises().


self.assertRaises(exception.InstanceNotFound, db.instance_get_by_uuid,
                  elevated, instance_uuid)

If a stubbed function/method needs a generic exception for testing purposes, test.TestingException is available.


def stubbed_method(self):
    raise test.TestingException()
self.stubs.Set(cls, 'inner_method', stubbed_method)

obj = cls()
self.assertRaises(test.TestingException, obj.outer_method)

Stubbing and Mocking

Whenever possible, tests SHOULD NOT stub and mock out the same function.

If it's unavoidable, tests SHOULD define stubs before mocks since the TestCase cleanup routine will un-mock before un-stubbing. Doing otherwise results in a test that leaks stubbed functions, causing hard-to-debug interference between tests1.

If a mock must take place before a stub, any stubs after the mock call MUST be manually unset using self.cleanUp calls within the test.