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.

​
Viewing and editing a test case

Click any test case in the library list to open its detail panel. Every field is editable directly — click into any field and make your change. There is no Save button; changes are saved immediately. You can edit the name, instruction, expected result, platform, priority, type, and tags at any time. Before editing, check the Used in Suites section at the bottom of the detail panel. It lists every suite this test case currently belongs to. If the test case is part of active suites, changes to the instruction or expected result affect all of them.

​
Adding test cases to a suite

![](/images/image (22).png) From the library:
  1. Check the boxes next to the test cases you want to group.
  2. A bar appears at the bottom of the screen showing the count of selected cases and two options: Add to Suite and Delete.
  3. Click Add to Suite and choose an existing suite or create a new one.
From inside a suite: Use the + Test Case button inside the suite to search the library and add cases from there. From Test Studio: After generating tests in a recipe, select them in the Tests panel and click + Add to Suite.

​
Bulk actions

Select multiple test cases using the checkboxes in the library list. The action bar at the bottom of the screen shows the count of selected cases with two options:
  • Add to Suite — adds all selected cases to a suite of your choice
  • Delete — permanently deletes all selected cases
Click the checkbox in the column header to select all test cases currently visible in the list.

​
Deleting test cases

Single test case:
  1. Open the test case from the library.
  2. Scroll to the bottom of the detail panel and click Delete Test Case.
  3. Confirm the deletion.
Multiple test cases:
  1. Select them using the checkboxes.
  2. Click Delete in the action bar at the bottom.
  3. Confirm the bulk deletion.
Deleting a test case removes it from every suite it belongs to. Check the Used in Suites section before deleting anything that is part of an active suite.

​
Keeping test cases current

Test cases become outdated when the app UI changes — a button gets renamed, a screen is redesigned, a flow is restructured. An outdated instruction causes Mahoraga to fail on steps that no longer match the actual app. When the app changes, update affected test cases immediately rather than waiting for a test failure to flag it. Check the instruction against the current UI and update any element names, navigation steps, or field labels that have changed. If the change is significant enough that the old test case should be preserved for historical reference, create a new test case rather than overwriting the existing one.

​
Searching and filtering at scale

As your library grows, filtering and tagging are how you stay organised. Use the filter tabs (Agent / Manual) to see how your coverage was created — a library dominated by Agent-generated tests that have never been manually reviewed is worth auditing periodically. Use Priority + Type filters together to build targeted suite selections. For example: filtering to Critical + Functional gives you exactly the test cases that should be in your smoke suite. Use tags consistently. A test case with no tags is harder to find, harder to group, and harder to audit. Agree on a tagging convention with your team early and apply it to every test case, including generated ones.