Repository navigation
feat: complete the model-based test - #2
Merged
Merged
Conversation
Fill in the driver, so that the traces generated from the specification are replayed against the implementation and the two states are compared after every step. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
conjikidow
added a commit
that referenced
this pull request
Aug 17, 2026
Fill in the driver, so that the traces generated from the specification are replayed against the implementation and the two states are compared after every step. Co-authored-by: Claude Opus 5 (1M context) <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.
Fills in the four
TODOs the skeleton left, which is what step 1 of the tutorial asks participants to do.With the driver in place, the traces generated from the specification are replayed against the implementation,
and the two states are compared after every step.
They disagree, so
Test Rustfails here on purpose: that disagreement is what step 2 is about.