New Rule: Prefer mock resolved/rejected shorthands

[alexilyaev]

Simple sugar function for:

jest.fn().mockReturnValue(Promise.resolve(value));

Useful to mock async functions in async tests:

test('async test', async () => {
  const asyncMock = jest.fn().mockResolvedValue(43);

  await asyncMock(); // 43
});

Refs:

• https://facebook.github.io/jest/docs/en/mock-function-api.html#mockfnmockresolvedvaluevalue
• https://facebook.github.io/jest/docs/en/mock-function-api.html#mockfnmockresolvedvalueoncevalue
• https://facebook.github.io/jest/docs/en/mock-function-api.html#mockfnmockrejectedvaluevalue
• https://facebook.github.io/jest/docs/en/mock-function-api.html#mockfnmockrejectedvalueoncevalue

[SimenB]

Yeah, sounds good!

[G-Rath]

fwiw this is actually technically not the same due to jestjs/jest#6645 but I still think it's worth a rule with a fixer to start with, and turn it into a suggestion if we get complaints.

(I've so far only hit this once (slorber/react-async-hook#24) so am hoping it's very rare).

[github-actions]

🎉 This issue has been resolved in version 26.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀