Repository navigation
The verifier: check, recording and verdict (mobiumdev/mobium#281) - #18
Merged
Merged
Conversation
…v/mobium#281) An example for each of the three tools on every surface, the guide copied from Mobium's docs, and why none has a picture: each reads a recording, not a device.
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.
Examples for the three tools mobiumdev/mobium#281 added, in canonical.json and all five clients, and docs/guides/verifier.md copied with the other guides. The Go example uses the new
CheckOptions;checkasksopenai:qwen2.5:14b, the judge the guide measured, not the default.None has a screenshot: each reads a recording, not a device (
no-picture.json).Checked locally against mobium main after #281:
npm run gen,npm run check(122 scenarios and every client's snippets, 0 problems) andnpm run build.