Conversation
pratushnyi
approved these changes
May 8, 2026
Allure Report Summary
|
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 a new
allure-selenium-bidimodule for Selenium users who enable WebDriver BiDi. The integration automatically enriches Allure test results with aggregated browser console log and network metadata attachments, without requiring per-test cleanup code. If BiDi is unavailable or unsupported for a driver session, the integration degrades silently and does not affect the test outcome.Users can wrap a Selenium driver with
AllureWebDriverBiDi:By default, the integration captures logs and network metadata, attaches only non-empty data, and redacts sensitive headers such as
Authorization,Cookie,Set-Cookie, andX-Api-Key. The network attachment includes request and response metadata exposed by Selenium’s stable BiDi API, but does not capture request or response bodies.Checklist