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 Newman reference ​

When collecting data for a test report, the Allure Newman adapter analyzes the Newman's native metadata, as well as special commands found in the JavaScript comments.

Note that the values in such commands cannot contain spaces.

Metadata ​

Assign a test's description, links and other metadata.

Description ​

If a Postman request has documentation, it will be used as the test's description in Allure Report.

Owner ​

  • // @allure.label.owner=⟨VALUE⟩

Set the test's owner.

js
// @allure.label.owner=JohnDoe
pm.test("Test Authentication", function () {
  // ...
});

Tag ​

  • // @allure.label.tag=⟨VALUE⟩

Set the test's tags.

js
// @allure.label.tag=WebInterface
// @allure.label.tag=Authentication
pm.test("Test Authentication", function () {
  // ...
});

Severity ​

  • // @allure.label.severity=⟨VALUE⟩

Set the test's severity.

Allowed values are: “trivial”, “minor”, “normal”, “critical”, and “blocker”.

js
// @allure.label.severity=critical
pm.test("Test Authentication", function () {
  // ...
});

Label ​

  • // @allure.label.⟨NAME⟩=⟨VALUE⟩

Set an arbitrary label for the test. This is the underlying implementation for a lot of Allure's other metadata.

You can use this command multiple times to create an array of values under the given name.

js
// @allure.label.mylabel=value
pm.test("Test Authentication", function () {
  // ...
});

ID ​

  • // @allure.id=⟨VALUE⟩

Set the test's ID.

js
// @allure.id=123
pm.test("Test Authentication", function () {
  // ...
});

Behavior-based hierarchy ​

  • // @allure.label.epic=⟨VALUE⟩
  • // @allure.label.feature=⟨VALUE⟩
  • // @allure.label.story=⟨VALUE⟩

Assign names of epics, features or user stories for a test, as part of Allure's behavior-based hierarchy.

js
// @allure.label.epic=WebInterface
// @allure.label.feature=EssentialFeatures
// @allure.label.story=Authentication
pm.test("Test Authentication", function () {
  // ...
});

Suite-based hierarchy ​

  • // @allure.label.parentSuite=⟨VALUE⟩
  • // @allure.label.suite=⟨VALUE⟩
  • // @allure.label.subSuite=⟨VALUE⟩

By default, Allure Newman uses the folder hierarchy from the Postman collection for the Allure's suite-based hierarchy. You can override the names of a test's parent suite, suite and sub-suite individually by providing the special commands in JavaScript comments.

js
// @allure.label.parentSuite=WebInterface
// @allure.label.suite=EssentialFeatures
// @allure.label.subSuite=Authentication
pm.test("Test Authentication", function () {
  // ...
});

Test steps ​

If a Postman request has multiple pm.test() calls in its “Tests” section, Allure will display them as separate test steps.

js
pm.test("Make sure the response is valid JSON", function () {
  // ...
});

pm.test("Compare the response with the expected data", function () {
  // ...
});
Pager
Previous pageConfiguration
Next pageGetting started
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.