Thomas Grainger
Thomas Grainger
@eyedean I don't have access to this repo either
@JWCook can you make a PR with a test for this in?
> Given that pytest 6 is allowed to do breaking changes Can we flip the default here so markers default to strict in v6? What about xfail_strict
> We could then change the default to True in a future release so pytest by default will be more strict From @nicoddemus seems like this is exactly that future...
I think if we add strict-markers and strict-config to `--strict` we should also have it cover `xfail_strict`
> I don't think we should do this now (and after the RC is out already). In that case I think we should just drop the `--strict` alias in v6.0...