ae2d9ecf67
Currently the SSH user and private key is assumed to be taken from the local account (e.g., /home/ubuntu/.ssh). This change proposes to add 2 environment variables so that a tox test of Trove can use an arbitrary SSH user and key file for testing. Obviously, this assumes that the test setup has already installed those credentials in the image under test. Change-Id: Ibc83cb7fcd291a13706550965fe2dd1d5ca3504e Closes-Bug: 1469775
Trove
Trove is Database as a Service for Open Stack.
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