Bug 1042953

Summary:	[RFE][oslo]: Run DB API tests on a given DB backend
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/oslo/+spec/tests-given-db-backend
Whiteboard:	upstream_milestone_none upstream_status_needs-code-review upstream_definition_review
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:19:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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