medplum / medplum / 25935689627 / 1

92%

main: 92%

push

github

Fix `act()` warnings in provider tests (#9224)

* Fix `act()` warnings in Provider tests

When using `userEvent`, that tool already wraps the effects in React's
`act`. These redundant outer wrappers cause issues about "not configured
to support act(...)" to spew into the test output.

Unwrapping these removes that output noise and cleans up the test code
little bit.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Noah Silas <noah@medplum.com>

* Fix `act()` warnings in provider tests

The `<MultiResourceInput>` component (used by `<ResourceInput>`, which
is used by these components) wraps some of its setup actions related to
setting up the default value in a promise deferral. These tests then
were not capturing those events inside of an `act()` wrapper, leading to
noise in the test output like "An update to MultiResourceInput not
wrapped in act...".

Adding `await act(async () => {})` to these tests lets those updates get
captured by the test helpers and removes that noise.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Noah Silas <noah@medplum.com>

* Fix `act()` warnings in CoverageRequestInbox tests

Two "Check Eligibility" error-notification tests used the native
element.click() method, which fires the event synchronously outside of
any act() context.  The async Mantine notification state update that
followed then triggered "An update to Notifications not wrapped in
act(...)" warnings.  Replace with userEvent.click(), which wraps the
interaction in act() and lets waitFor() properly observe the result.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Noah Silas <noah@medplum.com>

---------

Signed-off-by: Noah Silas <noah@medplum.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

21933 of 24761 branches covered (88.58%)

Branch coverage included in aggregate %.

44456 of 47202 relevant lines covered (94.18%)

18641.61 hits per line