Skip to main content

Documentation Index

Fetch the complete documentation index at: https://quashbugs.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

About the Test Cases Library

The Test Cases library is the central repository for all your test cases in Quash. Every test case your team creates — whether generated by Megumi in Test Studio, or written manually — lives here and can be reused across any number of suites. To access Test Cases: Click the Test Cases icon in the left navigation panel. ![](/images/image (5).png)

The library list

The library shows every test case in your workspace as a table. Each row displays:
ColumnWhat it shows
NameThe test case title
Created ByWho added it
SourceHow it was created — AGENT (generated by Megumi), Manual (written by hand)
PriorityCritical, High, Medium, or Low — shown with a coloured dot
TagsAny labels attached to the test case
Last RunA green dot with a date means it has been run; a dash means it has never run
CreatedWhen it was first added

Filtering and searching

The filter bar at the top of the list lets you narrow down by source, priority, or type.
  • Agent / Manual tabs — filter by how the test case was created
  • Priority dropdown — filter to Critical, High, Medium, or Low
  • Type dropdown — filter to Functional, Smoke, Regression, E2E, or Custom
The count in the header updates to reflect your active filter. Use the search bar to find a specific test case by name.

What you can do from the library

  • Open any test case to view or edit its details
  • Create a new test case manually with + New Test Case
  • Select multiple test cases to add them to a suite or delete them in bulk
  • Filter by source, priority, or type to find what you need quickly

How test cases fit into your workflow

Test cases are the building blocks that suites are made of. The typical flow is:
  1. Create test cases — in Test Studio by prompting Megumi, or manually
  2. Add them to suites — group related cases for a feature, flow, or release cycle
  3. Run the suite — Mahoraga executes each case and reports results
A test case exists independently of any suite. One test case can belong to multiple suites simultaneously — editing it in the library updates it everywhere.