Finding and Organizing Test Cases

Use the ContextQA test case list, search, filters, sorting, folders, labels, pagination, and test suites to maintain a scalable test library.

The ContextQA Test Cases page is the searchable inventory for test cases and reusable step groups. Use it to locate coverage, inspect lifecycle state, organize cases with folders and labels, and select cases for list actions.

Navigate to the test case list

1. Sign in to the required ContextQA workspace.
2. Confirm the intended workspace and version are active.
3. Select Test Cases in the left navigation.
4. Confirm the page heading is Test Cases and the subtitle reads Manage and Execute all your Test Cases.

Use the Test Cases and Step Groups tabs to switch between executable cases and reusable step sequences.

Understand the list

The default List view contains these verified columns:

Column	What it shows
Test Cases	Generated TC- identifier and title
Type	Platform, such as Browser or Mobile
Priority	Assigned priority or Unassigned
Result	Latest observed result, such as Passed, Failed, Aborted, or Not Executed
Status	Lifecycle status, such as Ready or In Review
Labels	Assigned labels or No labels
Created By	Creator or System
Folder	Folder name or Unorganized
Created At	Creation timestamp
Updated At	Last update timestamp
Last Run	Last run timestamp or -
Action	Row-level More actions menu

The header also includes Search, Export, the active/trash selector, Filter, column settings, refresh, New Test Case, and List/Modular view controls.

Search for a test case

1. In Search by ID or Title, enter a complete or partial TC- identifier or title.
2. Review the matching rows and result count.
3. Open the required case from the result list.
4. Clear the search value to return to the full list.

The placeholder explicitly limits the verified search scope to ID or title. Do not rely on this control to search descriptions or steps.

Filter test cases

1. Select Filter.
2. Choose one or more available criteria: Created By, Status, Test Type, Type, Priority, Latest Run Result, Created Date, Updated Date, or Labels.
3. Select Apply Filter.
4. Confirm the returned rows satisfy every visible criterion.
5. Clear the applied filter state before concluding that a case is missing.

An empty filtered result means no visible cases match the current criteria; it does not mean the cases were deleted.

Sort the list

Select a sortable column heading to change its order. The verified sortable headings are Test Cases, Priority, Created By, Folder, Created At, Updated At, and Last Run. Select the same heading again to reverse the direction, then verify the first rows follow the selected order.

Move between result pages

1. At the bottom of the table, open Rows per page to choose how many cases appear.
2. Review the displayed range and total, for example 1–10 of 7172.
3. Use the next or previous page controls.
4. Confirm that the displayed range and rows change.

Select test cases

Use Select row to select one case or Select all rows to select the rows available to the table selection control. Verify the selection count and displayed action toolbar before applying an action. Because the tested UI did not expose a stable bulk-action toolbar during safe verification, confirm each action offered by your workspace before proceeding and test destructive actions only on disposable cases.

Use List and Modular views

• List presents sortable metadata in a table and is best for search, status review, and comparison.
• Modular presents folder-based organization and is best when browsing the functional structure.

The list shows Unorganized when a test case has no folder assignment.

Organize cases with folders and labels

Folders provide the primary visible hierarchy in the test case inventory. Labels provide cross-cutting classification and filtering.

• Use a folder for a stable functional area, such as Authentication or Checkout.
• Use labels for attributes that can span folders, such as Smoke, Security, or Integration.
• Use Status for workflow state, not functional grouping.
• Use Priority for business or failure impact, not test type.

A case can display a folder and multiple labels in the list. The current list also supports Unorganized for cases without a folder.

Test case, step group, test suite, and test plan

Object	Use it for
Test case	One independently maintainable scenario and expected outcome
Step group	A reusable sequence, such as shared sign-in setup
Folder	Navigating a functional hierarchy in the test inventory
Label	Filtering cases across folders by a shared attribute
Test suite	Grouping cases that should be managed or executed together
Test plan	Defining an execution strategy and configuration for selected coverage

Do not duplicate a test case only to place the same behavior in another execution grouping. Reuse the case through the supported suite or plan relationship instead.

Practical authentication example

Create these cases using the naming pattern [Area] — [User action] — [Expected outcome]:

• Authentication — Sign in — Valid credentials
• Authentication — Sign in — Invalid password
• Authentication — Reset password — Registered email

For each case, use a fictional test account and add steps that navigate to the sign-in page, perform the named action, and verify the observable result. Place the cases in the Authentication folder if that folder exists, and apply Smoke only to the minimum release-blocking path. Add the related cases to an authentication suite when they should execute together; configure execution in a test plan rather than encoding browser or environment names in each case title.

To verify the organization, search for Authentication, filter by the chosen label, open each case to confirm its steps, and inspect its relationships. A common mistake is using Ready as a functional category; correct it by using a folder or label and reserve Status for review state.

Organization guidelines for large teams

• Name cases after observable behavior and keep one primary outcome per case.
• Search before creating a case to avoid duplicate coverage.
• Use a step group for genuinely reusable setup.
• Keep volatile environment details out of names; use execution configuration.
• Create a new suite only for a meaningful reusable grouping.
• Create a new plan only when the execution selection or configuration differs.
• Move obsolete cases to Trash only after reviewing relationships and history; permanently delete only when retention is not required.

Troubleshooting

Problem	Likely cause	Resolution
Search returns no rows	The text is not in the ID or title	Search with a shorter title fragment or the TC- identifier.
An expected case is missing	Search, filters, pagination, workspace/version, or Trash state differs	Clear search and filters, check the workspace/version and result pages, then inspect Trash.
A case shows Unorganized	No folder is assigned	Assign the case to the appropriate functional folder if your process uses folders.
A sort appears ineffective	Values on the current page are identical or blank	Check the sort indicator and compare a column with distinct values.

Limitations and permissions

• Search was verified for the UI contract Search by ID or Title; description and step search were not verified.
• Saved views and reusable saved filters were not present in the tested list.
• A separate archive lifecycle was not present; the verified lifecycle uses Trash, Restore, and Delete Forever.
• Exact bulk actions and selection limits require workspace-specific confirmation.
• Permission differences were not verified across multiple roles.

Related documentation

• Create test cases
• Manage test cases
• Manage test suites
• Create and run test plans
• Reuse steps with step groups

Frequently asked questions

How do I find a test case in ContextQA?

Open Test Cases and search by its TC- identifier or title. Clear filters and check Trash if it is not in the active results.

What is the difference between a folder and a label?

A folder provides a navigable functional location; a label provides a cross-cutting filter that can classify cases from different folders.

Does ContextQA support archive?

No separate Archive action was present in the verified test case UI. Use recoverable Trash for removal, and reserve Delete Forever for irreversible cleanup.