Repository navigation
Update allure-cucumber to Cucumber version 8 #1451
Description
What problem should this solve?
Cucumber v8 introduced a number of breaking changes to some internals that currently break allure-cucumber7-jvm, making the latest Cucumber unusable in combination with Allure.
What would you like to happen?
To continue supporting the latest Cucumber version, there needs to be a new allure-cucumber package (maybe allure-cucumber8-jvm) that supports cucumber version 8.x.
Alternatives considered
No response
Additional context
No response
Activity
RaymondMouthaan commentedon Oct 7, 2026
Thanks for filing this! We're hitting the same issue and wanted to add some details in case they help.
With
allure-cucumber7-jvm3.0.0 (the latest) andcucumber-bom8.0.x oncucumber-junit-platform-engine, every scenario errors before it runs:As far as we can tell, Cucumber 8 moves to
io.cucumber:messages34, whereLocation.getLine()no longer returnsjava.lang.Long, and the plugin is compiled against the old signature. Withcucumber-bom7.34.9 the same minimal project passes and writes Allure results normally.We're staying on Cucumber 7.x for now. Thanks for all your work on Allure! 🙏
Report Cucumber 8 through the Allure Cucumber 8 adapter (#6914)