Merge lp:~jtv/maas/test-before-landing-bitch into lp:maas/trunk
| Status: | Merged |
|---|---|
| Approved by: | Jeroen T. Vermeulen on 2012-06-05 |
| Approved revision: | 608 |
| Merged at revision: | 608 |
| Proposed branch: | lp:~jtv/maas/test-before-landing-bitch |
| Merge into: | lp:maas/trunk |
| Diff against target: |
33 lines (+3/-5) 2 files modified
src/maasserver/testing/factory.py (+1/-2) src/maasserver/tests/test_nodegroup.py (+2/-3) |
| To merge this branch: | bzr merge lp:~jtv/maas/test-before-landing-bitch |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Julian Edwards (community) | 2012-06-05 | Approve on 2012-06-05 | |
|
Review via email:
|
|||
Commit Message
Fix test breakage, lint, and mis-formatted imports.
Description of the Change
The NodeGroup branch broke our build. Not when you ran its tests in isolation, but definitely when you ran the whole test suite. The reason is that the NodeGroup test case was derived from maastesting.
There was also some lint, and the imports formatting tool had apparently not been run. Tsk, tsk.
Lessons to be learned:
* Stop the proliferation of TestCase classes. If it must be a TestCase-
* Always run “make check” on a branch before landing it.
* A warning about this in the template for our python tests may help.
* “make lint” and “./utilities/
Jeroen
| Julian Edwards (julian-edwards) wrote : | # |


* Stop the proliferation of TestCase classes. If it must be a TestCase- derivative, give it an obvious name.
For the love of $DEITY, YES YES YES.