Skip to main content

Test Cases

Test cases are the heart of your repository. They capture expected behaviour, link back to requirements, and power manual or automated execution. The editor supports rich structure, version control, and review workflows.

Authoring a test case​

Every revision can capture:

  • Metadata – Title, workflow state, priority, severity, layer, behaviour, form (functional, exploratory, etc.), automation status, estimated execution time, and flakiness indicator.
  • Personas & segments – Associate the test with a target persona or customer segment for better coverage reporting.
  • Rich description – Pre-conditions, post-conditions, and body content stored as structured TipTap JSON (supports formatting, links, and lists).
  • Reusable steps – Build classic steps, step groups, or shared step items with action, data, and expected result fields.
  • Parameters – Attach dataset definitions or structured parameters (including child parameters) for data-driven tests.
  • Attachments – Upload screenshots or supporting evidence; thumbnails are generated automatically.
  • Custom fields – Capture additional attributes defined by your organisation (text, number, boolean, date, single/multi-select, etc.).
  • Tags – Apply labels for filtering and reporting across the project.
  • Traceability links – Link internal requirements or external work items (Jira, ClickUp, GitHub issues) via requirement links and external link records.

Reviews & versioning​

  • Draft vs. approved – Projects can require reviews for creation, updates, or deletions. Revisions track review status (draft, pending_review, approved).
  • Reviewer assignment – Request specific reviewers or use the project default reviewer count before a revision can be approved.
  • Revision history – Each approval generates a new immutable revision. You can compare versions, restore deleted cases, or roll back to earlier revisions.
  • Comments – Leave inline review comments and capture approval/rejection notes.

Productivity features​

  • AI-assisted generation – Send requirement context to the AI service, preview suggestions, and bulk-create selected cases directly into the suite.
  • Bulk update & delete – Update metadata across multiple cases provided the project review policy allows it. Bulk delete respects review rules.
  • Clone – Create a copy (with all steps, attachments, requirements, and tags) for fast authoring of variants.
  • Recycle bin – Soft-deleted cases can be restored individually or in bulk.
  • Defect linkage – View all defects raised against the case (internal and external) along with execution history.
  • Powerful search – Find test cases instantly with filters by suite, tags, workflow state, assignee, and more.
  • Version history – Track all changes with revision history. Compare versions, restore deleted cases, or roll back to earlier revisions.

Best practices​

  • Keep titles action-oriented ("Verify user can reset password via email link").
  • Use personas and segments to highlight coverage gaps.
  • Add parameters for environment variables or test data so automated runs can reuse the same case.
  • Review workflow policies are managed under project settings → Review Configuration. Tune them to balance speed and governance.