allure-framework / allure-framework/allure3

Awesome: sub-step counter shows the number of direct sub-steps only

Open
#235 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
401
Forks
58
Avg merge
2d 20h
Merged PRs (30d)
34

Description

**Describe the bug**
If a test has multiple nested steps, the number of sub-steps is displayed next to the parent step's name. Unlike in Allure 2, Allure Awesome only displays the number of direct sub-steps in this case, rather than the total number of all sub-steps (including the children of direct sub-steps, their children, and so on).

This is especially noticeable when a step has failed sub-steps nested several levels deep. #210 has implemented an indicator that displays the total number of such sub-steps next to the parent step's name. Unlike the counter for the total number of sub-steps, it counts failed sub-steps recursively, which creates a misalignment between the two numbers.

**To Reproduce**
Steps to reproduce the behavior:
1. Create the following test result:
```json
{
"name": "Foo",
"fullName": "foo",
"historyId": "foo",
"testCaseId": "foo",
"status": "failed",
"stage": "finished",
"steps": [
{
"type": "step",
"name": "Step 1",
"status": "passed",
"stage": "finished",
"steps": [
{
"type": "step",
"name": "Step 1.1",
"status": "passed",
"stage": "finished",
"steps": [
{
"type": "step",
"name": "Step 1.1.1",
"status": "passed",
"stage": "finished"
}
]
}
]
}
]
}
```
2. Generate and open the report.
3. Navigate to the test and check the counter next to the parent step's name.

**Expected behavior**
The counter should display `2` instead of `1`.

**Screenshots**

Image

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue by generating the report from the nested JSON test result and inspect where the Awesome UI renders the sub-step counter next to the parent step. Confirm that the counter includes nested descendants recursively and displays 2 for the provided example.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.