Build should fail if we don't reach up to the desired code-coverage
Note: we will not have code climate until we go public so we use only cobertura for now
Implemented Changes
Examine the cobertura properties:
In some properties you will see a tripled tuple:
for example lineCoverageTargets: '70, 80, 70'
The first value is threshold, second is health and third is stability
Added a cobertura validation and reporting to jenkins mechanism
output the results to junit format
Definition of Done
Show our tests coverage in jenkins
Fail in case we are lower than the desired threshold
Changelog
[ ] The CHANGELOG has been updated, or
[x] This PR does not include user-facing changes and doesn't require a
CHANGELOG update
Test coverage
[ ] This PR includes new unit and integration tests to go with the code
changes, or
[x] The changes in this PR do not require tests
Documentation
[ ] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: [insert issue ID]()
[x] This PR does not require updating any documentation
Behavior
[ ] This PR changes product behavior and has been reviewed by a PO, or
[ ] These changes are part of a larger initiative that will be reviewed later, or
[x] No behavior was changed with this PR
Security
[ ] Security architect has reviewed the changes in this PR,
[x] These changes are part of a larger initiative with a separate security review, or
[ ] There are no security aspects to these changes
Desired Outcome
Build should fail if we don't reach up to the desired code-coverage Note: we will not have code climate until we go public so we use only cobertura for now
Implemented Changes
Examine the cobertura properties: In some properties you will see a tripled tuple: for example
lineCoverageTargets: '70, 80, 70'
The first value is threshold, second is health and third is stabilityDefinition of Done
Changelog
Test coverage
Documentation
README
s) were updated in this PRBehavior
Security