lizhimins opened a new pull request, #6343:
URL: https://github.com/apache/rocketmq-dashboard/pull/6343
Two frontend tests pass in isolation and fail under the load of a full-suite
run. Both depend on antd motion timing rather than on the behaviour they claim
to pin.
**`UserManagement.test.tsx` — `does not reload session details after their
drawer is closed during revocation`**
```
expect(screen.queryByRole('dialog')).not.toBeInTheDocument();
```
asserted synchronously right after the awaited reload. `rc-drawer` keeps the
dialog node in the accessibility tree until its exit motion finishes, and that
motion is timer-driven, so under load the node is still there. It failed three
consecutive full-suite runs (and the same failure reproduces on the commit
before #6113 landed, so it is not a regression from that change) and passed
every isolated run. Wrapped in `waitFor`, which still fails if the drawer
genuinely stays open.
**`K8sCertsPage.test.tsx` — `deletes a certificate after confirmation`**
```
Error: Unable to perform pointer interaction as the element has
`pointer-events: none`: BUTTON(label=删除)
```
The row is rendered by `findByText` before the table's loading mask finishes
leaving, and while it does the action buttons carry `pointer-events: none`.
This one is intermittent rather than deterministic. `userEvent.setup({
pointerEventsCheck: 0 })` is what the rest of the suite already uses for this
case (e.g. `DLQPage.test.tsx`); the click target's pointer-events state is not
the contract under test here.
Both files pass in isolation and `eslint` / `prettier --check` are clean.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
