test_backend classes not always run in the test_backend_* module
Bug #1334408 reported by
Morgan Fainberg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Invalid
|
Low
|
Unassigned | ||
Bug Description
The various classes defined in test_backend module do not always get a subsequent class in the test_backend_* module. There should be a better way to ensure that a given suite of tests is run against any/all backends (could this be done with fixtures).
This is another bug in the long-line of restructuring the testing to be better within Keystone.
| Changed in keystone: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Dolph Mathews (dolph) wrote | #1 |
| Changed in keystone: | |
| importance: | Wishlist → Low |
| status: | New → Triaged |
| tags: | added: test-improvement |
Revision history for this message
| Morgan Fainberg (mdrnstm) wrote | #2 |
| Changed in keystone: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
FWIW, I try to save "Wishlist" for user-facing things, and use Low for dev-facing improvements, etc.