Skip to main content

Test editor

Open a test under Tests to edit its instructions or inspect its saved code.

  • Gherkin contains structured scenarios and steps; a Markdown test shows a Markdown tab for its plain-language instructions instead.
  • Code contains the generated Playwright test, normally a .spec.js file, and appears once generated code exists.
  • Runs shows executions associated with a code-backed test. Use the main Runs page for Assistant runs of tests without generated code.
  • History lets you inspect previous versions.

Editing instructions does not automatically make existing generated code match them. Save your changes, then generate or regenerate the code when needed. Review the result before running it.

The editor's Tools menu contains the actions available for that file. Available actions depend on the file type and whether generation is in progress.

Use project variables and secrets for changing data or credentials. See edit test content, generated files, and variables and secrets.