Skip to main content

Tests

Tiden's test repository stores suites and test cases. Tests can be managed in the web UI, CLI, public REST API, and MCP server.

Suites and cases​

Suites organize cases. Cases carry the executable test intent and can link back to specs.

Common case fields:

  • Title and description.
  • Status such as Draft, Active, or Deprecated.
  • Priority.
  • Type, for example functional or smoke.
  • Layer, for example unit or end-to-end.
  • Tags.
  • Component.
  • Assignee.
  • Muted state.
  • Steps.

Steps​

Use steps for test cases where ordered actions and expected results matter. Keep steps focused on observable behavior rather than implementation details.

Links connect test cases to specs and power traceability.

On main, test link-spec creates a durable link. On a non-main branch, it creates a branch link proposal. Review link proposals before merging the branch.

Identity​

Tiden builds each case key from the repository, file or package, and test name. See How Tiden identifies a test case for renames, merges, and undo.

Test ingest​

The CLI supports batch ingestion from reporter drafts:

tiden test ingest ./test-draft.json --product-id <product-id>

Use test push --dry-run to count proposed suites, cases, and links before writing them:

tiden test push --dry-run ./test-draft.json

Branch behavior​

Tests are branch-aware. Use --branch <name> for CLI operations that support branch-scoped reads or writes.

Known gap: component CLI commands do not yet accept branch flags, and per-branch GetComponent is not available.