allure-framework / allure-framework/allure-js
[Playwright][Feature] Show parsed stacktrace in the report
- Dominant language
- TypeScript
- Stars
- 281
- Forks
- 137
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 13
Description
It would be great if parsed stack trace would appear in the Allure report like in the line (built-in) reporter. It would more convenient to understand where the test broke.
Allure:

Line:
```
Error: expect(received).toBeTruthy()
Received: false
11 | await loginPage.typeLoginInformation('user', 'pass')
12 | await loginPage.clickSubmit()
> 13 | await feedPage.mainHeader.assertUserMenuButtonIsVisible()
| ^
14 | })
15 |
at /Users/mindaugasm/web-e2e-tests/pages/components/MainHeader.ts:22:59
at TestTypeImpl._step (/Users/mindaugasm/web-e2e-tests/node_modules/@playwright/test/lib/test/testType.js:196:7)
at MainHeader.assertUserMenuButtonIsVisible (/Users/mindaugasm/web-e2e-tests/pages/components/MainHeader.ts:21:5)
at /Users/mindaugasm/web-e2e-tests/tests/BasicTests.ts:13:3
at WorkerRunner._runTestWithBeforeHooks (/Users/mindaugasm/web-e2e-tests/node_modules/@playwright/test/lib/test/workerRunner.js:426:7)
```
Contributor guide
Research direction
The issue provides a Playwright failure example and expected parsed stack trace, but names no repository file, test, or entry point. Begin by locating the Playwright integration and report-generation path, then compare its output with Playwright’s built-in line reporter. Done means the Allure report displays the parsed stack trace for the shown failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100