Artem Zakharchenko
Software engineer. Helping you master automated testing at http://EpicWeb.dev. Author mswjs.io. Instructor egghead.io.
I tell stories @zakarcher.com.
My debut book "LOGGERHEADS" it out 👇
zakarcher.com/books/loggerheads
- Okay, so I looked into the comments on the MSW usage in the latest State of JS, and the negative ones are either misunderstanding what mocking is or blatantly promoting what feels like their own tools. This made me happy. I don't consider any of that a relevant feedback.
- I know there are a ton of people who think "mocks = bad". Not only is that a huge misconception, but if you truly abide by it, you will produce terrible tests. Mocking is a tool. Is a brush bad? Depends on who's holding it, I suppose. The same applies to mocking.
- You simply cannot test certain functionality in an isolated manner without tools that establish that isolation. Mocking is one of those tools, and it's the primary ones when it comes to dealing with the network requests. Here are a few more words on it: www.epicweb.dev/what-is-a-t...
- Stating that "mocks are never the answer" or "needing mocks is a sign of a bad architecture" is simply false. I guarantee you people who think this way are the same people who don't like writing tests and never wish to see their test suite again. And it's not a coincidence.
- I like reading sentiments like this because they remind me that I have a lot of work to do to educate people and help them figure out automated testing. That's what I've been doing for the past eight years. That's what I'll keep doing for the years to come.
- 📦 MSW v2.12.8 fixes two issues that resulted in a memory leak in Node.js. Please update your projects! Release notes: github.com/mswjs/msw/r...
- I will never be not amazed at how a seemingly trivial bugfix can suck you into a rabbit hole of issues that spans three dependencies deep. That was a fun quest!
- Enjoyed talking about authentication in end-to-end tests in a recording today! The thing is, the way you approach authentication as a feature and as a prerequisite to test other features has one important difference. Overall, this is already my most detailed workshop to date ❤️
- 100M a week. Sheesh.
- Can I pick your brain, folks? Reply with 3 topics you consider advanced in automated testing 👇
- I genuinely don't know how npm cli and website aren't considered abandonware at this point. Trusted Publishing is broken, features behaving inconsistently across them, token management is non-existent, obscure error messages... 😔
- Thank you, Santosh! ❤️
- Can someone tell me what am I doing wrong? The whole point of trusted publishing is so I DON'T have to log in to npm to publish a package from a trusted workflow. So no tokens are involved.
- The full failed job here: github.com/mswjs/sourc...
