Closed pyseed closed 5 years ago
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
cluster/cluster.py | 1 | 8 | 12.5% | ||
<!-- | Total: | 16 | 23 | 69.57% | --> |
Totals | |
---|---|
Change from base Build 32: | -1.09% |
Covered Lines: | 556 |
Relevant Lines: | 580 |
Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
cluster/cluster.py | 1 | 8 | 12.5% | ||
<!-- | Total: | 16 | 23 | 69.57% | --> |
Totals | |
---|---|
Change from base Build 32: | -1.09% |
Covered Lines: | 556 |
Relevant Lines: | 580 |
Files with Coverage Reduction | New Missed Lines | % | ||
---|---|---|---|---|
cluster/tests/test_migrate.py | 2 | 97.85% | ||
cluster/cluster.py | 4 | 97.74% | ||
<!-- | Total: | 6 | --> |
Totals | |
---|---|
Change from base Build 43: | 0.09% |
Covered Lines: | 653 |
Relevant Lines: | 672 |
Thanks for this works!
Do you mind to add a test case to improve coverall and avoid regression on this new features ?
I guess you can find inspiration how to do it from this check test test to assert consol output.
And you could probably reuse/refactor fill_data method.
Next evolution could be to add a --format option to let user choose wich fields to add per service, for instance it could be nice to display the deploy date or deploy id. But probably doing that in an other PR, what do you think about ?
Regards
Thanks for input.
Yes i will fix coverage in same PR, fields improvement will go in another PR.
@petrus-v Hi. coverage improved, PR candidate for a merge.
@petrus-v readme/changelog updated, PR candidate for merge
LGTM, thanks for that feature
Pull Request Test Coverage Report for Build 33
💛 - Coveralls