The Problem
Currently, when using playwright-bdd with ReportPortal, test execution results are not well-structured in the ReportPortal UI. Only raw logs are visible without clear mapping of:
- Feature → Scenario → Step
- Which step failed
- Stack trace of failed steps
- Screenshot attachments
- Duration of each step or scenario
This limits the ability to analyze test failures effectively, especially in large-scale or CI-driven projects.
Current Behavior:
- All steps are logged as plain text logs in a single test entry
- No hierarchy of step execution
- No error trace or screenshot attachment per step
- Difficult to trace which Given/When/Then step failed
Proposed Solution
Expected Behavior:
When integrated properly with ReportPortal, each test should be reported in a structured manner:
- Features → Scenarios → Steps
- Each step reported as a separate entry (with status: PASSED / FAILED / SKIPPED)
- Failed step includes:
- Stack trace
- Screenshot
- Timestamp
Ability to attach logs and artifacts to individual steps
Additional Context
No response
Priority Level
High
The Problem
Currently, when using playwright-bdd with ReportPortal, test execution results are not well-structured in the ReportPortal UI. Only raw logs are visible without clear mapping of:
This limits the ability to analyze test failures effectively, especially in large-scale or CI-driven projects.
Current Behavior:
Proposed Solution
Expected Behavior:
When integrated properly with ReportPortal, each test should be reported in a structured manner:
Ability to attach logs and artifacts to individual steps
Additional Context
No response
Priority Level
High