Conversation
Ensure all uses of caplog._item have a comment highlighting it is a private API and not for use in real tests!
All the tests in this file are tests of `caplog`
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
for more information, see https://pre-commit.ci
| nose/unittest-style "dot" output. | ||
|
|
||
| - many many more detailed improvements details | ||
| - many, many, more detailed improvements details |
There was a problem hiding this comment.
generally in English, doubled words aren't appropriate without punctuation, and often they're just errant.
|
|
||
| - fix issue320 - fix class scope for fixtures when mixed with | ||
| module-level functions. Thanks Anatloy Bubenkoff. | ||
| module-level functions. Thanks Anatoly Bubenkoff. |
There was a problem hiding this comment.
This matches other instances of what I have to presume is the same entity.
|
|
||
| - fix issue244 by implementing special index for parameters to only use | ||
| indices for paramentrized test ids | ||
| indices for parametrized test ids |
There was a problem hiding this comment.
there's an amusing thing elsewhere about a serious of variations of this word, but this isn't one of them...
| Gospodnetic for the PR. | ||
|
|
||
| - change XPASS colour to yellow rather then red when tests are run | ||
| - change XPASS colour to yellow rather than red when tests are run |
There was a problem hiding this comment.
technically this is grammatical, but most spell checkers have been able to flag rudimentary grammar errors, so there are a handful of fixes for things like this...
| private permissions. | ||
|
|
||
| pytest used to silently use a pre-existing ``/tmp/pytest-of-<username>`` directory, | ||
| pytest used to silently use a preexisting ``/tmp/pytest-of-<username>`` directory, |
There was a problem hiding this comment.
both flavors were preexisting in this repository :)
| you accessed helpers and possibly collection classes through | ||
| the ``py.test`` Python namespaces. The new ``pytest`` | ||
| Python module flaty provides the same objects, following | ||
| Python module flatly provides the same objects, following |
There was a problem hiding this comment.
It could be that there's a module flaty, but...
| :pypi:`pytest-ads-testplan` Azure DevOps Test Case reporting for pytest tests Sep 15, 2022 N/A N/A | ||
| :pypi:`pytest-affected` Nov 06, 2023 N/A N/A | ||
| :pypi:`pytest-agent` Service that exposes a REST API that can be used to interract remotely with Pytest. It is shipped with a dashboard that enables running tests in a more convenient way. Nov 25, 2021 N/A N/A | ||
| :pypi:`pytest-agent` Service that exposes a REST API that can be used to interact remotely with Pytest. It is shipped with a dashboard that enables running tests in a more convenient way. Nov 25, 2021 N/A N/A |
There was a problem hiding this comment.
I couldn't tell if this is a list of descriptions that come from the modules, in which case the fixes would belong in the modules -- but searches didn't seem to show lots of indications where I'd expect if that was the case, so...
| def pytest_configure(config: Config) -> None: | ||
| if config.option.stepwise_skip: | ||
| # allow --stepwise-skip to work on it's own merits. | ||
| # allow --stepwise-skip to work on its own merits. |
There was a problem hiding this comment.
the previous text would mean it is which seems very wrong
| # assert rep.outcome.where.lineno == 3 | ||
| # assert rep.outcome.where.path.basename == "test_func.py" | ||
| # assert instanace(rep.failed.failurerepr, PythonFailureRepr) | ||
| # assert isinstance(rep.failed.failurerepr, PythonFailureRepr) |
There was a problem hiding this comment.
It's possible this was instance, but I didn't think that was a thing
nicoddemus
left a comment
There was a problem hiding this comment.
Looks great, thanks!
Usually we would squash the commits before merging for a mostly automated PR like this one, but perhaps it makes sense to keep those commits because they do add context to each change?
| using a check such as ``if isinstance(node, Instance): return``. | ||
| Such plugins should simply remove consideration of ``Instance`` on pytest>=7. | ||
| However, to keep such uses working, a dummy type has been instanted in ``pytest.Instance`` and ``_pytest.python.Instance``, | ||
| However, to keep such uses working, a dummy type has been instanced in ``pytest.Instance`` and ``_pytest.python.Instance``, |
There was a problem hiding this comment.
The descriptions here are taken from PyPI and are generated automatically, so they will be overwritten on the next update, but this is fine.
|
@nicoddemus: are you waiting for something from me? |
|
@jsoref no, thanks for the ping. I was waiting to see if others would like to review too, but merging now. |
I'm open to adding a changelog item, but as I generally get pushback on some changes in long sets, I'm disinclined to write it proactively as I don't know what it'll say.
Fwiw, here's the tooling output that reported the items that I'm fixing: https://github.com/jsoref/pytest/actions/runs/8286348273#summary-22676128090
And here's a report showing those items have been addressed: https://github.com/jsoref/pytest/actions/runs/8286348842#summary-22676129381