@react-aria/test-utils offers common select interaction testing utilities. Install it with your preferred package manager.
Initialize a User object at the top of your test file, and use it to create a Select pattern tester in your test cases. The tester has methods that you can call within your test to query for specific subcomponents or simulate common interactions.
// Select.test.tsimport {render} from'@testing-library/react';
import {User} from'@react-aria/test-utils';
lettestUtilUser = new User({
interactionType: 'mouse'
});
// ...it('Select can select an option via keyboard', asyncfunction () {
// Render your test component/app and initialize the select testerlet {getByTestId} = render(
<Select data-testid="test-select">
...
</Select>
);
letselectTester = testUtilUser.createTester('Select', {root: getByTestId('test-select'), interactionType: 'keyboard'});
lettrigger = selectTester.trigger;
expect(trigger).toHaveTextContent('Select an item');
awaitselectTester.selectOption({option: 'Cat'});
expect(trigger).toHaveTextContent('Cat');
});
API
User
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.
Selects the desired select option. Defaults to using the interaction type set on the select tester. If necessary, will open the select dropdown beforehand.
The desired option can be targeted via the option's node, the option's text, or the option's index.
Returns the select's options if present. Can be filtered to a subsection of the listbox if provided via element.
Testing FAQ
In cases like this, first double check your test setup and make sure that your test is rendering your select 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 select's state post interaction.
Whenever the select tester queries its elements or triggers a user flow, it does so against the current state of the select. Therefore the select tester can be used alongside whatever simulated user flow you add.