Notices by Robert Roskam (raiderrobert@mastodon.social), page 2

I wrote a pair of tests. One that’s sanity check, and another that’s a parameterized test for each of the expected outcomes.

I wrote a really simple #React component that has logic inside of it. (Yes, I know that should be factored out, but it’s a toy example. So hush.)

I apologize ahead of time for the wall of text.

It’s a meme at this point about the rate of change in $frontend with the various #JS libraries.

I wanted to spend some time to understand why https://bun.sh appears to be all the rage.

But first I spent some time this week to figure out what the state of testing is—specifically for #React.

More boiler plate and configs than expected.
The relatively few examples was surprising: https://testing-library.com/docs/recipes
The lack of something as simple as a hello world component and test was surprising.

I’m going to complain now for a bit, so buckle up.

This seems _fine_, but I’m also vaguely disappointed.

I initially went back to Enyzme before figuring out that it seems to be largely community deprecated, and I should be using instead the “react-testing-library”. That took me a couple of times to grok.

So fine, let’s use the “react-testing-library”.

I’m left wondering if I’m missing something. If there’s another library that is “the way” instead….but the 18k Github stars suggest no. This is the way.

The way these docs appear to mostly want to justify their decisions and give an FAQ before dropping you into their Core API was kind of strange.

So yeah, can someone in the #javascript / #js / #React ecosystem tell me if I’m missing another more popular library that has a lot of great examples? Because this felt a little weird to me.