Skip to content
Allure report logoAllure Report
Main Navigation ModulesDocumentationStart

English

Español

English

Español

Appearance

Sidebar Navigation

Introduction

Install & Upgrade

Install for Windows

Install for macOS

Install for Linux

Install for Node.js

Upgrade Allure

Getting started

How to view a report

Improving readability of your test reports

Improving navigation in your test report

Features

Test steps

Attachments

Test statuses

Sorting and filtering

Defect categories

Visual analytics

Test stability analysis

History and retries

Timeline

Export to CSV

Export metrics

Guides

JUnit 5 parametrization

JUnit 5 & Selenide: screenshots and attachments

JUnit 5 & Selenium: screenshots and attachments

Setting up JUnit 5 with GitHub Actions

Pytest parameterization

Pytest & Selenium: screenshots and attachments

Pytest & Playwright: screenshots and attachments

Pytest & Playwright: videos

Playwright parameterization

How it works

Overview

Test result file

Container file

Categories file

Environment file

Executor file

History files

Integrations

Azure DevOps

Bamboo

GitHub Actions

Jenkins

JetBrains IDEs

TeamCity

Visual Studio Code

Frameworks

Behat

Getting started

Configuration

Reference

Behave

Getting started

Configuration

Reference

Codeception

Getting started

Configuration

Reference

CodeceptJS

Getting started

Configuration

Reference

Cucumber.js

Getting started

Configuration

Reference

Cucumber-JVM

Getting started

Configuration

Reference

Cucumber.rb

Getting started

Configuration

Reference

Cypress

Getting started

Configuration

Reference

Jasmine

Getting started

Configuration

Reference

JBehave

Getting started

Configuration

Reference

Jest

Getting started

Configuration

Reference

JUnit 4

Getting started

Configuration

Reference

JUnit 5

Getting started

Configuration

Reference

Mocha

Getting started

Configuration

Reference

Newman

Getting started

Configuration

Reference

NUnit

Getting started

Configuration

Reference

PHPUnit

Getting started

Configuration

Reference

Playwright

Getting started

Configuration

Reference

pytest

Getting started

Configuration

Reference

Pytest-BDD

Getting started

Configuration

Reference

Reqnroll

Getting started

Configuration

Reference

REST Assured

Getting started

Configuration

Robot Framework

Getting started

Configuration

Reference

RSpec

Getting started

Configuration

Reference

SpecFlow

Getting started

Configuration

Reference

Spock

Getting started

Configuration

Reference

TestNG

Getting started

Configuration

Reference

Vitest

Getting started

Configuration

Reference

WebdriverIO

Getting started

Configuration

Reference

xUnit.net

Getting started

Configuration

Reference

On this page

Sorting and filtering ​

The Behaviors, Suites, Packages, and Categories tabs in a test report generated by Allure (see Improving navigation in your test report) provide various ways to sort and filter the list of tests.

Sort tests ​

Click on a label in the header to change how the tests are sorted. This affects both the sorting of groups (categories, suites, etc.) and the sorting of tests within the same group. Click on an active label again to reverse the sorting order.

Allure Report sort test results by execution order, name, duration or status

The possible sorting criteria are:

  • the order of execution;
  • the name: the title of a test or a group of tests;
  • the duration of execution;
  • the status tests finished with, see the list in Filter tests by status.

Filter tests by name ​

In the search box, enter some text to see only the tests that contain it text in their title. The filter is case-insensitive.

Allure Report filter test results by name

Filter tests by tags ​

Enter tag: followed by a comma-separated list of tags. The report will only show tests that have all the tags you've entered. The tag names are case-insensitive. Tags with whitespaces are not supported.

Allure Report filter test results by tags

Filter tests by status ​

Click on the colored buttons to hide or show all the tests that finished with a specific status.

The number on each button indicates the number of tests with this status present in the hierarchy. If there are no tests with a given status in the hierarchy, then the corresponding button reads zero and does nothing.

Allure Report filter test results by status

Filter tests by marks ​

Click on a button with an icon to enable or disable a filter by a specific mark set by Allure.

If one or more filters by marks are enabled, the report will only show those tests that have all selected marks. If no filters by marks are enabled, all tests in the hierarchy are shown.

The possible marks are: Flaky, New failed, New passed, New broken, Retried. See Test stability analysis for more details.

Allure Report filter test results by new/known errors, flaky or retried

Need more? ​

If you need to filter test results against a broader set of criteria, check out Allure TestOps. It allows you to filter by environment, layer, assignee, and other parameters. Add custom fields and use Allure Query Language to create even more advanced filters. Such filters are handy for collaborative work on test result analysis, especially if the number of tests is huge.

Pager
Previous pageTest statuses
Next pageDefect categories
Powered by

Join our newsletter

Allure TestOps
  • Overview
  • Why choose us
  • Cloud
  • Self-hosted
  • Success Stories
Company
  • Documentation
  • Blog
  • About us
  • Contact
  • Events
© 2025 Qameta Software Inc. All rights reserved.