Timeline for Why do code coverage of integration test?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 16, 2021 at 19:33 | comment | added | Adam Parkin |
"You typically exclude test code from code coverage reports" -- I actually don't do this for one specific reason: sometimes it reveals tests that aren't actually being run, or test fixtures that aren't actually being used. Like if I see tests/foobar.py at less than 100% coverage I immediately go "hey that's weird" and look inside to see what in that file isn't being exercised as part of a test run.
|
|
| Jan 23, 2017 at 13:59 | comment | added | Thiago Fioravante | Thanks @jpjwolli, I'll try this and return a feedback about the remote code coverage. | |
| Jan 20, 2017 at 19:42 | comment | added | ernie | I'm pretty sure they're asking how to measure what code their integration tests touch, not if something else is testing their tests . .. | |
| Jan 20, 2017 at 15:50 | history | answered | jpjwolli | CC BY-SA 3.0 |