You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a component re-renders asynchronously, any exceptions thrown should be propagated to the test thread. The related question, #318, shows a case where this did not happen, making it hard to diagnose the issue with the test.
The text was updated successfully, but these errors were encountered:
After trying out a few ways to achieve this, the best option I've come across is to have the WaitFor* methods throw the any unhandled exceptions caught by the renderer. This will allow users who have async code to capture the exceptions. Sync code will simply surface the exception normally, so I think this is a pretty decent solution.
When a component re-renders asynchronously, any exceptions thrown should be propagated to the test thread. The related question, #318, shows a case where this did not happen, making it hard to diagnose the issue with the test.
The text was updated successfully, but these errors were encountered: