summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_controller.js
diff options
context:
space:
mode:
authorXavier Morel <xmo@odoo.com>2020-07-23 08:13:50 +0000
committerXavier Morel <xmo@odoo.com>2020-07-27 09:30:51 +0000
commit92903e22f893f569d4cce0214b4adef82c2fe825 (patch)
treeac5e06d7d0878008e6cae3f2abb2b4442757da8e /addons/web/static/src/js/views/basic/basic_controller.js
parent297c3d83785453b6a273af324a955d9d038e989d (diff)
[IMP] core: reporting after tests
Currently there are a few issues with testing reporting (at the command-line): 1. there is a global report after at_install tests, but it gets "scrolled off" by long post_install tests, and is thus easy to miss 2. with test tags, it's easy to fat finger a typo and run 0 tests, which look like everything's running fine (no failure) To improve this, print a global report at shutdown (in `--stop-after-init` mode if tests are enabled) which recapitulates the test results *and prints a warning if no tests were run at all*. Also update the reporting collection to make this more reliable: * have `run_unit_tests` return `None` if it has run no tests, the assertion reporting machinery counts this as neither success nor failure which is exactly what we want * have load_test only report a success *if files were actually loaded* (by having `load_data` return that information) Task 2301268 closes odoo/odoo#54812 Signed-off-by: Xavier Morel (xmo) <xmo@odoo.com>
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions