67adc87e92
Unhandled logging messages generated from sources other than Trove's tests were flooding the log with numerous messages that included complete backtraces. These backtraces are over 150mb when you run tox -e py27. Unfortunately, while they are an indication of a problem, they are most often not things that can be fixed in the Trove project. To fix this, at least in the short term, this change only reports anything if the logged message is coming from the context of a test. Also, this change disables back traces in the messages being reported unless an optional enables_backtrace is set. By default it set to False and can only be enabled with a code change (i.e. no configuration setting). Change-Id: I9452f03bdd5365991e3c4831aa4936de3713612e Closes-Bug: 1521373 |
||
|---|---|---|
| apidocs | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc | ||
| releasenotes | ||
| tools | ||
| trove | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| babel.cfg | ||
| doc-test.conf | ||
| generate_examples.py | ||
| requirements.txt | ||
| run_tests.py | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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.shStop the server with:
$ ./tools/stop-fake-mode.shTests
To run all tests and PEP8, run tox, like so:
$ toxTo run just the tests for Python 2.7, run:
$ tox -epy27To run just PEP8, run:
$ tox -epep8To 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