Our current approach to testing has some awesome benefits. Namely, anyone can install the Marconi core package, and start writing their own third-party drivers, and utilize the base test classes which offer great conformance tests.
However, there is a devious problem. Currently, there is no easy way to define methods that can be overridden by children test classes short of the author exposing their own X{Queue, Messages, Claims}ControllerTest classes, where X is the storage backend. Also, recently, a bug was patched (https://review.openstack.org/#/c/59539) that as a result of the diamond inheritance problem introduced by a Mixin class, would cause the Mongodb storage suite to consume ~19GB per run.
The goal here is twofold, and it's all refactoring:
1. Make it possible to expose methods that can be overridden easily in some base class (_purge_databases, _prepare_conf, etc.)
While...
2. Keeping things extensible and making it difficult to encounter the diamond problem.
"There should be one-- and preferably only one --obvious way to do it."
Fix proposed to branch: master
Review: https:/