6608e63b19
This commit adds functional tests for the db api. It is still a rough implementation right now, but to start I'm not worried about that too much since it works. Things will just be a bit slow, because it drops the db and runs the migrations on an empty db on each test method, locks against every other api test method and the migration tests, and requires a local mysql db exist with the hardcoded values from the migration opportunistic test functions. But it works! Ideally we would just use the in memory sqlite db for this testing since it provides the isolation we really desire for running individual tests. However, because the migrations don't work on sqlite this makes it kinda difficult. To mitigate the locking penalty a bit a group regex is added to the testr.conf to serialize tests at the class level. This will at least mean that api tests will run serially since they're all in the same class. In an effort to decrease code duplication as part of adding additional DB functional tests the existing migration tests are refactored to use a common set of fixtures and util methods to handle the test db setup and connection configuration information. We also should slowly ramp up the number of tests here since the coverage is very basic as this was intended to mostly start the framework. But that, can be a follow up patch. Change-Id: Iea6dd86498002ab20977b5fb02b4c7d751a08bca
13 lines
183 B
Plaintext
13 lines
183 B
Plaintext
hacking>=0.9.2,<0.10
|
|
coverage>=3.6
|
|
discover
|
|
fixtures>=0.3.14
|
|
mock>=1.0
|
|
sphinx>=1.1.2,<1.2
|
|
testscenarios>=0.4
|
|
testrepository>=0.0.18
|
|
testtools>=0.9.34
|
|
oslosphinx
|
|
MySQL-python
|
|
psycopg2
|