write_test_case
Document a test case with title, steps, and expected results; index it for search, and auto-push to git. Check existing coverage before adding to avoid duplicates.
Instructions
Create a test case document, index it immediately, and auto-push to git.
Call search_tests() first to check for existing coverage before adding
a new test case.
Side effects: creates tests/YYYY-MM-DD-{slug}.md in the docs path,
indexes it into the vector store, and pushes to git if configured.
Use after writing or modifying tests to make them discoverable.
Status values: "pass", "fail", "blocked", "pending" (default: pending).
Args:
title: Short test case title (e.g. "User login with expired token")
scenario: What is being tested and why (the test intent)
steps: Step-by-step test procedure
expected_result: What should happen when the test passes
preconditions: Setup required before running the test (optional)
actual_result: Observed result if already executed (optional)
status: "pass", "fail", "blocked", or "pending" (optional)
tags: Comma-separated tags, e.g. "auth,regression,critical" (optional)
project: Target project name (optional)
Returns:
Saved filename, chunk count, and whether auto-push succeeded.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | ||
| steps | Yes | ||
| title | Yes | ||
| status | No | ||
| project | No | ||
| scenario | Yes | ||
| actual_result | No | ||
| preconditions | No | ||
| expected_result | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |