fix(e2e): click the button inside the Move action, not its li wrapper - #571
Merged
Merged
Conversation
The folder-sharing spec drove the new sidebar's "Secret actions" menu via
getByTestId('secret-detail-move'), but data-testid falls through to
NcActionButton's ROOT element, which is the <li> wrapper rather than the
<button> that carries the click handler. Dispatching a native click on the
<li> is a silent no-op, so SecretMoveDialog never opened and the spec failed
on the downstream '.move-form' assertion instead of at the click.
The testid resolving fine is what made this read as a dialog bug: the click
step passed and only the next assertion timed out.
Descend to the button so the handler actually fires. The sibling testids in
this spec (secret-detail-share, secret-detail-more-info) sit on NcButton and
a native <summary>, whose roots ARE the interactive element, so they are
unaffected.
Contributor
Quality Report — ConductionNL/keepiq @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| check-manifest | ✅ | ||||
| test-l10n | ✅ | ||||
| format | ✅ | ||||
| check-l10n-js | ✅ | ||||
| check-schema-l10n | ✅ | ||||
| composer | ✅ | ✅ 111/111 | |||
| npm | ✅ | ✅ 536/536 | |||
| app:check-code | ⏭️ | ||||
| info.xml | ✅ | ||||
| REUSE | ❌ | ||||
| PHPUnit | ✅ | ||||
| Newman | ✅ | ||||
| Playwright | ⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development | ||||
| Hydra gates | ✅ |
Quality workflow — 2026-08-31 14:04 UTC
Download the full PDF report from the workflow artifacts.
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.
What
tests/e2e/workflows/folder-sharing.spec.tshas failed ondevelopmentsince #479 landed. The spec drives the new detail sidebar's "Secret actions" menu, and its Move step targetsgetByTestId('secret-detail-move').data-testidfalls through toNcActionButton's root element, which is the<li>wrapper, not the<button>that carries the click handler. Dispatching a native click on the<li>is a silent no-op, soSecretMoveDialognever opens.Why it read as a dialog bug
The testid resolved fine, so the click step passed and only the next assertion timed out:
The failure names
.move-form, four lines below the step that actually did nothing.The fix
Descend to the button so the handler fires. Verified against the installed
@nextcloud/vue@9.11.0:NcActionButton's render root iscreateElementBlock("li")with the<button>inside, and it does not setinheritAttrs: false.Scope
Checked the whole class rather than the one instance. The other testids this spec clicks natively are unaffected because their roots are the interactive element:
secret-detail-moveNcActionButton<li>secret-detail-shareNcButton<button>secret-detail-more-info<details><summary>Verification
E2E does not run on PRs into
development(only on the push run), so this needs the post-merge run to confirm green.