Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Never fully hiding in Jest tests

See original GitHub issue

It seems like Tippy never actually hides and unmounts when using jest + testing-library. onHide is called, but the test fails on waitForElementToBeRemoved and onHidden is also never called.

import React from 'react';
import * as test from '@testing-library/react';
import Tippy from '@tippyjs/react';

it('should hide', async () => {
  const onHide = jest.fn();
  const onHidden = jest.fn();
  const { rerender, queryByText } = test.render(
    <Tippy content="foo" onHide={onHide} onHidden={onHidden} visible />,
  );
  expect(queryByText('foo')).toBeInTheDocument();
  rerender(<Tippy content="foo" onHide={onHide} onHidden={onHidden} visible={false} />);
  expect(onHide).toHaveBeenCalled();
  await test.waitForElementToBeRemoved(() => queryByText('foo'));
  expect(onHidden).toHaveBeenCalled();
});

  ● should hide

    Timed out in waitForElementToBeRemoved.

      12 |   rerender(<Tippy content="foo" onHide={onHide} onHidden={onHidden} visible={false} />);
      13 |   expect(onHide).toHaveBeenCalled();
    > 14 |   await test.waitForElementToBeRemoved(() => queryByText('foo'));
         |              ^
      15 |   expect(onHidden).toHaveBeenCalled();
      16 | });
      17 |

      at Object.waitForElementToBeRemoved (../node_modules/@testing-library/dom/dist/wait-for-element-to-be-removed.js:22:24)
      at Object.<anonymous> (__tests__/tippy.test.tsx:14:14)

Version: 4.1.0 TippyJS version: 6.2.6