Post

Hi @ricky.fm, @danabra.mov! I'm trying to migrate vitest-browser-react to use the new `await act` approach. I have a test where I try to assert a suspended component shows fallback and then the content when it's ready. I remember reading there's a threshold for showing fallback but couldn't find it.

Is there any reference you can point me to? Thanks!

What’s the issue? act should wait for the fallback?

The behavior is inconsistent. If I simulate a promise that takes 1000ms to resolve it will show the fallback and if my promise takes 300ms it doesn’t show the fallback and just waits for the content to appear. My question is if there’s a threshold for showing the fallback on the client side

Or if I’m testing something that is entirely a react implementation detail that shouldn’t concern vitest-browser-react while using await act. And thanks for the reply, I appreciate it.

There is some waiting but I’d need to see the test to say exactly what’s happening.