Refactor chaotic test codes

Registered by Haomai Wang on 2013-09-06

Trove has a complete different test code style with other OpenStack core projects which cause the developers confused. It really block other OpenStack project developers to join Trove. Besides the author of test codes, no one could have a clear mind on these in short time.

We need to refactor the test codes which have following features:
1. the test codes are interdependent
2. the test codes exist magic connection
3. the test codes are dirty and make others confused

Blueprint information

Status:
Complete
Approver:
Michael Basnight
Priority:
High
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
Accepted for future
Implementation:
Informational Informational
Milestone target:
milestone icon ongoing
Started by
Nikhil Manchanda on 2014-06-09
Completed by
Nikhil Manchanda on 2014-06-09

Related branches

Sprints

Whiteboard

i'd suggest to avoid using keystone as an example to follow in this regard ;) -dolph
lol

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.