Reporting improvements for Scrutineer
Author: Zac-HDCreated Jan 19, 2023Updated Apr 13, 2026
Labelsenhancement
As part of the explain phase, codenamed Scrutineer, we collect and analyze coverage information. This issue is about upgrading the way we report the information we collect, defined in this python module.
Looking at the following output from a failing Pandas test made me think of a few improvements:
Explanation:
These lines were always and only run by failing examples:
C:\hostedtoolcache\windows\Python\3.10.9\x64\lib\site-packages\_pytest\_io\saferepr.py:81
C:\hostedtoolcache\windows\Python\3.10.9\x64\lib\site-packages\_pytest\assertion\\\util.py:235
C:\hostedtoolcache\windows\Python\3.10.9\x64\lib\site-packages\numpy\core\_methods.py:49
C:\hostedtoolcache\windows\Python\3.10.9\x64\lib\site-packages\pandas\io\formats\format.py:1306
C:\hostedtoolcache\windows\Python\3.10.9\x64\lib\site-packages\pandas\io\formats\format.py:1312
(and 18 more with settings.verbosity >= verbose)- Add some more files to the ignorelist
- Increase the number of displayed locations from five to ten
- Sort so that we prefer local files, then site-packages, and standard-library last of all.
Source: HypothesisWorks/hypothesis