Merge lp:~jml/testtools/wrap-result-in-concurrent-suite into lp:~testtools-committers/testtools/trunk
| Status: | Merged |
|---|---|
| Merged at revision: | 251 |
| Proposed branch: | lp:~jml/testtools/wrap-result-in-concurrent-suite |
| Merge into: | lp:~testtools-committers/testtools/trunk |
| Diff against target: | 0 lines |
| To merge this branch: | bzr merge lp:~jml/testtools/wrap-result-in-concurrent-suite |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| testtools committers | 2012-04-13 | Pending | |
|
Review via email:
|
|||
Description of the Change
From talking with Benji, it looks like they need to be able to wrap up the per-thread results in ConcurrentTestSuite so that they can tag the tests in those results. This branch adds a hook.
I'm not 100% convinced by this change. I think that perhaps the only valid use is (once https:/
def _wrap_result(self, per_thread_result, thread_number):
return Tagger(
And so we might as well do that. On the other hand, the approach in this branch feels a little more "small pieces, loosely joined".
- 253. By Jonathan Lange on 2012-04-13
-
pyflakes
- 254. By Jonathan Lange on 2012-04-17
-
Parametrize wrap_result, rather than relying on inheritance.
- 255. By Jonathan Lange on 2012-04-17
-
Better docs
