Skip to main content

Editor

Help URL: /reference/forms/editor

Purpose​

View and edit a project file (for example a generated Playwright .spec.ts or a Gherkin .feature) in TestVibe's in-house editor.

Common Tasks​

  • Open an existing project file (commonly a generated Playwright spec) and edit it.
  • Save changes back to the project.
  • Revert unsaved changes to the last loaded/saved content.
  • Create a new file when content is provided (for example, from the recorder flow).

Key UI Elements​

  • Editor surface: Displays the current file content with syntax highlighting; Tab indents and Shift+Tab dedents.
  • Save: Writes the current editor text back to the project file (prompts for a file name when creating a new file).
  • Revert: Restores the editor text to the last loaded/saved content.
  • Close: Exits without saving.

Notes​

  • Project files are stored in TestVibe's cloud (the canonical copy lives in TestVibe's database), not in a GitHub repository. Saving writes the file back to the project.
  • For Gherkin features the editor also offers Format and Tidy with AI.
  • Common entry points: open code from Test, or review generated/recorded files after using Recorder (Playwright).