pytest-dev / pytest-dev/pytest-django
"rf" alias to "request_factory" (or vice versa)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 367
- PR merge metrics
- No merged PRs in 30d
Description
Fixtures are already a bit of an obscure concept for people new to Pytest. And as in the good old saying goes... "readability counts".
(suggesting to keep rf, no need for a hamster wheel update of a bunch of test cases, that will just make a lot of people feel miserable)
By the way, thanks for a great project 💟
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
Search the pytest-django fixture definitions and related tests for rf and request_factory; start by comparing how the existing fixture is exposed and exercised. Add the requested alias without renaming existing uses, then run the relevant fixture tests to verify both names work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100