Search Syntax

Search Syntax

The report search bar supports a powerful query language for filtering scenarios. You can combine text search, tag filtering, status filtering, and boolean operators.

Tip: Press / anywhere in the report to focus the search bar. Click the ? icon next to the search bar for a quick syntax reference.

Basic Text Search

Type any word to filter scenarios by feature name, feature description, scenario name, step text, error messages, tags (categories/labels), and diagram source.

order

You can also search by feature name to find all scenarios in a feature:

Pancakes Creation

Multiple words are treated as implicit AND — all words must appear:

order create

Quoted Phrases

Wrap text in double quotes for exact phrase matching:

"delete order"

This matches "Delete order fails gracefully" but not "Order was deleted".

Advanced Operators

When you use &&, ||, or !!, the search switches to advanced mode with full boolean expression support.

Operator	Meaning	Example
&&	AND — both sides must match	order && !!delete
||	OR — either side must match	payment || order
!!	NOT — excludes matches	order && !!delete
( )	Parentheses — group expressions	(payment || order) && !!delete

Operator Precedence

From highest to lowest:

1. !! (NOT)
2. && (AND)
3. || (OR)

Use parentheses to override precedence:

payment || order && create     → payment || (order && create)
(payment || order) && create   → matches both "payment" and "create", or "order" and "create"

Implicit AND

In advanced mode, adjacent operands without an explicit operator are joined with implicit AND. This means:

@smoke $failed "order"

is equivalent to:

@smoke && $failed && "order"

You can mix implicit and explicit operators freely.

Tag Filtering (@tag)

Filter by tags (categories/labels) using the @ prefix:

@smoke
@api && @smoke

Tags match against scenario categories and labels (case-insensitive).

Legacy Tag Expressions

When not using advanced operators (&&/||/!!), you can use Cucumber-style tag expressions with English keywords:

@smoke and @api
@smoke or @regression
not @slow
(@ui or @api) and not @slow

Note: Legacy tag expressions are only available when no advanced operators are present in the search. If you use &&, ||, or !! anywhere in the query, use @tag with those operators instead.

Status Filtering ($status)

Filter by test execution status using the $ prefix:

$failed
$passed
$skipped

Combine with other operators:

$failed && order
$passed || $skipped
@api && $failed

Note: $status is an advanced-mode feature. It activates the advanced search engine automatically, even without explicit &&/||/!! operators.

Combining Everything

You can freely mix text, tags, status, and operators:

@api && $failed && !!timeout
(order || payment) && $passed
@smoke && "expected result" && !!@slow

Examples

Query	What it matches
order	Any scenario with "order" in its name, steps, or diagram
"create order"	Exact phrase "create order"
payment || order	Scenarios containing "payment" or "order"
order && !!delete	Scenarios with "order" but not "delete"
$failed	Only failed scenarios
$failed && order	Failed scenarios containing "order"
$passed && @smoke	Passed scenarios tagged "smoke"
@api && @smoke	Scenarios with both "api" and "smoke" tags
(a || b) && c	Scenarios matching ("a" or "b") and "c"
@smoke and not @slow	Legacy tag expression — "smoke" tag without "slow" tag

What Gets Searched

The search matches against:

• Scenario display name (test method name, humanized)
• Step text (Given/When/Then steps)
• Error messages (for failed scenarios)
• Diagram source (PlantUML code behind sequence diagrams)
• Tags/categories (via @tag syntax only)
• Status (via $status syntax only)

Fallback Behaviour

If the advanced search engine encounters a parse error (e.g. unmatched parentheses), it silently falls back to legacy search, which uses simple text matching with implicit AND.