jamesplease / jamesplease/bestfetch
Testing: switch to `.resetHistory()` instead of `.reset()`
Open
tests
- Dominant language
- JavaScript
- Stars
- 46
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I think `.reset()` is working due to some strange env setup, but `.resetHistory()` is what I actually want.
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test path is identified in the issue. Search the test setup for `.reset()` and compare its use with the intended `.resetHistory()` call, then run the affected tests to confirm the history is reset as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100