Create a test for each benchmark file
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Some benchmarks simply fail, and we are not tracking that. Example: https://github.com/nodejs/node/pull/59173.
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
Review the benchmark files and the failure example linked in PR #59173 to determine how benchmark execution is currently checked. Add coverage so each benchmark file is tested for failure, and verify the suite detects the failures described by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100