testdouble / testdouble/suture
Add a benchmarking mode
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 1.4k
- Forks
- 27
- Avg merge
- 27m
- Merged PRs (30d)
- 2
Description
The call_both command is useful in pre-prod for telling you whether the refactored path behaves the same way extrinsically, but it'd be super neat if it also had a benchmark option for recording the duration (individually and in aggregate) of each code path
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 locating the call_both command and reading how its two code paths are invoked. Define the benchmark option around recording each path's duration and an aggregate duration, then verify that the command reports both individual and aggregate timings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100