f7cda9912d
pymongo version 3.1 produces segmentation faults when running unit tests and has broken the trove gate, see bug 1512870. This is one part of the solution, the other part of the solution is to push the change to global-requirements.txt. That's in the review https://review.openstack.org/#/c/290233/2 Change-Id: I0ac00931cc696e53f1845b60c23f84c9846a6a5e Depends-On: I94dd0d031bb2c6ecae45ec9482cc2f481e77ce03 Closes-Bug: 1554838 Related-Bug: 1512870
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