allure-framework / allure-framework/allure-js
Failed tear down fixtures are poorly visible in the report
- Dominant language
- TypeScript
- Stars
- 281
- Forks
- 137
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 13
Description
**Describe the bug**
Failed fixtures from the `Tear Down` section of the report are hidden inside passed tests. If no other errors are present, the report shows a 100% green circle on the overview page, which is not quite true and may conceal a potential bug.
**To Reproduce**
The problem can be illustrated with allure-cypress, but most probably affects other integrations.
Steps to reproduce the behavior:
1. Create an Allure Cypress project.
2. Define the following spec:
```javascript
afterEach(() => { throw new Error(); });
it("foo", () => {});
```
4. Run Cypress, generate and open the report.
**Expected behavior**
Depends on the solution. It might be an extra placeholder test result to make the error visible similar to how it's done for [Reqnroll](https://github.com/allure-framework/allure-csharp/blob/bc189897d249f7efa6019f2f90e0c92f8ebbcf72/Allure.Reqnroll/Events/HookFinishedEventHandler.cs#L111).
**Screenshots**
Contributor guide
Research direction
No target file or test is named. Start by reproducing the afterEach failure in an allure-cypress project, then trace how Tear Down failures are represented and how the overview calculates its status; the linked Reqnroll HookFinishedEventHandler.cs shows a related integration approach. Done means a teardown failure is visible in the report and prevents an all-green overview, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, javascript, typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100