Conversation
Allure Report Summary
|
pratushnyi
approved these changes
May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
This PR adds
allure-playwright, a new integration for Playwright Java that automatically reports browser actions as Allure steps. After enabling the AspectJ weaver, common Playwright actions such as navigation, clicks, fills, waits, screenshots, and related page interactions appear in the report as readable runtime steps, with sensitive parameters redacted by default.The integration also captures useful Playwright diagnostics automatically. User screenshots are attached to the current Allure step or test, and failed tests can include page screenshots, page source, traces, videos, console messages, and page errors when those artifacts are available.
Example setup:
Checklist