coveralls
commented
6 years ago Pull Request Test Coverage Report for Build 390
- 129 of 175 (73.71%) changed or added relevant lines in 2 files are covered.
- 3 unchanged lines in 1 file lost coverage.
- Overall coverage increased (+8.9%) to 37.976%
| Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
|---|---|---|---|---|---|
| sktm/reporter.py | 125 | 143 | 87.41% | ||
| sktm/executable.py | 4 | 32 | 12.5% | ||
| <!-- | Total: | 129 | 175 | 73.71% | --> |
| Files with Coverage Reduction | New Missed Lines | % | ||
|---|---|---|---|---|
| sktm/executable.py | 3 | 16.24% | ||
| <!-- | Total: | 3 | --> |
| Totals | |
|---|---|
| Change from base Build 382: | 8.9% |
| Covered Lines: | 463 |
| Relevant Lines: | 1095 |
veruu
Test with commands like
sktm -vv --mail-from me --mail-to someone report --assets dir-with-resultswhere
dir-with-resultsis a directory containing stage results (which are not yet implemented in skt, so you'll need to create your own ones for testing purposes). Examples of content:build.log build.report build.result merge.report merge.resultorapplied.patch merge.report merge.result s390/ x86/wheres390/containsbuild.report build.result config.gz kittyandx86/containsbuild.report build.result useless-fileFrom the examples,
useless-fileis not referenced in the report text so it's not added,config.gz,applied.patchandkittyare referenced and added as attachments.I'll add a proper directory structure definition to meta/pull6 so it's less confusing but I wanted to publish the code here before the weekend.