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

Defect categories ​

Defects can be divided into categories based on the statuses and output messages of the corresponding tests. Each defect belongs to no more than one category. It can be one of the default categories or a custom category.

On the Categories tab in a test report, the tests are grouped by their category and then by their error message. The tests that do not belong to any category are not displayed on the tab.

Allure Report Categories tab

INFO

Allure also uses the information about defect categories to build the Categories trend graph and display the Categories block on the Overview tab.

Default categories ​

Allure defines two default defect categories, both of which include tests that did not finish successfully:

  • Product defects (corresponds to the Failed status) — tests that stopped because of an assertion error.
  • Test defects (corresponds to the Broken status) — tests that stopped because of any uncaught exception other than an assertion error.

Note that if a test result matches a custom category, it is considered neither a product defect nor a test defect.

Custom categories ​

You can define any number of custom categories by placing a categories file into the test results directory (see How it works). Allure checks each test against all the categories in the file, from top to bottom. The test gets assigned the first matching category. When no matches are found, Allure uses one of the default categories if the test is unsuccessful or no category otherwise.

Some Allure plugins can generate the file automatically based on the project configuration. Check your adapter's documentation.

Link defects to Jira ​

One feature that the community frequently asks for is the ability to integrate Allure Report with Jira, YouTrack, and other task trackers. Currently, there is no such functionality in Allure Report, but we are working on implementing it.

If this is essential for you at the moment, you may consider using Allure TestOps. Like Allure Report, it allows you to manage defects. But it also allows you to link the defects to the issues on Jira, YouTrack, or other task trackers.

Pager
Previous pageSorting and filtering
Next pageVisual analytics
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.