Change-Id: I6dac94a98b9125d3371c19fa14a0de9b4e766820 Signed-off-by: Zane Bitter <firstname.lastname@example.org>
|11 years ago|
|fake||11 years ago|
|README.rst||11 years ago|
|__init__.py||11 years ago|
|runner.py||11 years ago|
Heat Testing Infrastructure
A note of clarification is in order, to help those who are new to testing in Heat:
- actual unit tests are created in the "tests" directory;
- the "testing" directory is used to house the infrastructure needed to support testing in Heat.
This README file attempts to provide current and prospective contributors with everything they need to know in order to start creating unit tests and utilizing the convenience code provided in nova.testing.
Test Types: Unit vs. Functional vs. Integration
Writing Unit Tests
The TestCase class from heat.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 overriden.
Writing Functional Tests
Writing Integration Tests
Tests and assertRaises
When asserting that a test should raise an exception, test against the most specific exception possible. An overly broad exception type (like Exception) can mask errors in the unit test itself.