Consolidate Testing Infrastructure
One of the outcomes of Soren's email to the OpenStack list about testing for essex was a desire to consolidate testing infrastructure in the interest of speeding up unit tests and making it more clear for contributors regarding how to create unit tests for Nova and best practices for testing.
Blueprint information
- Status:
- Complete
- Approver:
- Soren Hansen
- Priority:
- Low
- Drafter:
- Nova Testing Cleanup Team
- Direction:
- Approved
- Assignee:
- Duncan McGreggor
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Deferred
- Milestone target:
- None
- Started by
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
The following items have been proposed for development:
[oubiwann] create a new subpackage, nova.testing, to house nova testing infrastructure: DONE
[oubiwann] move the test runner code into this module (and have the shell script call it directly, via "python nova.testing.
[oubiwann] move the top-levell fake*.py modules into testing: DONE
[oubiwann] create a document for describing how to best use nova.testing at nova/testing/
[oubiwann] moving nova.test to nova.testing.base: TODO
[oubiwann] moving other fakes in various subpackages into nova.testing.fake: INPROGRESS
[oubiwann] removing redundancies in testing base classes: TODO
[oubiwann] creating new testing base classes, as required for ease of maintenance and contributions: TODO
[oubiwann] separating out functional tests from unit tests -- this will likely be a large task, and thus might spawn per-module work-items: TODO
[oubiwann] update nova/testing/
[oubiwann] remove the blueprint link and WIP caveat from nova/testing/
Gerrit topic: https:/
Addressed by: https:/
First steps towards consolidating testing infrastructure
