jest mock client execute mutation fails assertion

@JoviDeCroock @kitten expect(mockClient.executeMutation).toBeCalledTimes(1); /// gives 0

may be I am doing something wrong. but can you guys guide me

sample code

const apiClient: any = {
        executeMutation: jest.fn(() =>
          fromValue({
            fetching: true,
            data: {
              login: {
                token: '',
              },
            },
          }),
        ),
      };
      const { getByTestId } = render(
        <Provider value={apiClient}>
          <Login />
        </Provider>,
      );
      const submitEl = getByTestId('submit');
      await act(async () => {
        const userNameEl = getByTestId('email');
        const passwordEl = getByTestId('password');
        fireEvent.change(userNameEl, {
          target: {
            value: 'username',
          },
        });
        fireEvent.change(passwordEl, {
          target: {
            value: 'password',
          },
        });
        await fireEvent.click(submitEl);
      });
      expect(mockClient.executeMutation).toBeCalledTimes(1);

[baldurpan]

There is nothing about that second argument in the testing docs, so I can see why that would cause confusion. It currently demonstrates:

expect(mockClient.executeMutation).toBeCalledWith(expect.objectContaining({ variables }));

Perhaps the docs should be updated?

[kitten]

@chiragprodsmiths looks like you’re just missing the second argument for executeMutation here: https://github.com/FormidableLabs/urql/blob/062c1359a7ccd41044d2eb963ab0da5629143cc5/packages/core/src/client.ts#L343-L344 (Note the red , {} at the end of Jest’s Received output.