Support multiple filter conditions (include / exclude) on the same field

Problem / Background

We frequently filter test cases by Region to define market-specific test scopes (e.g. JP-only behavior, compliance differences, partner rollouts).

Currently, Testiny’s filter UI only allows one condition per field, which makes it impossible to express common filtering logic such as:

  • Include test cases that contain JP

  • Exclude test cases that also contain other regions (e.g. TW, TH)

Because of this limitation, QA teams need to manually filter test cases at the test plan level before creating test runs, which adds significant manual effort. Supporting the same include / exclude filtering when creating test runs would greatly improve efficiency and accuracy.

Please reference: How to filter title with multiple conditions


Current Behavior

  • Region is stored as a text or multi-value field (e.g. JP, TW, TH, BR)

  • The filter supports only a single condition per field (e.g. Region contains JP)

  • It is not possible to combine include and exclude conditions on the same field within a single query (e.g. Region contains JP AND Region does not contain TW)

As shown in the attached test plan screenshot, include and exclude conditions must currently be defined as separate condition groups (e.g. one group for Region ~ JP, another for Region !~ TW, TH, BR).

However, these conditions cannot be evaluated together as a single logical query when creating test runs.

The suggested workaround using an “exact match” operator is not sufficient, because it can only match one fixed combination of values per query and cannot express include / exclude logic on the same field.


Example

Test cases:

  • Case A: JP, TW, TH, BR

  • Case B: JP, HK, BR

Filter condition:

  • Include JP

  • Exclude TW, TH

Expected result:
Only Case B is returned.

Thank you for this feature request!
I can totally understand your need for this feature. On the backend side, we already support all kind of combinations, but the frontend UI is lagging a bit behind :grimacing:

If somebody reads this request and would also like to have this feature, make sure to vote for this topic. We do consider the number of votes for feature requests in our roadmap and priority planning.

Best regards,
Alex