pytest-dev / pytest-dev/pytest

Provide for an easier way to re-use fixtures or plugins from other conftests

Open
#2,062 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: feature-branch type: refactoring
Dominant language
Python
Stars
14.5k
Forks
3.4k
Avg merge
2d 9h
Merged PRs (30d)
35

Description

It'd be very helpful to have one canonical way to re-use fixture code between test modules. Right now, I know of 3 ways to do this, each with their own downsides:

  1. Import the fixture/hook directly -- Results in unused imports, and isn't always clear where the code came from. Easy to break things later when cleaning up unused imports.
  2. Use pytest_plugins = 'path.to.conftest' -- Will result in pytest errors if you run the current module and the module the conftest came from at the same time. Also makes the plugin globally active, which isn't always desired.
  3. Move the code to a common-ancestor -- Can make the fixtures too broadly usable, especially if the test modules aren't relatively close to each other.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the three fixture-reuse approaches described for conftests and test modules. Review how fixture code is currently shared, then define a canonical reuse mechanism that avoids unused imports, simultaneous-module errors, unwanted global activation, and overly broad common ancestors; done means the approach is specified and its trade-offs are resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.