Improve Karate result reporting and runtime evidence - #1363
Merged
Conversation
baev
added
the
pr:improvement
pratushnyi
approved these changes
Jul 30, 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
2 participants
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
Improves Allure reporting for Karate 2 so each top-level scenario produces exactly one result.
callandcalloncescenarios, including nested calls, now appear beneath their caller instead of inflating the reported test count, while parallel execution keeps each scenario’s evidence isolated.Adds rich HTTP request and response exchanges, failed-step attachments, multipart embeds, and image diffs. Karate reporting privacy settings and logging masks are applied before evidence is written, preventing suppressed or sensitive details from leaking into results.
JUnit Platform now leaves Karate’s JUnit 5 and JUnit 6 nodes to the dedicated Karate integration, preventing duplicate results while continuing to report ordinary Jupiter tests. Optional Karate classpath mismatches no longer prevent JUnit Platform reporting from starting.
fixes #1085
fixes #1127
fixes #1143
Checklist