-
Notifications
You must be signed in to change notification settings - Fork 22
Description
Describe the bug
When I use allure3 and the awesome reporter to generate a report of the tests, the ordering of the test stages is utterly wrong. For example, within the test "Download Bob" it goes, 3.0 -> 2.23 -> 2.3 -> 2.10 -> 2.9 -> 1.1 -> 2.0.
Sorting by Alphabet A-Z is somewhat improved as it goes 1.1 -> 2.1 -> 2.10 -> 2.11 -> 2.15 -> 2.2, which, while wrong, is still better.
To Reproduce
Steps to reproduce the behavior:
- Have a "suite"
- Within that suite have "steps" starting with 1.x, 2.x
- Run tests and generate a report
- Observe the odd sorting
Expected behavior
The ordering of execution (and naming) goes
1.1, 1.2, 1.3, 2.0, 2.1, 2.2, 2.3, 2.10, 2.15, 2.22, 3.0, 3.1
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: Windows
- Browser Chromium
- Version 3.3.1
Additional context
The way the vitest test is written is an outer describe.sequential, which wraps "steps".
Each step is a describe which contains a beforeAll and test(s).
An attempt was made to force ordering using allure.step("Step 1", async () => await step1()) but that hasn't seemingly changed any behaviour.