Mikhail Burshteyn
Mikhail Burshteyn
This should be relatively easy to do if limited to comparisons only (or maybe comparisons and logical operators), but will probably get a lot harder if we want to break...
NB: since pytest 6.0.0, the options can also reside in pyproject.toml. [Docs](https://docs.pytest.org/en/stable/customize.html#configuration-file-formats)
Hi @ROpdebee, Thanks for the report! I'm not really familiar with pytest-describe and its naming conventions, but I'll see what I can do to fix this.
I looked at pytest-describe, and it's more complicated than that. Full support would also mean supporting tests imported into a describe block via [`@behaves_like`](https://github.com/pytest-dev/pytest-describe#shared-behaviors). And even if we ignore `@behaves_like`,...
Another example of a deprecated fixture is `mock` -> `mocker` from `pytest-mock`.
@sobolevn These cases are not what I meant. If the fixture function returns a function which has some assertions in it, that is fine, since the function is called during...
Thanks @sobolevn, I've added it to the description
Hi @cansjt, Thank you for your report! This is currently working the way I intended: when there is a single name, the plugin always expects it to be a plain...
In any scenario, if we expect a test to fail, it is best to pin **how exactly** we expect it to fail, so that it will be noticed if something...
Hi @sobolevn, I'm not sure that duplicating `pytest`'s runtime checks on the linter level is the way to go. Linters and tests are typically run in the same CI pipeline,...