Compatible with your test suite
Interactors work out-of-the-box with your existing tests in Jest, Cypress, BigTest, and more. You can add them in over time to improve what you already have.
Optimized for design systems
More and more teams opt to use design systems to build their apps, which come with tricky components like date pickers or interactive tables. Eliminate hacky and fragile tests from those cases by shipping Interactors along with your design system components.
UX & a11y centric
Nobody uses an app by searching
[test-data-submit-button] selectors: we read labels, click buttons, or navigate through keystrokes. Interactors help you detect interaction flaws such as ambiguity in the elements of your page or the lack of adequate aria labels.
Why use Interactors?
In many typical test suites, if you change something about one button, you may have to change dozens of tests. It can take more time to update the tests than to make the change in the codebase. Does that sound familiar?
Interactors were designed to help solve this problem and bring your user interface tests closer to what users actually do.
A user finds something they want to interact with, takes action, and gets a result. The code to accomplish these same steps in a test is in one place as an Interactor. These Interactors can then be reused in many different test contexts. You can even create your own Interactors that test for whether a UI is accessible to people using assistive technology or navigating by keyboard controls.
Best of all, you do not need to throw out your existing tests when you try out Interactors! They fit right in with the work that you have already done. Try out the Quick Start guide to see this in action in your own app's test suite.