Skip to content

jmix-verify-bootrun: add Vaadin UI driving notes to Gate 3 - #30

Open
knstvk wants to merge 2 commits into
v3from
feedback/29-vaadin-ui-driving
Open

jmix-verify-bootrun: add Vaadin UI driving notes to Gate 3#30
knstvk wants to merge 2 commits into
v3from
feedback/29-vaadin-ui-driving

Conversation

@knstvk

@knstvk knstvk commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

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 UI subsection 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 for vaadin-* 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.

@knstvk
knstvk marked this pull request as ready for review August 5, 2026 16:46
@knstvk
knstvk requested a review from glebfox August 5, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

jmix-verify-bootrun: Gate 3 gives no mechanics for driving a Vaadin UI

2 participants