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

Executor file ​

WARNING

This page describes a data format used by Allure and its adapters for test frameworks. Understanding this format is not necessary for using Allure in your project. For a more high-level description of the process of building a report, see How it works.

The executor.json file in the test results directory, if present, should contain information about the CI build that produced the test report. It is automatically generated by various CI integration plugins.

Example:

json
{
  "reportName": "Build #1234",
  "buildOrder": 1234,
  "reportUrl": "http://example.org/build#1234/AllureReport",
  "name": "Jenkins",
  "type": "jenkins",
  "buildName": "allure-report_deploy#1234",
  "buildUrl": "http://example.org/build#1234"
}

Report properties ​

  • reportName (string) — the name to be shown on top of the Overview tab. When not set, it defaults to “Allure Report”.

History-related properties ​

These fields will be copied into the report's history files so that future reports can link back to the current one.

  • buildOrder (integer) — the identifier for this build's columns on future trend graphs.
  • reportUrl (string) — the URL at which this test report will be located.

Build properties ​

These fields affect the “Executor” block in the test report. The purpose of the block is to show what CI build produced the current report, with an optional link to that CI build.

  • name (string) — the name of the CI server or plugin.
  • type (string) — the type of the CI tool. This affects the icon next to the name. Allowed values are: “jenkins”, “bamboo”, “teamcity”, “gitlab”, “github”, “circleci”, “bitbucket”.
  • buildName (string) — the name of the CI build that produced the current report. Normally, a CI integration plugin includes a unique build identifier into this name.
  • buildUrl (string) — the URL of the CI build.
Pager
Previous pageEnvironment file
Next pageHistory files
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.