Merge lp:~lifeless/launchpad/registry into lp:launchpad
| Status: | Merged | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Approved by: | Michael Hudson-Doyle on 2010-08-05 | ||||||||||||||||
| Approved revision: | no longer in the source branch. | ||||||||||||||||
| Merged at revision: | 11298 | ||||||||||||||||
| Proposed branch: | lp:~lifeless/launchpad/registry | ||||||||||||||||
| Merge into: | lp:launchpad | ||||||||||||||||
| Diff against target: |
182 lines (+53/-40) 4 files modified
lib/lp/registry/tests/test_listteammembers.py (+0/-6) lib/lp/registry/tests/test_person.py (+7/-8) lib/lp/testing/_webservice.py (+43/-0) lib/lp/translations/stories/standalone/xx-pofile-translate-performance.txt (+3/-26) |
||||||||||||||||
| To merge this branch: | bzr merge lp:~lifeless/launchpad/registry | ||||||||||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Hudson-Doyle | 2010-08-05 | Approve on 2010-08-05 | |
|
Review via email:
|
|||
Commit Message
Factor out QueryCounter from the rosetta tests for reuse and cleanup a couple of registry tests.
Description of the Change
Some minor test cleanups from my performance day dive.
| Robert Collins (lifeless) wrote : | # |
13:19 < lifeless> I looked for it
13:19 < lifeless> but found QueryCounter
13:19 < lifeless> oh yay two totally different ways of doing the same thing.
13:19 < lifeless> uhm
13:20 < lifeless> sigh, thanks.
13:20 < lifeless> I think my refactoring is not harmful
13:20 < lifeless> in fact, I think QueryCounter is useful because its
aimed directly at the request, not at the storm layer
13:20 < lifeless> so its useful for 'is this page request going to be ok'
13:20 < lifeless> which, record_statements on allmembers is not a good
answers for
| Michael Hudson-Doyle (mwhudson) wrote : | # |
We talked about this a bit on IRC.
Happy for the branch to land as is. A colon seems to have become misplaced in QueryCounter.

Have you seen assertStatement Count on lp.testing. TestCase? It's a bit different, but more direct and general (I imagine get_request_ statements( ) uses a storm trace hook at some level), and I wonder if that should be the approach we aim to promote and generalize?
The test cleanups look fine.