You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Team,
could you please let me know what is the use of healthyTarget, unhealthyTarget and failingTarget in clover report. How does this impact graphical presentation of code coverage ?
Hi Gaurav,
I'm not an expert on this, but it appears these define the thresholds for what you'd deem healthy, unhealthy and failing from a coverage point of view. For example you might say a 50% method coverage is failing, 70% is unhealthy, and 80% is healthy.
Some more clues can be found here: https://stackoverflow.com/questions/37454187/how-to-specify-clover-coveragetarget-metrics-in-jenkins-pipeline
yes that is true but I was wondering how these thresholds are impacting clover report as I don't see like healthy or unhealthy notification in my test coverage report. So what is the significance then ? I mean if I put 60% instead of 70% for healthy threshold, how my report is going to be impacted ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's a good question, and one where I'd definitely be guessing. Perhaps it sends back an overall flag of the health of the coverage in the report corresponding with the targets, or sets an exit code.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.