It’s pretty straightforward to write E2E tests for a single user to complete a single workflow. Things get more complicated when you have thousands of E2E tests, some of which may depend on data or state from other tests. Or if your environments can’t handle that many concurrent runs.
What do you do then?
Run Rules let testers configure the order of individual tests and steps within tests. It’s all covered in our white paper. With Run Rules you can…
- Test multi-user workflows: Coordinate tests across different users and devices, like an Uber Rider and Driver that share data and state across two different users and devices.
- Share data between tests: Pass a user account, a recorded video, or a status update from one test to the next that needs it.
- Control the order tests run: Run one batch of tests before the next, or set a dependency so a test doesn’t start until another has completed a specific step.
Head to our docs for help setting up Run Rules.
