diff options
author | Mark McLoughlin <markmc@redhat.com> | 2013-06-10 14:01:19 +0100 |
---|---|---|
committer | Mark McLoughlin <markmc@redhat.com> | 2013-06-25 07:23:51 +0100 |
commit | 1667648b7e812db026933b0075e14f2ab1f1c70b (patch) | |
tree | 92183533e69cfc3725a1d1c5312529ad9e3fc501 /tox.ini | |
parent | bc10b7aeada4ea66e85e10b94b5c219e3c8d2e77 (diff) | |
download | oslo-1667648b7e812db026933b0075e14f2ab1f1c70b.tar.gz oslo-1667648b7e812db026933b0075e14f2ab1f1c70b.tar.xz oslo-1667648b7e812db026933b0075e14f2ab1f1c70b.zip |
Allow BaseTestCase use a different conf object
The new messaging work will register options like rpc_backend and, since
the existing RPC API registers those options with CONF, we need to run
the messaging tests with a different ConfigOpts object.
It's actually probably pretty sane for all unit tests to use a per-test
ConfigOpts object rather than cfg.CONF anyway.
The kombu and zmq tests have an issue with this where they rely on being
able to call self.config() before the base class setUp() is called.
Fixing this properly is a little tricky, so for now, initialize
self.conf early to cfg.CONF just for these tests.
Change-Id: I7b2e3db7c21c511f3ab16ac866e0cc80846cbd80
Diffstat (limited to 'tox.ini')
0 files changed, 0 insertions, 0 deletions