Frontend Subscribe to Frontend RSS feed

This is the appendix to the “Frontend Testing, Done Right” series. Whenever you hit an unfamiliar term in the series, come back here. Browse the full series Learning frontend testing means getting buried in unfamiliar words. How is a mock different from a stub? When do getBy and queryBy part ways? Why shouldn’t you take a coverage number at face value? This one page collects all of those terms — and each entry goes beyond “what it is” to “why it matters” and “when you’d use it.” ...

This is Part 1 of the “Frontend Testing, Done Right” series. Browse the full series · Glossary “Tests? But it already works.” We’ve all said it — or heard it. I said it for years. Look at the screen, click around, “yep, works,” done. But then the features pile up, and every time you touch the code a little voice asks, “if I change this, what breaks over there?” That creeping anxiety is exactly the moment tests become worth their price. ...

I built a dashboard. I was proud of it. Three lines of code using Promise.all to fetch three APIs at once — and the code review feedback was “clean.” Multiple tasks running concurrently - with Promise.all, one failure affects the whole thing Photo: Unsplash javascript Read line numbers: OFF Line-number reading help Reading line numbers aloud This button is for screen reader users. ...

At some point while writing JavaScript, you’ll end up with code like this: javascript Read line numbers: OFF Line-number reading help Reading line numbers aloud This button is for screen reader users. ...