Explore
Explored in your real app.
Re:agent signs in, clicks and reads the page. Every step is recorded.
Rehearsal explores your app, writes the tests and runs them on web, mobile and desktop, locally and on every pull request. It keeps them working as your app changes, so you do almost nothing.
Be first in. Early members get perks when Rehearsal opens.
Terminal, coding agents, GitHub and Vercel.
Message Re:agent
Re:agent uses your app the way a person would and turns what it did into a test. Here it checks that an invited member can join a project.
Explore
Re:agent signs in, clicks and reads the page. Every step is recorded.
await test.step('Sign in as the owner', async () => { await owner.page.getByLabel('Password') .fill(owner.password()); await owner.page .getByRole('button', { name: 'Sign in' }).click();});await test.step('Open the invitation as the member', async () => { const email = await member.latestEmail(); await member.page.goto(email.links[0]);});Verify
Rehearsal reruns the new test before marking it ready.
Say what to check, or nothing at all. Subagents open your app in real browsers and report the bugs they find.
When a flow involves two people, each gets a browser of their own. Follow an invitation from the person sending it to the person accepting it.
More than one person
Up to four people in one flow, each signed in with their own test account.
Every screen size
A layout that fits a laptop can break on a phone.
Every browser
Date pickers, uploads and video behave differently in each browser.
Every platform
Test your web, mobile and desktop apps in one workspace.
Connect the app running on your machine and run your saved tests against it. Rehearsal reaches it through a connection you keep open in your terminal.
npm install -g @rehearsal-labs/cliRetest is the test library Rehearsal runs your tests on. You can read its code, run it yourself and use it without Rehearsal.
Your agent can run the saved tests, read where one stopped, fix the app and run them again. Every command answers in JSON with the next step.
Connect a repository and choose which tests run on pull requests and deployments. Rehearsal tests the preview and posts the result on the commit.
Deployments
Rehearsal never reads your source code.
Open the run, follow its steps and watch the recording. A failed check names the step, what it expected and what the page showed.
Invited member can join and see the project Run 74
Runningstarted just now
ChromiumProductionparcel.example.com
Failed at step 12. It expected the page to show Parcel. The page showed No projects yet.
Run again after the fix. 12 of 12 steps passed in 39s.
A run that stops because of Rehearsal is marked could not run. It never counts as a failure and is never charged.