Unit tests should not require server(s) to be started
Bug #843182 reported by
klmitch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Unit tests do not need to have the keystone and other servers started up in order to test the code paths.
I'm going to refactor the unit tests in the following way:
a) Remove need to have a Keystone server up and running
b) Use base test classes for handling creation of fixtures
c) Have tests runnable with a simple call to $> nosetests
d) All fixtures should be created with the DB API, not the HTTP API
e) Remove all the unnecessary munging of sys.paths in each test file (nose can handle this for ya)
Expect a pull request sometime today. :)
-jay
Revision history for this message
| klmitch (q-noreply) wrote | #1 |
Revision history for this message
| klmitch (q-noreply) wrote | #2 |
Revision history for this message
| klmitch (q-noreply) wrote | #3 |
Revision history for this message
| klmitch (q-noreply) wrote | #4 |
To post a comment you must log in.
Awesome! Kevin also started plugging in `dtest`. Try this from test/functional:
./run_tests.py -u admin -p secrete -D -k http://
but I think he said dtest and nose are compatible (or he was making them so). Any thoughts?