Published 📅: ....
Last modified 📝: ....
Share this post on BlueskySee discussion on Bluesky
The other day I noticed this really succinct and to the point tweet about snapshot tests from Mark Dalgleish:
Just deleted all component snapshot tests from our React component library—in favour of screenshot tests.
We were snapshotting component markup in isolation, outside of a browser, without styles. We weren't testing the output. We were testing implementation details. — Mark Dalgleish (@markdalgleish) February 25, 2019
The valuable insight here being the following:
We were snapshotting component markup in isolation, outside of a browser, without styles. We weren't testing the output. We were testing implementation details.
When I started working with Jest and snapshot testing I thought it was one of the coolest things ever. It felt like I was adding meaningful code coverage to my code, when in reality I was only testing the implementation details of it.
Over time I started to realize that the tests I was adding were only adding more friction to the work I was doing. Since then I have been slowly removing snapshot tests from my code whenever I make a change that causes the snapshot tests to fail.
Loading...
Published: ....
Are we reinventing the wheel when it comes to onboarding new AI agents to a codebase, when we already have primitives available for onboarding humans?
Published: ....
Have you ever found the need to change the image you render on a web page based on the current preferred color scheme of your theme?
Published: ....
Have you ever wanted to create a class in JavaScript or TypeScript but also have the initialization be async? Here's a quick tip on a pattern that I've used in the past!
Published: ....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!