Run DB API tests on a given DB backend

Registered by Ilya Pekelny on 2013-09-16

The DB API tests run only on SQLite engine. DB API have engine specific bugs and features. Furthermore on production very rarely using SQLite but more often it is MySQL and PostgreSQL engines. So current API can have untested side effects on different DB backends. Thus at testing specific bug fixes and features required to run tests with different backends.
Could be solved in two different ways. First way: user defined database admin uri contained in env variable used to get database access, temporary test database created at every test run, backend specific tests skips at inappropriate backends. Second way: backend specific test cases must be inherited from special test case which use concrete backend for all defined tests, using default ci database aka "openstack_citest".
Inspired by: https://review.openstack.org/#/c/33236/

Blueprint information

Status:
Started
Approver:
Doug Hellmann
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Ilya Pekelny
Definition:
Review
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Ilya Pekelny on 2013-11-04

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/tests-given-db-backend,n,z

Addressed by: https://review.openstack.org/47818
    The ability to run tests at various backend

Gerrit topic: https://review.openstack.org/#q,topic:bug/1224898,n,z

Gerrit topic: https://review.openstack.org/#q,topic:Db_Fixtures,n,z

Addressed by: https://review.openstack.org/54375
    Opportunity to use default ci database for testing

Addressed by: https://review.openstack.org/56620
    SQLite behavior independent DB test cases

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.