Do pants integration tests bypass coverage? This ...
# development
w
Do pants integration tests bypass coverage? This covers something like 60-70% of the code, but the report shows 27% and basically none of the code that DEFINITELY runs is marked as covered?
pants test --report --use-coverage --coverage-py-report=html --coverage-py-filter=pants.goal.migrate_call_by_name src/python/pants/goal/migrate_call_by_name_integration_test.py
I'm guessing because the pants process runs separately, there is no hook back into pytest to let it know what's going on?
My hope was that we had something like this hooked up: https://coverage.readthedocs.io/en/latest/subprocess.html
h
Yeah, the integration tests shell out to Pants, and so have no way of knowing what is covered
👍 1
w
Wonder if there is some way to hook into that at test time... 🤷 For another day 🙂