Go to file
Peter Stachowski c72b2463a4 Cap test_log_generator_user_by_row to 100
For some datastores (for example postgreSQL), the guest-log scenario
test test_log_generator_user_by_row can take an inordinate amount of
time, since a lot of data is written into the user log once it is
enabled. This test should be capped so that an extremely large log file
won't cause the tests to time out.

Change-Id: Ie10c5cc4d5390013d111aef27991a747ac2ff795
Closes-Bug: #1559214
2016-03-18 16:32:36 +00:00
2016-02-03 11:26:52 -05:00
2015-05-29 07:27:59 +00:00
2014-12-02 09:57:52 +01:00
2013-06-24 14:11:15 -07:00
2013-06-14 18:25:42 -04:00
2013-06-24 14:11:15 -07:00
2014-03-19 15:06:23 +01:00
2015-02-04 11:10:28 -08:00
2015-05-29 07:27:59 +00:00
2013-04-29 18:01:12 -04:00
2013-06-25 10:41:57 +02:00
2015-11-19 10:25:01 +00:00
2015-09-23 14:14:17 +00:00
2016-03-08 21:12:11 -05:00

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
Description
OpenStack Database As A Service (Trove)
Readme 117 MiB
Languages
Python 95%
Shell 4.9%