@react-spectrum/test-utils offers common dialog interaction utilities which you may find helpful when writing tests. To install, simply
add it to your dev dependencies via your preferred package manager.
Once installed, you can access the User that @react-spectrum/test-utils provides in your test file as shown below. This user only needs to be initialized once and then can be used to generate
the Dialog tester in your test cases. This gives you access to Dialog specific utilities that you can then call within your test to query for specific subcomponents or simulate common interactions.
The example test case below shows how you might go about setting up the Dialog tester, use it to open and close the dialog, and verify the dialog's state after each interaction.
// Dialog.test.tsimport {render} from'@testing-library/react';
import {User} from'@react-spectrum/test-utils';
lettestUtilUser = new User({interactionType: 'mouse', advanceTimer: jest.advanceTimersByTime});
// ...it('Dialog can be opened and closed', asyncfunction () {
// Render your test component/app and initialize the dialog testerlet {getByTestId, getByRole} = render(
<DialogTrigger>
<ActionButton>Trigger</ActionButton>
<Dialog>
...
</Dialog>
</DialogTrigger>
);
letbutton = getByRole('button');
letdialogTester = testUtilUser.createTester('Dialog', {root: button, overlayType: 'modal'});
awaitdialogTester.open();
letdialog = dialogTester.dialog;
expect(dialog).toBeVisible();
awaitdialogTester.close();
expect(dialog).not.toBeInTheDocument();
});
See below for the full definition of the User and the Dialog tester.
Properties
Name
Type
Default
advanceTimer
UserOpts['advanceTimer']
Default: —
A function used by the test utils to advance timers during interactions. Required for certain aria patterns (e.g. table).
interactionType
UserOpts['interactionType']
Default: mouse
The interaction type (mouse, touch, keyboard) that the test util user will use when interacting with a component. This can be overridden
at the aria pattern util level if needed.
In cases like this, first double check your test setup and make sure that your test is rendering your dialog in its expected state before the test util interaction call. If everything looks correct, you can always fall back to simulating interactions manually, and using the test util to query your dialog's state post interaction.
Whenever the dialog tester queries its elements or triggers a user flow, it does so against the current state of the dialog. Therefore the dialog tester can be used alongside whatever simulated user flow you add.