Add browser probe DOM assertions#612
Merged
Merged
Conversation
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.
Summary
assert=support towordpress.browser-probefor selector state, count, text, attribute, console-error, and page-error assertions.files/browser/summary.json, with non-advisory failures failing after artifacts are written.Fixes #605.
Verification
npm run buildnpm run command-registry-smokenpm run task-input-contract-smokenpm run browser-probe-artifact-smokenpm run browser-probe-assertions-smokenpm run agent-sandbox-code-smokeKnown blocker
npm run checkcurrently fails atrecipe-interruption-artifacts-smokewith missing manifest entryfiles/runtime-evidence/run-attestation.json. This reproduces outside the browser-probe assertion path on currentorigin/main; targeted browser-probe checks pass.AI assistance