Bug 1042953 - [RFE][oslo]: Run DB API tests on a given DB backend
Summary: [RFE][oslo]: Run DB API tests on a given DB backend
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/oslo...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 16:46 UTC by RHOS Integration
Modified: 2015-03-19 17:19 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:19:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-13 16:46:48 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/tests-given-db-backend.

Description:

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/

Specification URL (additional information):

None
Note You need to log in before you can comment on or make changes to this bug.