Edit Test Content

Open a test in Tests, then edit its Gherkin or Markdown tab. The editor grows with the content, so the page remains the main scrolling surface.

Edit a step, insert a variable with @, apply a Structure hint, save, regenerate the code, edit the generated file, and review the History tab, as in the steps below.

Save your instructions

1. Edit the steps, setup, or expected results.
2. Choose Save when it appears, or use Ctrl+S / Cmd+S.
3. If generated code needs to reflect the changes, choose Regenerate from the test's … menu.

A recovered browser draft is not the same as a saved project revision. Save before leaving work you want the team or generation to use. While generation is editing this test, the source editor is read-only; use View progress to see its status.

Type @ to insert a variable or secret. Tokens appear as chips while the underlying text remains {{var:NAME}} or {{secret:NAME}}. Secret chips show the name, not the saved value.

A Structure hint can offer advice for a Gherkin draft. Apply changes the draft for review; it does not save it.

Edit generated code

Once code exists, open Code, select the file, edit it, and Save. Keep assertions faithful to the test's intended behavior. A later regeneration can replace manual code edits, so put lasting requirements in the authored instructions too.

Use History to review earlier revisions. After editing, run the test before widening the run to a group.

See Gherkin and feature files and Manage generated test files.