jmix-verify-bootrun: add Vaadin UI driving notes to Gate 3 - #30
Open
knstvk wants to merge 2 commits into
Open
Conversation
knstvk
marked this pull request as ready for review
August 5, 2026 16:46
glebfox
approved these changes
Aug 6, 2026
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.
Fixes #29.
Drafted from a field report while the problem was fresh, by the agent that hit it. It is unreviewed: treat the wording as a starting point, not a proposal to merge as-is.
Change
Adds a
### Driving a Jmix/Vaadin UIsubsection to Gate 3, plus one pointer sentence in step 3 of the walk. The four points are the ones that each cost failed tool calls during a real walk: wait for the Vaadin client to finish rendering before the first snapshot or screenshot; retake the snapshot before every interaction because refs go stale after each action; prefer refs from the current snapshot over role/name locators forvaadin-*components, with a DOM-query fallback when a component exposes no usable role; and treat a disabled action as a likely precondition (a required selection or entity state) rather than a defect.