Restructure Tests
Keystone already has a great test suite. When I started on the project I was surprised to find it better than most
closed source/corporate test suites I have worked with. I do, however, think that we can make it even better.
Tests are very important for a variety of reasons. IME the two that are most important are:
Making sure the system works (a verification tool)
Helping new developers understand the system (an education tool)
To be a verification and educational tool the tests have to be well organized and well factored. In other words
there should only be a single, easy to find test showing for a particular part of Keystone works.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- David Stanek
- Direction:
- Approved
- Assignee:
- David Stanek
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Steve Martinelli
Related branches
Related bugs
Sprints
Whiteboard
(morganfainberg) 2014-10-17: This is something we should absolutely do. I do not know if a formal spec is really needed in this case.
(stevemar) 2016-02-02: we've done a lot of restructuring of our tests in keystone, i'm marking this as superseded, if there is additional work to be done here, simply post the code, no need for a blueprint
