invocationCallOrder counter doesn't / can't be reset between tests

🐛 Bug Report

invocationCallOrder counter doesn’t / can’t be reset between tests

To Reproduce

Steps to reproduce the behavior: Run two tests against two mock functions, running .mockClear on each

  const a = jest.fn();
  const b = jest.fn();

  beforeEach(() => {
    a.mockClear();
    b.mockClear();
  });

  test('Test 1', () => {
    a();
    b();
    expect(a.mock.invocationCallOrder).toEqual([1]);
    expect(b.mock.invocationCallOrder).toEqual([2]);
  });

  test('Test 2', () => {
    a();
    b();
    expect(a.mock.invocationCallOrder).toEqual([1]); // Actual value [3]
    expect(b.mock.invocationCallOrder).toEqual([2]); // Actual value [4]
  });

Expected behavior

I’d expect the invocationCallOrder in the 2nd test to be [1] and [2].

It seems like the mock state is reset but not the counter, this means the tests will only have the expected callOrders if they’re the first tests run in the file. It also means you can’t run a single test as the values will be different.

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS High Sierra 10.13.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
  Binaries:
    Node: 8.9.4 - ~/.nvm/versions/node/v8.9.4/bin/node
    npm: 6.4.1 - ~/.nvm/versions/node/v8.9.4/bin/npm
  npmPackages:
    jest: ^23.6.0 => 23.6.0 

[hugeflower]

Simple solution I found to check call order :

    expect(a.mock.invocationCallOrder[0]).toBeLessThan(b.mock.invocationCallOrder[0])

to assert that a was called before b.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.