Found while following the skill on a Jmix 3.0.0 project.
Problem: silent — the instructions say what to exercise, not how.
Task
Render-walking a new dictionary list view plus its dialog detail view (a Department dictionary with a required reference to another entity).
Where
"Gate 3 — render walk", step 3 — "navigate to each view you created, click each button/action, fill each field".
What happened
The step says what to exercise but nothing about how, so the walk was driven partly by mutating the page: a component property was set to expand a collapsed menu group, and a field value was assigned directly. In a server-driven UI framework the server holds component state, so assigning a .value or a property in the page never reaches the server, and forcing a property on a server-bound component desynchronises client and server. The session was invalidated mid-walk and the app bounced back to the login view; the walk could not be resumed and the one save under test was left with an unknown outcome. Nothing appeared in the browser console, so it looked like an environment problem rather than a self-inflicted one. Caught only by the browser walk itself.
Suggested fix
In step 3, state that the walk must be driven only through real input events (a genuine click, real typing, Enter), and that assigning .value or any component property from the page/console must not be used — it does not reach the server and can desync the session, silently invalidating the gate. Add the read-only exception: reading the DOM to assert what rendered is fine, mutating it is not.
Found while following the skill on a Jmix 3.0.0 project.
Problem: silent — the instructions say what to exercise, not how.
Task
Render-walking a new dictionary list view plus its dialog detail view (a
Departmentdictionary with a required reference to another entity).Where
"Gate 3 — render walk", step 3 — "navigate to each view you created, click each button/action, fill each field".
What happened
The step says what to exercise but nothing about how, so the walk was driven partly by mutating the page: a component property was set to expand a collapsed menu group, and a field value was assigned directly. In a server-driven UI framework the server holds component state, so assigning a
.valueor a property in the page never reaches the server, and forcing a property on a server-bound component desynchronises client and server. The session was invalidated mid-walk and the app bounced back to the login view; the walk could not be resumed and the one save under test was left with an unknown outcome. Nothing appeared in the browser console, so it looked like an environment problem rather than a self-inflicted one. Caught only by the browser walk itself.Suggested fix
In step 3, state that the walk must be driven only through real input events (a genuine click, real typing, Enter), and that assigning
.valueor any component property from the page/console must not be used — it does not reach the server and can desync the session, silently invalidating the gate. Add the read-only exception: reading the DOM to assert what rendered is fine, mutating it is not.