Tryton - Issues



Title Add coverage report
Priority feature Status in-progress
Superseder Nosy List ced, pokoli, reviewbot
Type feature request Components
Assigned To ced Keywords review
Reviews 51501002
View: 51501002

Created on 2018-09-07.12:35:28 by ced, last changed by pokoli.

review51501002 updated at
msg43758 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-09-07.12:57:41
Here is review51501002 which adapt some main component and some modules.
msg43757 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2018-09-07.12:35:27
Even if I do no think that 100% coverage is not a goal and that the coverage value does not provide really a good metric, a low coverage tells something.
So I think coverage report could help to detect part of the code that could have some more tests. But such report should not be in any case a cause of failure.
I propose to run tox test with coverage and print the report for the tested module.
Date User Action Args
2018-11-06 18:54:14pokolisetnosy: + pokoli
2018-09-07 13:25:08reviewbotsetnosy: + reviewbot
messages: + msg43759
2018-09-07 12:57:41cedsetreviews: 51501002
messages: + msg43758
keyword: + review
2018-09-07 12:35:28cedcreate

Showing 10 items. Show all history (warning: this could be VERY long)