FrontKon#26High‑End Content. Community Soul.
Artem is a developer, speaker, and renowned open source software author. For the past decade, he has been promoting best practices in testing within the JavaScript ecosystem through his open source projects, such as Mock Service Worker, an API mocking tool that helps development teams build more reliable applications. He has helped teams at Google, Microsoft, Amazon, Spotify, Netflix, and countless other companies deliver better software.
He contributes to community education through articles, workshops, and talks, where he shares practical experience from building modern web applications.
Beyond technology, he is passionate about the intersection of development, design, and user experience. Before starting his career in software engineering, he worked in graphic design, considers himself a true typography enthusiast, and is more dependent on coffee than he is willing to admit.
Workshop
Your component tests are broken, but you aren't to blame. It's your test environment. For years, you've been taught to use things like JSDOM/HappyDOM to test your components and the people who taught you that knew those environments were broken, there just wasn't anything better. Until now.
You've heard about Service Workers but you've never tried writing one. It has its own APIs and restrictions, you need to "register" it, there's some life cycle events... It's confusing, I get it. But it doesn't have to be.