Skip to content

[Feature]: Native Support for ReportPortal Integration #341

Description

@AndyN27

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
Image

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions