Spinner logo QXQA

Did You Know?

Home / Test Cases / Advanced Test Case Search, Filters & Saved Presets

Advanced Test Case Search, Filters & Saved Presets

AXQA provides server-side search and advanced filtering for large Test Case libraries.
Multiple filters can be combined using AND or OR logic, and frequently used filter configurations can be saved as reusable presets.


Why it matters

  • Makes large Test Case repositories easier to navigate.
  • Helps teams isolate exactly the Test Cases needed for a specific activity.
  • Allows frequently used views to be saved and reused.

When to use it

  • When a project contains many Test Cases.
  • When preparing a specific regression or release scope.
  • When locating Test Cases by assignee, priority, group, build, or execution source.
  • When the same filters are used regularly.

Core concepts

  • Global Search – Searches multiple commonly used Test Case fields at once.
  • Field Filter – Filters one specific Test Case field.
  • Operator – Defines how the selected value should be matched.
  • AND Logic – Every filter must match.
  • OR Logic – At least one filter must match.
  • Filter Preset – A saved Test Case search and filter configuration.

How it works

  1. Enter a Global Search value or create one or more advanced filters.
  2. Choose the field and comparison operator.
  3. Add additional filters if needed.
  4. Select whether filters should use AND or OR logic.
  5. AXQA applies the filters to the Current Project.
  6. Save the configuration as a preset when it should be reused later.

How to use it

Step 1: Use Global Search

Enter text in the Search field.

Global Search currently checks common Test Case information including:

  • Title
  • Assigned User
  • Category
  • Priority
  • Group

The assigned-user search can match available user identity information such as username, first name, or last name.


Step 2: Create an advanced filter

Select a field from the Filter panel.

Available fields can include:

  • Title
  • Assign To
  • Bug
  • Category
  • Execution Source
  • Priority
  • Group
  • Environment
  • Build / Version / Platform
  • Created By
  • Created At
  • Progress

Step 3: Choose an operator

AXQA supports filter operators including:

  • Contains
  • Equals
  • Not Equals
  • Starts With
  • Ends With
  • Less Than
  • Less Than or Equal
  • Greater Than
  • Greater Than or Equal
  • Is Empty
  • Is Not Empty

Use numeric operators for values such as Progress where applicable.


Step 4: Combine filters

Add multiple filters to create a more specific view.

Example:

Priority = Critical

AND
Execution Source = Server
AND
Progress < 100

This can identify high-priority Server Test Cases that are not fully executed.


Step 5: Use AND or OR matching

Choose:

All (AND)
Every filter must match.

Example:

Priority = Critical
AND
Group = Regression
 
Any (OR)
At least one filter must match.

Example:

Priority = Critical
OR
Priority = High

Step 6: Save a Filter Preset

After configuring the view:

  1. Enter a Preset Name.
  2. Click Save.
  3. AXQA stores the current filter configuration for reuse.

The saved preset can include:

  • Filters
  • Global Search
  • Sort configuration
  • Sort direction
  • Page size
  • AND / OR filter logic

Step 7: Apply or delete a preset

Select an existing preset and click Apply to restore its configuration.

Delete presets that are no longer needed.


Best practices

  • Create presets for recurring QA activities such as Smoke, Regression, or Release Readiness.
  • Use AND logic when narrowing a specific execution scope.
  • Use OR logic when combining alternative values.
  • Use Progress filters to locate unfinished testing.
  • Keep preset names clear and purpose-driven.

Common mistakes

❌ Adding several filters but using the wrong AND / OR mode.
✔ Confirm whether all conditions or only one condition should match.

❌ Assuming Tags are included in Global Search.
✔ Use the supported Global Search fields and structured metadata such as Category, Priority, and Group.

❌ Rebuilding the same filter every day.
✔ Save recurring filter configurations as presets.


Security & permissions

  • Filters only operate on Test Cases available in the Current Project.
  • Saved presets are associated with the relevant project and user context.
  • Filters do not bypass normal project-access controls.
  • Filter values are processed by the server using supported fields and operators.

Related documentation

  • Test Case Manager Overview
  • Organizing Test Cases with Metadata
  • Inline Editing & Bulk Test Case Changes
  • Test Case Progress & Custom Step Statuses

Tools

A+ A-

Version

1.2