Repository navigation
got() automatic retries makes for confusing failures in Nock tests #1523
Description
Activity
- added a commit that references this issue
on May 2, 2019 🎉 This issue has been resolved in version 11.0.0-beta.11 🎉
The release is available on:
Your semantic-release bot 📦🚀
🎉 This issue has been resolved in version 11.0.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
- added a commit that references this issue
on Mar 21, 2026
As I mentioned at #1515 (comment), Got automatically retries failed requests twice.
That means if you have a test which mocks a 4xx or 5xx response, got will immediately reissue it.
At that point, the mock will have been consumed. The test will error out with
Nock: No match for request.Adding
{ retry: 0 }to thegotcalls will disable this behavior, and will make the tests behave less confusingly.As I also mentioned in that thread:
We should use
got.extend()to set defaults that turn off this behavior.