revisit testing-library recommendation?

[gurgeous]

Hi guys. We were adding tests to our vue app and we read this recommendation:

We recommend using @testing-library/vue for testing components in applications, as its focus aligns better with the testing priorities of applications. Use @vue/test-utils only if you are building advanced components that require testing Vue-specific internals.

Unfortunately, we discovered that testing-library doesn't work with basic vue3 features like async setup/. Getting anything to work requires massive amounts of research and obscure workarounds (see testing-library/vue-testing-library#230 and https://gist.github.com/sand4rt/5da4dda9b1aec636c92b83b83cc95aee.

Now that this use case is reasonably well supported by the latest version of test-utils, do we want to revisit this recommendation? I think this paragraph was written with the best of intentions years ago, but may no longer be accurate. I feel a bit misled and maybe we can prevent others from going through that experience.

[NataliaTepluhina]

@gurgeous this is a really good suggestion. I prefer VTU over testing-library myself, and it seems the fix for async+suspense in testing library is long due. I'll look into rewriting this recommendation (unless you would like to create a PR yourself 😅 )

[gurgeous]

This is great, thank you! Your work is appreciated :)