Move runtime test resources into setup.cfg [extras]

testscenarios and testresources are only needed if you're using the
oslo.db testing fixtures downstream, otherwise you don't need this at
runtime in a deployment, so move them into the setup.cfg [extras] group.

If a consumer of oslo.db wants to use the db test fixtures then they
install oslo.db like 'sudo pip install oslo.db[fixtures]'.

This should trigger a major version bump for the library when it lands.

Closes-Bug: #1429233

Change-Id: I1a7c5b6a7b29cd3a50655f60606cc0b025400a96

1 files changed, 1 insertions, 1 deletions

diff --git a/tox.ini b/tox.ini
index 4f6bd72..f8603fa 100644
--- a/tox.ini
+++ b/tox.ini
@@ -14,7 +14,7 @@ whitelist_externals = bash
 install_command = pip install -U {opts} {packages}
 setenv =
    VIRTUAL_ENV={envdir}
-deps = -r{toxinidir}/requirements.txt
+deps = .[fixtures]
        -r{toxinidir}/test-requirements.txt
 commands = bash tools/pretty_tox.sh '{posargs}'