Merge lp:~rockstar/launchpad/use-suspended-job-status into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Jeroen T. Vermeulen on 2010-01-12 |
| Approved revision: | not available |
| Merged at revision: | not available |
| Proposed branch: | lp:~rockstar/launchpad/use-suspended-job-status |
| Merge into: | lp:launchpad |
| Prerequisite: | lp:~rockstar/launchpad/job-suspended-status |
| Diff against target: |
258 lines (+175/-3) 4 files modified
lib/lp/soyuz/configure.zcml (+1/-1) lib/lp/soyuz/interfaces/archive.py (+6/-0) lib/lp/soyuz/model/archive.py (+35/-1) lib/lp/soyuz/tests/test_archive.py (+133/-1) |
| To merge this branch: | bzr merge lp:~rockstar/launchpad/use-suspended-job-status |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Jeroen T. Vermeulen (community) | code | 2010-01-12 | Approve on 2010-01-12 |
|
Review via email:
|
|||
| Paul Hummer (rockstar) wrote : | # |
| Jeroen T. Vermeulen (jtv) wrote : | # |
Went over this in IRL.
Some small superficial points—mainly indentation of query text, and XXXes to factor duplicated setup out into helpers.
Also, instead of a test method "assert that there are no builds with status X" it's probably more helpful to have one that returns whether there are any builds with status X, and use that for assertions directly in your tests. Two advantages:
* A failure shows up at the bottom of its stack trace, not in a generic method where you have to browse further up the trace to get to the semantic failure.
* You can show before/after comparisons very effectively. That can help separate bad test setup (which also sometimes tells you what you want to hear) from the change you're really testing for.
With those notes, r=me.
Jeroen

Hi Jeroen-
This branch just adds an IArchive.enable and IArchive.disable method to the
IArchive to appropriately tests it.
Paul