Also, Pants 2.0 will create RAW coverage file (.co...
# general
Also, Pants 2.0 will create RAW coverage file (.coverage) in addition to xml and html?
Seems like we moved away from pytest --cov and in favor of Current way (pants 1.25) like test.pytest --test-pytest-coverage=auto still works with 2.0?
We redesigned coverage support in 1.30 and 2.0.
never worked very well; it was confusing and the heuristic didn’t work with certain project layouts. The
field on
target was tedious. Instead, Pants now much more closely aligns to how coverage would work if you didn’t use Pants. See Regarding
pytest --cov
, that is only for us to generate the individual
files for each distinct test you run. We then use
to merge it all into a single report (or single
Thanks for the detailed explanation. I like the better. I am looking forward to upgrading to 2.0 👍
❤️ 1
You’re welcome! Please let us know how we can help with upgrading to 2.0. We’ve been putting a lot of polish into it and believe it’s a much better experience than what you’re getting with 1.25, including better concurrency, a more informative and less noisy UI, and dependency inference, where you can usually leave off the
field of BUILD files because Pants will analyze your import statements The upgrade guide will hopefully help, and we’re also really happy to help with any challenges you run into or feedback you have.
Do you have any custom Pants plugins right now?
I am actually not sure. I focus on testing part. We are trying to use Coveralls. This is why I am excited that Pants 2.0 will create raw coverage file so it can be consumed by Coveralls.
💯 1
Got it. We use it for that same reason at my org Toolchain