Add a byte[]-based overload for AllureApi.AddScreenDiff
#596
Conversation
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
epszaw
approved these changes
Oct 16, 2025
delatrie
changed the title
byte[] overload for AddScreenDiffbyte[]-based overload for AllureApi.AddScreenDiff
This was referenced Dec 23, 2025
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
Some e2e testing tools allow taking screenshots and keeping them in memory instead of writing to files (example). While there is an
AddAttachmentoverload that takes a byte array,AddScreenDiffonly allows attaching from files.This PR introduces a new
AddScreenDiffoverload, which accepts three byte arrays instead of file paths.Checklist