YAML Test Cases & Runs — QA Manager for VS Code

Manage manual test cases and test runs as YAML in your workspace — browse suites, edit cases, and execute runs from a three-column Test Repository UI inside VS Code.

Cases and runs live under .gitoza-lite/test/cases/ and .gitoza-lite/test/run/ as plain files in your repo.

AI-friendly workflow

Test cases are plain YAML in your repo — easy for AI assistants (Cursor, Copilot, ChatGPT, etc.) to read and write. Use your editor or chat to draft cases, then browse, review, and save them in a structured UI. No built-in AI is required.

Draft cases with AI — describe a requirement, generate a .yaml file, then open and refine it in the Test Repository before you commit.
Tests as code — every case and run is a file you can git add, git diff, and merge in pull requests.
Link manual cases to automation — use tags and params to reference a Playwright, Selenium, or other test file path (the case filename is the case id).
Track automation coverage — scripts or AI can scan your suite and set automated: true (and tags) on matching cases.

Example linking a manual case to a Playwright spec:

---
title: Login with valid credentials
tags: [smoke, auth, playwright]
automated: true
params:
  playwright: tests/auth/login.spec.ts
---

## Steps
1. Open the login page
2. Enter valid credentials

## Expected result
User is redirected to the dashboard.

Screenshots

Test Repository

Browse projects, suites, and cases in a three-column editor tab.

Test Repository UI

Cases are stored as plain YAML on disk:

Case YAML file

Test Run

Create runs, add cases from the repository, and mark Pass / Fail / Skip.

Test Run UI

Each run is a single YAML file listing case paths and results:

Run YAML file

Getting started

Requirements: VS Code 1.85+ and an open workspace folder.

Open a repository in VS Code.
The Gitoza Test Repository tab opens in the editor area when the extension activates (when .gitoza-lite/test/cases/ exists, or after you run the open command below).
If the tab was closed, click the Gitoza icon in the Activity Bar and choose Open Test Repository, or run Gitoza: Open Test Repository from the Command Palette.
If .gitoza-lite/test/cases/ does not exist, use Create first project to initialize it.
Switch to Test Run in the sidebar to create runs, add cases from the repository, and mark Pass / Fail / Skip.

VS Code Explorer stays available alongside the editor tab.

Workspace paths: This extension uses .gitoza-lite/test/cases/ and .gitoza-lite/test/run/ only. It does not read or modify the Gitoza Desktop paths .gitoza/test/cases/ or .gitoza/test/runs/. If you already have data under the Desktop paths, copy or move them into the lite paths manually — there is no automatic migration.

Features

Three-column Test Repository UI — folder tree, case list, and case detail
Local-first — reads and writes YAML on disk in your workspace; no SQLite or shadow clone
Git-based — every case and run is a file in version control
Tests as code — each case is a .yaml file with a Markdown body
Create projects, suites (folders), and test cases
Manual save — click Edit, then Save to write YAML (no auto-save)
Editor-tab UI — Test Repository opens in an editor tab (not the VS Code sidebar)
Test Run — YAML-backed manual runs with Pass / Fail / Skip

File formats

Case file format

Each test case is a YAML file with front matter and a Markdown body. The extension writes only editable fields on create/save (title, priority, tags, status, requirement_id, assigned_to, automated, params, and the Markdown body). Audit and review fields (updated_at, updated_by, approve_status, comments, etc.) are not written; if present in an existing file they are still parsed but not shown in the UI and are removed on the next save.

---
title: Login with valid credentials
priority: high
tags: [smoke, auth]
status: active
---

## Steps
1. Open the login page
2. Enter valid credentials

## Expected result
User is redirected to the dashboard.

Test run file format

Each test run is a single YAML file under .gitoza-lite/test/run/{run-name}.yaml. The filename is the run id; a human-readable title lives in front matter. Cases reference repository paths; results are stored inline.

---
title: Sprint 42 smoke
---
cases:
  - path: .gitoza-lite/test/cases/my_project/suite/login.yaml
    result: pending
  - path: .gitoza-lite/test/cases/my_project/suite/logout.yaml
    result: passed

Supported result values: pending, passed, failed, skipped.

About Gitoza

Built by Gitoza — a local-first, git-based test management platform where test cases and runs are stored as code in version control.

This extension is Gitoza Lite for VS Code: edit cases and run manual tests in the editor. For git sync, review workflows, automation pipelines, and the full desktop experience, visit gitoza.com.

Development

See CONTRIBUTING.md for build, test, and packaging instructions.

License

MIT — see LICENSE.

YAML Test Cases & Runs — QA for VS Code

Gitoza