evals metadata in builtin JUnit reporter#22
Open
giovanni-guidini wants to merge 1 commit intomainfrom
Open
Conversation
These changes annotate the `testTask` in a way that the built-in JUnit reporter can expose the evals metadata - similar to what is done for the JSON reporter. The formatting is discussed at length [here](https://www.notion.so/sentry/Evals-Schema-for-JUnit-XML-2098b10e4b5d80609d62f5beffc3de26?source=copy_link) JUnit is a very pervasive format, well established in the industry.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #22 +/- ##
==========================================
+ Coverage 84.50% 86.43% +1.93%
==========================================
Files 4 4
Lines 400 457 +57
Branches 115 134 +19
==========================================
+ Hits 338 395 +57
Misses 62 62
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
dcramer
reviewed
Jul 29, 2025
| name: "Factuality", | ||
| score: 0.9, | ||
| metadata: { | ||
| llm_judge: "gemini_2.5pro", |
Member
There was a problem hiding this comment.
should we consider just using the term model here?
aside I think metadata might be entirely arbitrary in scorers
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.
These changes annotate the
testTaskin a way that the built-in JUnit reporter can expose the evals metadata - similar to what is done for the JSON reporter.The formatting is discussed at length here JUnit is a very pervasive format, well established in the industry.
As an example, generating the JUnit report for the tests in the repo we get for one of the tests: