lincc-frameworks / lincc-frameworks/asv-formatter
Capture total pytest execution time
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
It would be really useful to track the overall pytest execution time as a statistic on the repo. This is not something that can currently be captured via asv, but if we could create some kind of mock metric that is plotted alongside the other metrics, we could at least observe when there's a significant regression and potentially find a culprit.
This came up while addressing https://github.com/astronomy-commons/lsdb/pull/194
Contributor guide
No contributing guide indexed for this repository
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 inspecting the repository's scripts that process ASV outputs and determine how existing metrics are represented and plotted. Then trace how pytest execution time could be obtained and represented as a mock metric. Done means the total pytest time appears alongside the other metrics and a meaningful regression can be observed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100