Merge lp:~anybox/openerp-command/trunk-pdb-tests-poc into lp:openerp-command
Proposed by
Georges Racinet
Status: | Needs review |
---|---|
Proposed branch: | lp:~anybox/openerp-command/trunk-pdb-tests-poc |
Merge into: | lp:openerp-command |
Diff against target: |
59 lines (+31/-1) 2 files modified
openerpcommand/run_tests.py (+11/-1) openerpcommand/test_result.py (+20/-0) |
To merge this branch: | bzr merge lp:~anybox/openerp-command/trunk-pdb-tests-poc |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
OpenERP Core Team | Pending | ||
Review via email:
|
Description of the change
This is a proof-of-concept implementation of post-mortem pdb for failures and errors.
The pdb related options are directly set on the TestResult subclass, which is a bit harsh and could be surprising for further developments, but that's good enough to demonstrate that it works.
A cleaner way would be to subclass TextTestRunner as well to pass options to PdbTextTestResu
If you'd prefer it that way, just tell me.
Cheers,
To post a comment you must log in.
Unmerged revisions
- 182. By Georges Racinet <email address hidden>
-
[IMP] options for pdb post-mortem debugging on failures and errors
This seems nice (I didn't try it).
Actually in the case of a failure, the stack wouldn't be much interesting (the stack would lead to the assertion error, not to the code at fault).
So this makes it possible to write it a bit more cleanly: just check a single --post-mortem flag, if it true, use your PdbTextTestResult, otherwise use the regular TextTestResult. (So no need to pass aroung the flag through class variables.)
Thanks!