Include the URL of your launchpad blueprint:
As a general policy we want to avoid requiring projects to use test base classes defined in libraries they do not control. Test fixtures are more composable, and easier to test themselves.
Copied from Providing Test Tools:
We originally created oslotest as a place to include the base class for all unit tests across all projects, to give the projects common behaviors in their test suites. Using a common base class is not always possible, however, when applications want to use their own base class and test fixture classes in ways that do not mix well. Multiple inheritance, in particular, is a problem because the order of setup and tear-down for test cases is harder to reason about.
Leaving BaseTestCase alone risks making it completely obsolete as projects drop its use due to issues with multiple inheritance.
The existing DeprecationWarning will not be changed other than to add the deprecation warning, so all existing users will continue to be able to use it until they move to the new fixtures.
Developers will need to create or update their own test base classes to use the desired fixtures. The old test case will not be removed for at least one cycle, to allow for migration time.
We will need unit tests for the new fixtures.
Target Milestone for completion: Liberty-2
See “Proposed change” above.
Each change will require updates to the API documentation for oslotest.
This work is licensed under a Creative Commons Attribution 3.0 Unported License. http://creativecommons.org/licenses/by/3.0/legalcode