-
Notifications
You must be signed in to change notification settings - Fork 4
feat: add tests for judge consistency #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
commit: |
| /** | ||
| * Clear Mismatch: Parameter name changed. | ||
| * Reference: process_batch(items, validate) | ||
| * Candidate: process_batch(data, validate) - parameter name differs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this too strict? parameter name is different but basically everything is the same and the output is the same.
tests/judgeConsistency.test.ts
Outdated
| const { reference, candidate } = diffPair; | ||
|
|
||
| if (scoreType === "logic-equivalence") { | ||
| return `Reference diff:\n${reference}\n\nCandidate diff:\n${candidate}\n\nCompare ONLY the logical behavior (conditions, edge cases, side effects). Ignore code structure and style. Respond with JSON.`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we reuse what we have in the scores files? to keep things consistent.
|
@Aslemammad, I think I need a review before I can merge |
69e28cd to
bdfe9d5
Compare
Created judge consistency tests to ensure stable evaluation behavior when changing judge instructions.
New Files:
Modified Files:
How It Works: