pytest-dev / pytest-dev/pytest
extract or integrate a dependency injection mechanism for fixtures
Open
Nobody has claimed this yet.
topic: fixtures
type: enhancement
type: proposal
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
CC @cjw296
the current fixture mechanism is something that grew entirely inside of pytest and is not usable without it
which in turn creates the need for parallel infrastructure when wanting to use the actual things again
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pytest's current fixture mechanism and tracing which parts are tightly coupled to pytest. The work is done when the fixture dependency-injection capability can be extracted or integrated for reuse outside pytest, avoiding parallel infrastructure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100