Skip to content

Conversation

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jan 30, 2020

No description provided.

ParetoLife and others added 18 commits January 27, 2020 10:50
From the description it seemed to me as if just prefixing your methods with ``test_`` was enough, but you also need to prefix your class with ``Test``. Of course, in the reference material this is clearly stated, but I think it makes sense to mention it here as well, since you also mention the part about the methods' prefix.
It should be in `test_code` when testing `_pytest._code.getfslineno`,
not to be confused with `_pytest._code.source.getfslineno`.

Adds an extra assert (via pytest-dev#6590).
The incremental marker is adapted to handle properly test classes with parametrize defined at class level.

Fix pytest-dev#3125
extend the incremental marker for parametrize
…ev#6583)

doc: getting-started.rst: mention "Test" prefix for classes
(cherry picked from commit fd1a51a)
…many_verbose

tests: harden test_teardown_many_verbose
tests: test_code: improve/clarify imports
Docs: Don't wrap the markdown for GitHub releases
Reverts pytest-dev#6610.

The tested `getfslineno` is `src/_pytest/_code/source.py` actually,
exported via `src/_pytest/_code/__init__.py`.
I've confused it with the one in `src/_pytest/compat.py` apparently.
@blueyed blueyed merged commit 4de8e68 into pytest-dev:features Jan 30, 2020
@blueyed blueyed deleted the merge-master-into-features branch January 30, 2020 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants