redyetidev

AFAIK, **Mocha:** [`this.retries(5);`](https://mochajs.org/api/mocha#retries) (On the TestContext) **Jest:** [`jest.retryTimes(5);`](https://jestjs.io/docs/jest-object#jestretrytimesnumretries-options) But I do think you are right about the `attempt()` method being unneeded and the use of the `test()` method for both...

> I'd be OK with following Mocha on this. I don't know, I think a config option `{ retries }` seems more like the rest of Node.js's testings

> I personally prefer that style. One nice thing about having it on the test context is that you can dynamically set it if you detect something happening while the...

Moving to draft for development

@cjihrig, I've made the requested changes.

I need to address a few errors.

> since it is mostly abused by encouraging tests to be non-deterministic and non-predictable (in the majority of cases i've seen). such features are often used to hide flakiness instead...

> It's fine to add the notable-change label, but most important for the changelog is [ semver-minor](https://github.com/nodejs/node/issues?q=is%3Aopen+label%3Asemver-minor+sort%3Aupdated-desc) PRs that contain new features and should be released in the next minor...

> Yes I understand, but `semver-minor` changes are automatically considered notable by the release tool. The `notable-change` label is only really useful for notable semver-patch changes. That's good to know!...

Would it be worth it to *also* add a reruns value, to rerun the test despite failure/success?