Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
automatically call screen.debug() if there's a timeout in waitFor
See original GitHub issueThis would be particularly nice for waitForElementToBeRemoved (which would benefit from this being added to waitFor) because then people could easily see what the DOM looks like and maybe why the element has not been removed.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:8 (5 by maintainers)
Top Results From Across the Web
About Queries | Testing Library
As elements appear and disappear in response to actions, Async APIs like waitFor or findBy queries can be used to await the changes...
Read more >React Testing Library's waitFor not working - Stack Overflow
I found the answer here: React Testing Library - using 'await wait()' after fireEvent. TLDR: "You can not use wait with getBy*.
Read more >How to use React Testing library to wait for async elements, a ...
A guide on how to use React Testing Library's to wait for and test asynchronously loaded elements. Contains code examples and a step-by-step ......
Read more >Common mistakes with React Testing Library - Kent C. Dodds
Hi there I created React Testing Library because I wasn't satisfied with the testing ... You can also call screen.debug instead of debug....
Read more >Xcode 11 hangs while attaching debugger to ios process
If I launch the app on the phone and attempt to attach the debugger from ... screen to the main screen but nowhere...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe we can have an
onTimeoutoption that defaults to callscreen.debug()😃🎉 This issue has been resolved in version 7.18.0 🎉
The release is available on:
npm package (@latest dist-tag)Your semantic-release bot 📦🚀