Lost test sequence numbers in xUnit

[dimkin-eu]

I'm submitting a ...

• bug report
• feature request
• support request

What is the current behavior?

Sequence of tests is unknown

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

What is the expected behavior?

some sequence nr. near test ( also adding extra sorting to existing name/duration/status)

Please tell us about your environment:

• Allure version: 2.1.1
• Test framework: [email protected]
• Allure adaptor: [email protected]
• Generate report using: [email protected]

Other information

[just-boris]

This is actually a severe item for Cucumber specs. All my steps are messed up and I do not know what goes after each other.

[dimkin-eu]

It kicks everything, not only cucumber, debugging of which failed after what not possible anyhow

[slipwalker]

Agreed. It is really challenging to get from the report what was going on and what the initial test sequence was, particularly for those people who might not have access to the source code.