Our tests take quite some time and quite a significant amount is due to coverage (see #9463).
Contributor guide
Tech stack
python
Domain
testingperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Python testing experiencefamiliarity with coverage tools
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue asks for ways to speed up coverage during tests. Begin by reading the referenced issue #9463 for context. Then profile the current test suite to identify slow coverage related steps. Investigate alternative coverage tools or configurations (e.g., using pytest cov with parallel execution, or subset coverage). Consider if incremental coverage or caching could help. Report findings and propose a concrete optimization in the issue.
