Ran Benita
Ran Benita
Right, that would be a good way to do it.
I like the idea, however I fear it might over-ignore some stuff. If we don't have too many xfails, I'd feel better with just manual `pragma: no cover` comments...
For a project which is using pytest, I agree there is little risk. But here we are not only using pytest, we are also developing pytest and testing pytest, and...
@webknjaz OK, I trust you judgment on this. Thanks for improving the coverage situation!
> I hope, this will help us start requiring 100% coverage on tests Just a heads up from me on this -- while I think reaching 100% coverage is a...
I'm not near a computer, the property issue is familiar (my first patch to pytest was fixing exactly that..), but the `_` part sounds very strange, does it really not...
Right. So the situation is this: - During collection, pytest needs to find fixtures (methods decorated with `@pytest.fixture`) - To do this, it scans all of the attributes of the...
I'm afraid not.
I think we shouldn't use `-I` in the user docs because it isn't really meant for it: `-E` - users often set envvars like `PYTHONPATH`, `PYTHONWARNINGS` etc, they shouldn't be...