Skip to main content
Your agent shows you every change before it makes it and waits for your approval. You ask in plain English; the examples below are the kind of thing you might say.

​
Manage scripts

Show me the script versions for the login test and publish the new one.
  • List a test case’s script versions and see which one runs
  • Read a version’s script, with configured secrets masked
  • Add a new draft script, one test case at a time or up to 20 at once
  • Publish a draft, so every future run uses it
  • Archive a version, or restore an archived one
  • Convert a test’s script between JavaScript or TypeScript and Python
A draft changes nothing that runs until it is published. Before publishing, your agent shows you the full change and what it replaces, and it stops if either has moved since you looked. Your organization’s owners and admins are notified of each script a coding agent publishes. A script holds one Playwright test. Shared setup belongs in a test case that runs first, and configuration belongs in environment variables. A language conversion is verified in its own run before it can be published.

​
Organize tests

Archive the old guest-checkout tests.
  • Archive up to 50 test cases at once, optionally with their test runs
  • Restore archived test cases, along with the runs that were archived with them
  • Read an archived test case in full, including its steps and scripts
  • Create, rename, move and delete folders, and file test cases into them
  • Edit a test case’s title, description, expected result, priority, type and approach
  • Set which test cases run before another
  • Link a cleanup test that runs after a test to remove what it created
An archived test case doesn’t run from any schedule or suite and doesn’t count as coverage. It stays readable, and your agent can restore it at any time.
Your agent won’t archive a test case that another active test still depends on. It tells you how many depend on it, so you can archive them together or remove the dependency first. When you restore a test case, any dependency on a test that is still archived is removed, as it is in the web app.
Folders nest up to five levels, and only an empty folder can be deleted. Renaming or moving a folder keeps it in every suite that includes it, while filing test cases into a different folder changes what a suite over that folder runs next time. Folders that mirror your repository can’t be changed here. Changing which tests run before another, or which cleanup test follows it, changes every future run of those tests. Your agent shows you each link it adds or removes, and every test whose runs change, before you approve.