Skip to content

allure-junit-platform missing report exclusion for allure-cucumber8-jvm #1497

Closed

Description

@USSQA

Problem

allure-junit-platform has exclusion code in AllureJunitPlatform.shouldSkipReportingFor(TestIdentifier) to avoid double-reporting test cases that other Allure adapters already report. Currently it explicitly checks whether allure-cucumber7-jvm is in the classpath, meaning that the new allure-cucumber8-jvm package is not excluded from junit reporting. This causes the tests to get reported twice in different parts of the report.

Screenshots

Before (running with allure-cucumber7-jvm and Cucumber 7):

Image

After (running with allure-cucumber8-jvm and Cucumber 8):

Image

The duplicated scenarios at the top level don't have any steps reported (since they were reported by the junit-engine plugin)

Proposed Fix

AllureJunitPlatform.shouldSkipReportingFor(TestIdentifier) needs an additional check similar to HAS_CUCUMBERJVM7_IN_CLASSPATH for allure-cucumber8-jvm as well to avoid double-reporting.

What Allure Integration are you using?

allure-junit-platform

What version of Allure Integration you are using?

3.1.0

What version of Allure Report you are using?

3.22.1

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. added theissue type on Nov 3, 2026
  2. added a commit that references this issue on Nov 9, 2026
    b2258e3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions