Ned Batchelder @nedbat@hachyderm.io
Public

Another kind of bug revealed by including tests in your coverage:

with pytest.raises(ValueError):
process_data("bad data 1")
process_data("bad data 2") # never executed!

nedbatchelder.com/blog/202008/

You should include your tests in coverage

This seems to be a recurring debate: should you measure the coverage of your tests? In my opinion, definitely yes.

nedbatchelder.com

Link author: Ned Batchelder@nedbat@hachyderm.io

Hugo van Kemenade @hugovk@mastodon.social
Public

@nedbatNed Batchelder Just this week, including tests in coverage helped find a common mistake:

copy/pasting a test function, changing the body, but forgetting to rename it, so the first one isn't run.

app.codecov.io/gh/hugovk/pyman

github.com/python/pymanager/pu

Two functions called test_get_install_to_run_with_platform. Same names, the second tests the case where windowed=True. The first one is marked in red to indicate it wasn't run. The second is green to indicate it was run.
0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/hugovk/statuses/114437288728540206 on your instance and quote it. (Note that quoting is not supported in Mastodon.)