PHPackages                             ezsystems/allure-behat - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. ezsystems/allure-behat

ActiveLibrary

ezsystems/allure-behat
======================

Behat output formatter for use with Yandex Allure reporting tool

v3.3.1(3y ago)15427.3k↓42.5%111Apache-2.0PHPPHP ^7.3 || ^8.0

Since Dec 5Pushed 3y agoCompare

[ Source](https://github.com/ezsystems/allure-behat)[ Packagist](https://packagist.org/packages/ezsystems/allure-behat)[ RSS](/packages/ezsystems-allure-behat/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (7)Dependencies (8)Versions (33)Used By (11)

Allure Behat Adapter
====================

[](#allure-behat-adapter)

This is a [Behat](http://behat.org/en/latest/) extension with Formatter that produces report data for [Yandex Allure](http://allure.qatools.ru/) test reporting tool with eZ Systems modification introducing requirement of eZ Systems `allure-php-commons`.

Installation
------------

[](#installation)

To install using [Composer](https://getcomposer.org/) simply add `"ezsystems/allure-behat"` to `composer.json`:

```
...
"require": {
...
    "ezsystems/allure-behat": "~3.0.0",
...
},
...

```

Usage
-----

[](#usage)

To enable this extension in [Behat](http://behat.org/en/latest/), add it to `extensions` section of your `behat.yml` file To use Allure formatter, add `allure` to your list of formatters in `name`

```
  formatters:
    pretty: true
    allure:
      output_path: %paths.base%/build/allure
  extensions:
    Allure\Behat\AllureFormatterExtension:
      severity_key: "severity:"
      ignored_tags: "tag_ignore"
      issue_tag_prefix: "JIRA:"
      test_id_tag_prefix: "BUG:"
```

Here:

- `output_path` - defines the output dir for report XML data. Default is `./allure-results`
- `ignored_tags` - either a comma separated string or valid yaml array of Scenario tags to be ignored in reports
- `severity_key` - tag with this prefix will be interpreted (if possible) to define the Scenario severity level in reports (by default it's `normal`).
- `issue_tag_prefix` - tag with this prefix will be interpreted as Issue marker and will generate issue tracking system link for test case (using [**allure.issues.tracker.pattern** setting for allure-cli](https://github.com/allure-framework/allure-core/wiki/Issues))
- `test_id_tag_prefix` - tag with this prefix will be interpreted as Test Case Id marker and will generate TMS link for test case (using [**allure.tests.management.pattern** setting for allure-cli](https://github.com/allure-framework/allure-core/wiki/Test-Case-ID))

### Use attachment support

[](#use-attachment-support)

To have attachments in allure report - make sure your behat runs tests with [Mink](https://github.com/minkphp/Mink)

Allure can handle exception thrown in your Context if that exception is instance of `ArtifactExceptionInterface`and get screenshots path from it.

### How does it work?

[](#how-does-it-work)

Behat has the following test structure:

```
It has Features described in separate feature files
        Each Feature contains Scenarios
            Each scenario contains Steps

```

Allure has a bit different hierarchy:

```
    Each report contains Test Suites
        A Test Suite contains Test Cases
            Every Test Case can contain one or more Steps

```

On the other hand, Allure also supports grouping Test Cases by Feature, by Story or by Severity level.

Behat Allure formatter does the following mapping:

- Behat Test Run -> Allure Test Suite
- Gherkin Scenario (and every single Example in Scenario Outline, too) -> Allure Test Case
- Gherkin Step -> Allure Test Step

Behat Scenarios are annotated with it's feature title and description to be grouped into Allure Feature.

Behat also has tags and they are also can be used in Allure reports:

- If a tag appears in ignored\_tags configuration parameter, then it will be ignored and will not appear on Allure report
- If a tag starts with severity\_tag\_prefix, then formatter will try to interpret it's affixed part as one of the possible [Allure Severity Levels](https://github.com/allure-framework/allure-php-adapter-api/blob/master/src/Yandex/Allure/Adapter/Model/SeverityLevel.php)
- If a tag starts with test\_id\_tag\_prefix, then formatter will interpret it's affixed part as [Test Case Id](https://github.com/allure-framework/allure-core/wiki/Test-Case-ID) for your TMS
- In all other cases tag will be parsed as Allure Story annotation

### Contribution?

[](#contribution)

Feel free to open PR with changes but before pls make sure you pass tests `./vendor/behat/behat/bin/behat`

###  Health Score

45

—

FairBetter than 93% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity40

Moderate usage in the ecosystem

Community26

Small or concentrated contributor base

Maturity79

Established project with proven stability

 Bus Factor2

2 contributors hold 50%+ of commits

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~91 days

Recently: every ~105 days

Total

26

Last Release

1175d ago

Major Versions

v2.0.1 → v3.0.12019-12-11

v2.0.2 → v3.0.22020-01-13

v2.0.3 → 3.1.x-dev2020-04-17

v2.0.5 → v3.3.02022-01-04

v2.0.6 → 3.3.x-dev2023-02-28

PHP version history (3 changes)1.0.0PHP >=5.5

v3.1.1PHP ^7.1

v3.3.0PHP ^7.3 || ^8.0

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/681611?v=4)[Ibexa Bot](/maintainers/ezrobot)[@ezrobot](https://github.com/ezrobot)

![](https://avatars.githubusercontent.com/u/130489?v=4)[Łukasz Serwatka](/maintainers/lserwatka)[@lserwatka](https://github.com/lserwatka)

---

Top Contributors

[![mnocon](https://avatars.githubusercontent.com/u/10993858?v=4)](https://github.com/mnocon "mnocon (18 commits)")[![eduard-sukharev](https://avatars.githubusercontent.com/u/3235378?v=4)](https://github.com/eduard-sukharev "eduard-sukharev (11 commits)")[![m-tyrala](https://avatars.githubusercontent.com/u/23000531?v=4)](https://github.com/m-tyrala "m-tyrala (9 commits)")[![micszo](https://avatars.githubusercontent.com/u/13622502?v=4)](https://github.com/micszo "micszo (7 commits)")[![webhdx](https://avatars.githubusercontent.com/u/10212760?v=4)](https://github.com/webhdx "webhdx (6 commits)")[![kacper-wieczorek-ibexa](https://avatars.githubusercontent.com/u/79905560?v=4)](https://github.com/kacper-wieczorek-ibexa "kacper-wieczorek-ibexa (2 commits)")[![katarzynazawada](https://avatars.githubusercontent.com/u/42930265?v=4)](https://github.com/katarzynazawada "katarzynazawada (1 commits)")[![pbisaga](https://avatars.githubusercontent.com/u/78412233?v=4)](https://github.com/pbisaga "pbisaga (1 commits)")[![robot-bucket](https://avatars.githubusercontent.com/u/135020565?v=4)](https://github.com/robot-bucket "robot-bucket (1 commits)")[![tikolakin](https://avatars.githubusercontent.com/u/5860505?v=4)](https://github.com/tikolakin "tikolakin (1 commits)")[![adamwojs](https://avatars.githubusercontent.com/u/211967?v=4)](https://github.com/adamwojs "adamwojs (1 commits)")

---

Tags

BDDBehatallure

###  Code Quality

TestsPHPUnit

Code StylePHP CS Fixer

### Embed Badge

![Health badge](/badges/ezsystems-allure-behat/health.svg)

```
[![Health](https://phpackages.com/badges/ezsystems-allure-behat/health.svg)](https://phpackages.com/packages/ezsystems-allure-behat)
```

###  Alternatives

[sensiolabs/behat-page-object-extension

Page object extension for Behat

1166.5M27](/packages/sensiolabs-behat-page-object-extension)[laracasts/behat-laravel-extension

Laravel extension for Behat

2611.3M12](/packages/laracasts-behat-laravel-extension)[dvdoug/behat-code-coverage

Generate Code Coverage reports for Behat tests

593.6M37](/packages/dvdoug-behat-code-coverage)[bex/behat-extension-driver-locator

Driver locator tool for behat extensions

385.2M4](/packages/bex-behat-extension-driver-locator)[ciaranmcnulty/behat-stepthroughextension

Extension for behat to help debug failing scenarios

601.6M5](/packages/ciaranmcnulty-behat-stepthroughextension)[allure-framework/allure-behat

Allure Behat integration

13179.9k](/packages/allure-framework-allure-behat)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)