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

Allure TestNG configuration ​

This page describes the configuration options that affect the behavior of Allure TestNG.

To set the configuration options, create a allure.properties file in your project's src/test/resources directory. Allure TestNG loads the configuration into the JVM system properties for the test runtime.

allure.label.⟨NAME⟩ ​

properties
allure.label.epic = Authentication
allure.label.severity = blocker

Assign an arbitrary label to all the tests in the current test run.

allure.link.⟨TYPE⟩.pattern ​

properties
allure.link.issue.pattern = https://jira.example.org/browse/{}

Define a link pattern — a template that can be used to construct full URLs from short identifiers, see the reference.

The value must be a string pattern containing {} at the position where the identifier should be placed. The pattern will be applied when processing any link of the given TYPE.

You can use the option multiple times, thus defining multiple link patterns for different link types.

allure.results.directory ​

properties
allure.results.directory = build/allure-results

Path to the directory where Allure TestNG will save the test results, see How it works. If the directory does not exist, it will be created. Defaults to allure-results.

allure.testng.hide.disabled.tests ​

properties
allure.testng.hide.disabled.tests = true

In Allure, all tests from a run are reported by default. This includes disabled tests, which are marked as 'skipped' in the report. However, you can modify this behavior.

To hide disabled tests from the report, set the allure.testng.hide.disabled.tests variable to true. This will exclude these tests from the report.

allure.testng.hide.configuration.failures ​

properties
allure.testng.hide.configuration.failures = true

Allure, by default, treats configuration failures (e.g. errors in @BeforeMethod or @AfterMethod methods) uniquely. It generates a separate 'fake' test result for each configuration failure. This approach is adopted because configuration failures lead to the skipping of all dependent tests, which are then reported as skipped. The 'fake' test result explicitly shows the error in the configuration method, aiding in easier identification and troubleshooting of the issue.

To prevent Allure from creating separate results for failed configuration methods, set the allure.testng.hide.configuration.failures variable to true. This will disable the reporting of failed configuration methods as separate test results.

Pager
Previous pageGetting started
Next pageReference
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.