Overall analytics number seems wrong #129
-
|
There is something wrong with the "overall number" from codecov. I started investigating because I could not understand how our main number fluctuated like that. 
Based on the numbers of tracked lines and the % of tracked lines I calculated the total number of lines covered by tests 
I get so my question is: where are you getting Is there a way to see the overall code coverage across all repos ( |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hi @mathiasrw, I'm one of the product managers at Codecov, I appreciate your deep dive here. Each data point on the graph is a one week bucket showing a max. This means that if you select a couple of repos, the data point on the chart will be the highest coverage number from any commit within those repos within the week. Your confusion is merited here, the way the chart is built sort of implies that we're aggregating data in some way when that isn't really the case. As to your final question, there isn't a great way to see an overall number of coverage across commits without some outside of the UI work. This particular area of the product is ripe for some improvement and I'd love to hear more about how you want to use this as well as more generally how your code base is setup (monorepo? microservices? something else?). Happy to jump on a call as well if you'd prefer. |
Beta Was this translation helpful? Give feedback.
-
|
Sure. Shoot me an email on [email protected] so we can find a suitable time. |
Beta Was this translation helpful? Give feedback.
-
|
@aj-codecov how do I reach you? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mathiasrw Apologies for the delay, just shot you an email with a few times! |
Beta Was this translation helpful? Give feedback.
-
|
Can we pick this up again? |
Beta Was this translation helpful? Give feedback.
Hi @mathiasrw, I'm one of the product managers at Codecov, I appreciate your deep dive here. Each data point on the graph is a one week bucket showing a max. This means that if you select a couple of repos, the data point on the chart will be the highest coverage number from any commit within those repos within the week. Your confusion is merited here, the way the chart is built sort of implies that we're aggregating data in some way when that isn't really the case. As to your final question, there isn't a great way to see an overall number of coverage across commits without some outside of the UI work.
This particular area of the product is ripe for some improvement and I'd love to hear …