Merge lp:~anybox/openobject-server/7.0-test-report into lp:openobject-server/7.0
Status: | Needs review |
---|---|
Proposed branch: | lp:~anybox/openobject-server/7.0-test-report |
Merge into: | lp:openobject-server/7.0 |
Diff against target: |
142 lines (+45/-17) 4 files modified
openerp/modules/loading.py (+12/-4) openerp/tools/assertion_report.py (+12/-4) openerp/tools/convert.py (+12/-8) openerp/tools/yaml_import.py (+9/-1) |
To merge this branch: | bzr merge lp:~anybox/openobject-server/7.0-test-report |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
OpenERP Core Team | Pending | ||
Review via email: mp+208008@code.launchpad.net |
Description of the change
Simple way to have assertion_report record more information.
Here is the output I get after deliberately breaking a YML test file in the crm module, with ``oe initialize -d tmp --tests --module crm``, from the branch at lp:~anybox/openerp-command/7.0-initialize-test-report
(...long log...)
2014-02-24 20:17:15,303 3680 INFO tmp openerp.osv.orm: Computing parent left and right for table res_partner_
FAIL : 1 failure(s) or error(s) have been recorded
Module crm, in test file u'test/
test: state == "pendinsg"
values: ! pending == pendinsg
Unmerged revisions
- 5247. By Georges Racinet <email address hidden>
-
[FIX] platform independency by using openerp.
module. module API - 5246. By Georges Racinet <email address hidden>
-
[IMP] Improved reporting of test failures
While loading modules with the tests option, it's useful to have a report that
display test problems separately from the main log. It's then up to the
launching system (for instance openerpcommand) to produce meaningful user
output.This would ease I hope the maintainers task in case of regressions by letting
them dispatch easily to people that happen to know the relevant modules
(together with the author of the commit that triggered the error)A corresponding patch for openerpcommand has already been uploaded.