Code Coverage for System Tests

Not sure if the line was not covered, because if it was not covered it should be red. Do you get a "counter" when you hover over the line?

For the details on how the overall coverage is exactly calculated, best have a look at the source code of the coverage generation tool code. I remember we had on Github some discussions about this about a year ago related to codecov as they did the calculation in a different way but I couldn't find it anymore :frowning: I never digged into the details of the exact calculation as there are many different ways on doing it and for us the coverage is more an indicator value and it does not matter too much if it is 72.2 or 73.4.

Ah, found the github issue:

Thank you for the immediate response. Also, i don't see an overall coverage for the entire module. I just see the coverage individual directories. However, in the blog i saw the image where they had given the overall coverage for their tests. Am i missing something here ? How to see the overall coverage ?

And yes i do get the counter when i hover over the line.

Also, when i try to merge multiple coverage file into one file it's consuming lot of space and in some cases the machines runs out of space in the middle of conversion and the operation aborts. Has anyone encountered this ? If yes, kindly provide your solution.

For the overall coverage there comes from codecov: But we have also an internal python script to do the magic (see comment andrew).

What is a large file for you? For how long do you run your application with the coverage enabled?

The tests run for about 6-7 hours.

This topic was automatically closed after 21 days. New replies are no longer allowed.

Ok, I can see why your files get really large. Our tests take between 1 and 60 seconds. What is the file sizes you get?