Currently, the report server supports generating reports from Playwright blobs, but it only uses built in HTML report. We can add posibility to specify which built-in Playwright reporters (e.g., list, dot, line, junit, json) can be also used during the report generation process.
Feature request:
• Add support for passing built-in Playwright reporters as an option when generating the server report.
• Ensure compatibility with multiple reporters (e.g., ['html', 'junit']).
• Expose configuration through CLI and/or API.
Why this is useful:
• Teams often need additional reporting formats (like junit for CI/CD integration).
• Enables broader compatibility with existing Playwright workflows.
• Reduces the need to rerun tests with separate reporter configs just to get extra formats.
Acceptance criteria:
• User can specify built-in reporters when generating server report.
• Reports are correctly generated and saved alongside the aggregated report. Additional reports files (xml, json, html, etc) accessible from ui, api.
• Documentation updated with usage examples.
Currently, the report server supports generating reports from Playwright blobs, but it only uses built in HTML report. We can add posibility to specify which built-in Playwright reporters (e.g., list, dot, line, junit, json) can be also used during the report generation process.
Feature request:
• Add support for passing built-in Playwright reporters as an option when generating the server report.
• Ensure compatibility with multiple reporters (e.g., ['html', 'junit']).
• Expose configuration through CLI and/or API.
Why this is useful:
• Teams often need additional reporting formats (like junit for CI/CD integration).
• Enables broader compatibility with existing Playwright workflows.
• Reduces the need to rerun tests with separate reporter configs just to get extra formats.
Acceptance criteria:
• User can specify built-in reporters when generating server report.
• Reports are correctly generated and saved alongside the aggregated report. Additional reports files (xml, json, html, etc) accessible from ui, api.
• Documentation updated with usage examples.