OpenStack Database As A Service (Trove)
aeadbfc974
Add generic integration tests for instance create. Also moved some global constants to the base runner. Note: Did some additional cleanup work on other test groups as well. Broke down some negative tests into more self-contained units. Added a comment string on tests that did not have it. Had to fix database_actions test to work for users defining hosts (like MySQL users). Change-Id: I7c1413fa5742c276454e26ebbbeae8e02569a392 |
||
---|---|---|
apidocs | ||
contrib | ||
devstack | ||
doc | ||
etc | ||
tools | ||
trove | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
doc-test.conf | ||
generate_examples.py | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
requirements.txt | ||
run_tests.py | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Trove
Trove is Database as a Service for OpenStack.
Usage for integration testing
If you'd like to start up a fake Trove API daemon for integration testing with your own tool, run:
$ ./tools/start-fake-mode.sh
Stop the server with:
$ ./tools/stop-fake-mode.sh
Tests
To run all tests and PEP8, run tox, like so:
$ tox
To run just the tests for Python 2.7, run:
$ tox -epy27
To run just PEP8, run:
$ tox -epep8
To generate a coverage report,run:
$ tox -ecover
(note: on some boxes, the results may not be accurate unless you run it twice)
If you want to run only the tests in one file you can use testtools e.g.
$ python -m testtools.run trove.tests.unittests.python.module.path