Skip to main content
Everything here changes something in Peeps, so your agent shows you the change and waits for your approval first. All of it needs the Contributor role or above.

Edit a test case’s details

Mark the checkout tests as critical priority.
Your agent can change a test case’s title, description, expected result, priority, type and approach. It reads the test case first and shows you only the fields that change. If somebody else edited the test case since, Peeps refuses rather than overwriting their work, and your agent shows you the new state. Editing details changes nothing else. Steps, scripts, suites, schedules and runs stay as they are.

Update a test case’s steps

The settings page moved into the account menu. Update the steps for the profile test.
Your agent shows you the step changes before it saves them. Change the steps only when what the product is meant to do has changed. A selector fix or other script repair doesn’t belong in the steps. Updating steps doesn’t publish a script or start a run. When the script needs to change too, your agent proposes both together as a fix. See intended behavior change.

Set which tests run first

The order history test needs a signed-in user with a past order. Make it run after “Place an order”.
A test case can have prerequisites: test cases that run before it, such as signing up a user or seeding data. Your agent shows you each link it adds or removes, and every test whose runs change as a result, before you approve. Changing prerequisites changes every future run of those tests. It doesn’t change which suites or schedules include them.

Add a cleanup test

After the “Create a project” test, run “Delete the test project” to clean up.
A cleanup test runs after a test to remove what it created. Your agent previews the complete change — every link and every affected test — before you approve it. If anything changes between the preview and your approval, it previews again.

Archive and restore test cases

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.
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.
If your project runs specs from your own repository, archiving and restoring work there too, exactly as in the web app. It changes how Peeps organizes its test cases, never the repository. Removing a test file from your repository doesn’t archive its test case; Peeps only marks it missing. If the file comes back, the test case is restored automatically.

Worked example: archive, then restore

You: We removed guest checkout. Archive those tests.
Your agent searches for guest-checkout test cases and finds three. It shows you their titles, and says that one active test, “Apply a discount as a guest”, still depends on one of them.
You: Archive that one too, and their runs.
Your agent archives all four test cases and their test runs. They stop running from every schedule and suite. A month later:
You: Guest checkout is back. Restore those tests.
Your agent searches archived test cases, finds the four, and asks you to confirm. It restores them along with the runs archived with them. They are active again, and every schedule and suite that includes them runs them.

Organize folders

Move the refund tests into a new Payments folder.
  • Create, rename, move and delete folders.
  • File test cases into a folder, move them between folders, or take them out of any folder — up to 500 at once.
Folders nest up to five levels, and only an empty folder can be deleted. There is no restore for a deleted folder. Renaming or moving a folder keeps it in every suite that names it. Moving test cases into a different folder can change what a suite over that folder runs next time. Your agent renames a folder in place rather than recreating it, so suites don’t lose it. Folders that mirror your repository can’t be changed here.

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
A draft changes nothing that runs until it is published. Before publishing, your agent shows you the full change and the version it replaces. It stops if either one has moved since you looked. Your organization’s owners and admins are notified of each script a coding agent publishes. Publishing, archiving the version that runs, and restoring an archived version all change what runs, so they need the Publish permission. Before your agent archives the version that runs, it tells you which version takes over.

What a script can contain

  • One Playwright test per test case. Shared setup belongs in a test case that runs first.
  • JavaScript or TypeScript as one self-contained module. It can import @playwright/test and Node built-ins. Copy any helpers, page objects and fixtures it uses into the file.
  • Python, where your Peeps deployment runs it.
  • Configuration as placeholders. Write {{BASE_URL}} or {{ADMIN_EMAIL}}, and the value comes from the environment the test runs in.
Peeps screens each script for credentials and refuses one that contains any, without storing it. A script that has a syntax error, or uses a placeholder the project doesn’t define, is stored as a draft but can’t be published. Your agent can add the missing variable, with your approval, and then publish the same draft.

Convert a script’s language

Convert the login test’s script to Python.
Your agent can convert a test’s script between JavaScript or TypeScript and Python. The conversion is verified in its own run before it can be published, and publishing is a separate approval. Your client has to support the approval form Peeps shows for this. If it doesn’t, Peeps says so.