Merge lp:~javier.collado/utah/add_client_include_exclude_tests into lp:utah
Proposed by
Javier Collado
Status: | Merged |
---|---|
Approved by: | Javier Collado |
Approved revision: | 716 |
Merged at revision: | 715 |
Proposed branch: | lp:~javier.collado/utah/add_client_include_exclude_tests |
Merge into: | lp:utah |
Diff against target: |
126 lines (+87/-3) 2 files modified
utah/client/tests/test_runner.py (+36/-3) utah/client/tests/test_testsuite.py (+51/-0) |
To merge this branch: | bzr merge lp:~javier.collado/utah/add_client_include_exclude_tests |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Joe Talbott (community) | Approve | ||
UTAH Dev | Pending | ||
Review via email:
|
Description of the change
This branch verifies include/exclude features by adding some test cases.
- In the runner, a test case is added to make sure that whatever is written
in the master run list in the include_
to the test suite objects using include/exclude parameters.
- In the test suite, a few test cases make sure that the test case selection
is based on the information passed through the include/exclude parameters.
To post a comment you must log in.
Looks good to me.
I haven't used mock before so I'm not sure what is happening there. You could just as easily inspect the testsuites in the runner and verify that the tests are what you expect them to be.