pytest-dev / pytest-dev/pytest
rough performance analysis of the current internals
Open
Nobody has claimed this yet.
type: performance
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
this is the second followup to #401
its about time we take a good looks what eats time when executing pytest,
the last deep look was quite a while ago
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 issue #401 and profiling the current pytest execution path. The issue provides no files or tests to target; done would require identifying the main sources of execution time and recording the performance findings for follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100