Sebastian "Sebbie" Silbermann
Sebastian "Sebbie" Silbermann
I think this is up to you to handle exceptions thrown from event handlers. I don't remember of the top of my hat but this also depends on your testing...
How to mock event handler function defined on parent component and geting invoked on child component
Support requests filed as GitHub issues often go unanswered. We want you to find the answer you're looking for, so we suggest checking out our [community discord](https://testing-library.com/discord) and see if...
It doesn't look like this bug report has enough info for one of us to reproduce it. Please provide a CodeSandbox (https://react.new), or a link to a repository on GitHub....
> This doesn't make sense to me, any particular reason for doing this @eps1lon? Because we're not acting when we wait for something to happen. Anything wrapped in `act` will...
> Is this documented somewhere? I guess the [documentation for `act()`](https://reactjs.org/docs/testing-recipes.html#act) could be more explicit about this. It's somewhat implied by "state updates have been processed at the end" but...
Thanks for the report. This is probably an old issue. It's caused due to the timing of when the state updater function runs. If you capture the value, the test...
Just to be clear: The code is working fine with manual testing in a browser. It only fails with our `fireEvent.change` implementation. So we do want to keep an eye...
For issues with `user-event` please file an issue with `testing-library/user-event`. This issue is just about `fireEvent.change`.
> Using component from next/script for inline colour mode script. Can you elaborate what behavior you're seeing without this change, what behavior the change results in, and why we should...
> Sorry if I made any mistakes raised_handsblush I didn't mean to imply that. I was wondering what this change is doing in the first place or what it's intended...