test: add a real Lambda Feedback export as test data - #40
Merged
Merged
Conversation
Add the ME2 Introduction question set exactly as Lambda Feedback exported it, with a short description of the export's JSON, so the suite can be checked against what the platform really produces. Further exports are added as sibling folders. Exclude the exports from pre-commit: its JSON formatter and whitespace hooks would otherwise rewrite them and they would stop being real exports. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Adds one real question set exactly as Lambda Feedback exported it, so in2lambda can be tested against what the platform actually produces rather than against its own templates.
What's in it
tests/fixtures/exports/me2_introduction/: the ME2 Introduction set (six questions and three images), byte-for-byte as exported. It covers symbolic, numeric-with-units and multiple-choice answer boxes, feedback cases, text between answer boxes, and worked solutions split into steps.tests/fixtures/exports/README.md: a short description of the export's JSON, checked against these files. Further exports go in as sibling folders..pre-commit-config.yaml: excludes the exports. The JSON formatter and whitespace hooks would otherwise rewrite them on commit, and they'd stop being real exports.What's not in it
No test code. Using this data is the job of the next change: a harness that loads every export here, writes it back and compares, and that picks up a new export without any code change.
🤖 Generated with Claude Code