Wrong step order in allure-report

[IlgizVafin]

I'm submitting a ...

• bug report
• feature request
• support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

Wrong step order in allure-report.

Steps to reproduce:

1. create demo project for UI-testing based on framework webdriverio with Cucumber.
   You can use:

• boilerplate project - cucumber-boilerplate
• my demo project - https://github.com/IlgizVafin/webdriverio-demo-project2;

2. write some test scenario by Gherkin:

Feature: Broken feature

    @Broken
    Scenario: Go to github.com and press non-existent button
        When I go to https://github.com
        And I press button "Non-existent button"
        Then I expect page title "Join GitHub · GitHub"

Feature: Passed feature

    @Passed
    Scenario: Go to github.com and press signup button
        When I go to https://github.com
        And I press button "Sign up for GitHub"
        Then I expect page title "Join GitHub · GitHub"

3. run test - wdio wdio.conf.js (for example)
4. generate report - allure generate ./allure-results (for example)
5. open report and look at the step order
   
6. step order isn't correct.

What is the expected behavior?

Step order should be equal to order in *.feature scenarious.

My environment:

Allure version	2.3.4
Test framework	webdriver.io + cucumber@~2.2.0
Generate report using	[email protected]

Other information

[slipwalker]

I faced the same issue. Tests execution order is different from that Allure report shows (looks like tests order in Allure report has some random nature). Even, when for every test explicitly set priority on a test level (in case using TestNG framework for instance). I have simple test class with test methods and they have different order in Allure that they were actually executed.

[eliranshani]

Can you share when this fix will be released ?

[lrocheWB]

+1

[maciejkamela]

Have the same issue. Moreover when I run eg. 8 scenarios they are mismatched and just 5 was presented but in wrong order. I would expect the test outcome to be grouped by feature.

[lrocheWB]

@baev thanks ! https://github.com/allure-framework/allure2/releases/tag/2.3.5

It works for me.

[ravxz]

Have similar issue with TestNG DataProvider tests. The test cases under test class in report are ordered backward like: #3, #2, #1. Meanwhile, default shown order is by "name" forward.

[reedchan7]

I have the same issue in allure-java 2.13.7.. Test order is different in the allure report. Isn't this fixed?

[sarvesh371]

I am facing the same issue with pytest framework

[VanillicRipple]

+1, I have the same in allure

[poengen]

+1, Same issure here with kotest framework

[FFFFFF]

+1, Same issue with jest-junit and allure.

[SivasubramanianV]

I still see this issue in mocha wdio, the steps are back and forth