CODEWITHSUNDEEP
javascriptnode.jsecmascript-6jestjses6-promise
Rüdiger Schulz
Rüdiger Schulz

Reputation: 3108

Why is a mocked jest promise not rejected with allSettled?

I want to test a method which returns the result of Promise.allSettled() and calls another function which returns promises.

I reduced the problem to the following test code:

  describe('Promise tests', () => {
    it('should reject directly', async () => {
      const f = jest.fn().mockRejectedValue(new Error('foo'));
      const p = async () => await f();

      // works
      await expect(p).rejects.toThrow('foo');
    });

    it('should reject with allSettled', async () => {
      const f = jest.fn().mockRejectedValue(new Error('foo'));
      const p = async () => await f();

      const results = await Promise.allSettled([p]);
      expect(results[0].status).toBe('rejected'); // fulfilled - but why?
      expect(results[0].reason).toBe('foo');
    });
  });

Why is the second case not receiving a rejected promise?

Upvotes: 0

Views: 2739

Answers (1)

r3dst0rm
r3dst0rm

Reputation: 1926

You are almost there. Promise.allSettled expects to receive an array of Promises not an array of functions returning a promise, which in fact is what your constant p does.

By simply calling the p() you solve your issue:

  describe('Promise tests', () => {
    it('should reject directly', async () => {
      const f = jest.fn().mockRejectedValue(new Error('foo'));
      const p = async () => await f();

      // works
      await expect(p()).rejects.toThrow('foo');
    });

    it('should reject with allSettled', async () => {
      const f = jest.fn().mockRejectedValue(new Error('foo'));
      const p = async () => await f();

      const results = await Promise.allSettled([p()]);
      expect(results[0].status).toBe('rejected'); // fulfilled - but why?
      expect(results[0].reason).toBe('foo');
    });
  });

By the way: My linter complains about unnecessary awaits :-)

Upvotes: 2

Related Questions