Go to file

Mike Bayer 4522a9728e Break optimize_db_test_loader into package and module level

This unittest-compatible load_tests function was not
well organized for package-level tests and was broken
for module-level usage; as in the case of module-level usage,
the "pattern" parameter was being passed, which was unexpected
since the Python 2.7 documentation for unittest claims it will
be None.  However, we are using subunit to run tests, which
uses the unittest2 library that achieves compatibility with
Python 3 - in Python 3, the documentation was changed here
to note that "pattern" may be present (and in fact it is).

Instead, break it into optimize_package_test_loader and
optimize_module_test_loader.  The former assumes placement
inside of __init__.py only and the latter assumes placement
inside of a specific module only.

The issue with this function was observed when trying to get
OptimisingTestSuite to work correctly with neutron; tests
would be duplicated due to the double-search.  In local testing
it was shown that the function could cause recursion overflows.

It has been observed that using this function at the module level
is of great use when running subsets of tests, since the package-level
load_tests function is not consulted unless the test run is package-wide.

Change-Id: I267fd2fbc16504c11addef870fc8d4fc500da7d9

2016-11-16 15:41:01 -05:00

doc/source

Make it possible to use enginefacade decorators with class methods

2016-06-27 17:22:01 +03:00

oslo_db

Break optimize_db_test_loader into package and module level

2016-11-16 15:41:01 -05:00

releasenotes

Merge "utils: deprecate InsertFromSelect properly"

2016-11-10 19:03:52 +00:00

tools

Allow testing of MySQL and PostgreSQL scenario locally