kevinveenbirkenbachandClaude Opus 5 58f92cc857 test(roles): drop the persona callbacks that cannot assert anything ...

personas/utils/interaction.js requires every persona scenario to drive a
real role-specific interaction and refuses to supply a generic fallback,
because a "click any visible link" assertion tests nothing role-specific.
All 47 roles carrying an `adminInteraction` had rebuilt exactly that
fallback. Seven of them now assert admin rights for real; these 40 cannot.

36 declare `PERSONA_ADMINISTRATOR_BLOCKED=true`, and `runAdminFlow` returns
at its first guard long before `runRoleInteraction`, so those callbacks have
never executed in any variant. port-ui is the opposite case: its callback
does run and passes silently, because the role has no admin tier for the
locator to find. Writing a strict assertion into either is worse than the
vacuous one it replaces, because nothing would ever observe it failing.

The same module sanctions passing no callback at all, which leaves the
persona scenario asserting the auth chain it already covers. After this the
number of callbacks describes the coverage that exists instead of implying
one that does not. In 14 specs `expect` and `resolveTimeout` were used only
by the deleted blocks and go with them.

mobilizon's TODO named `mix mobilizon.users.modify --enable-admin`. Upstream
knows only `--admin`, and the converger that will resolve that entry lives
on feature/designer in faee47c6b7, so the bullet points there instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-10-13 15:07:14 +02:00

..

.nocheck

…

playwright.spec.js

test(roles): drop the persona callbacks that cannot assert anything

2026-10-13 15:07:14 +02:00