Closed KevinBon closed 6 months ago
Uh oh! @KevinBon, the image you shared is missing helpful alt text. Check your issue body.
Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.
Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.
Uh oh! @KevinBon, the image you shared is missing helpful alt text. Check your issue body.
Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.
Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.
Uh oh! @KevinBon, the image you shared is missing helpful alt text. Check your issue body.
Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.
Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.
@testing-library/dom
version: 9.3.1@testing-library/react
version 14.0.0jasmine@5.1.0
Relevant code or config:
What you did:
I added logs to demonstrate that the
waitFor
callback has been called even after it has been resolved from a timeout.What happened:
After the
waitFor
is resolved (see:spec finished: ✅
),spec waitfor:callback
is still being invoked.PS: Log points added to surface internal
react-testing-library
,dom-testing-library
andjasmine
callsReproduction:
Problem description:
The following issue can only be seen when the jasmine.Clock is installed against
waitFor
.To prevent any side-effect (e.g: the
waitFor
callback modifies the global environment), thewaitFor
callback should never be invoked once it "finishes/resolves"Suggested solution:
https://github.com/testing-library/dom-testing-library/pull/1271