Ensure all SQL driven unit tests can run against all supported RDBMS
Different databases have different requirements. We need to ensure that the codes doesn't break any of the systems. Right now, unit test are only runnable against sqlite. To run against PostgreSQL and MySQl, for each one :
1. Create a new schema/table namespace. For Mysql, this will involve running
mysql
create database keystone-unit-test
and for postgres it will involve running
sudo -u postgres createdb keystone-unit-test
In both cases, it will have to drop the database at the end of the unit tests:
for mysql
mysql ; drop dtabase keystone-unit-test
and for postgres:
sudo -u postgres dropdb keystone-unit-test
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Adam Young
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
The bp only addresses mysql and postgres but the title of the bp is "all DBs", which is a completely unrealistic goal. I'd suggest creating more specific blueprints targeted at whatever configuration you want to test against, and WHAT you want to be tested (e.g. keystoneclient_sql tests? v3 API tests? migration tests? etc)
