Add benchmarks to tests
Open
Nobody has claimed this yet.
discussion
- Dominant language
- JavaScript
- Stars
- 543
- Forks
- 117
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 2
Description
I propose for 3.0 that we should add benchmark tests in order to see, if changes reduce (or better: improve) performance.
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
The issue names no files, tests, or entry points. First inspect the existing test and performance infrastructure, then define which Blaze 3.0 behaviors to benchmark and how results should be compared; done means repeatable benchmarks that reveal whether changes improve performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100