Add a public DB fixture that will be usable without DbTestCase

Registered by Roman Podoliaka on 2015-02-24

Currently DbFixture can only be used together with DbTestCase or one of its subclasses. Using of inheritance to inject engine/session functionality might be problematic in target projects as they tend to use their own base test case classes, which can possibly conflict with DbTestCase.

A DB fixture should be usable on its own, so that target projects would be able to directly use it in their setUp() methods instead of relying on inheriting from DbTestCase.

A new fixture class will be introduced to fix this problem, original DbFixture will be made private and DbTestCase will be marked as deprecated and eventually removed in a few releases of oslo.db.

Blueprint information

Status:
Not started
Approver:
Doug Hellmann
Priority:
Undefined
Drafter:
Roman Podoliaka
Direction:
Approved
Assignee:
Roman Podoliaka
Definition:
New
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

We discussed this in IRC on 24 Feb 2015 and agreed that unless the folks working on it need a spec we would just track with a blueprint. - dhellmann (see 2015-02-24T13:32:51 in http://eavesdrop.openstack.org/irclogs/%23openstack-oslo/%23openstack-oslo.2015-02-24.log)

You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.