UI & UXConference40min
Component wrappers and other patterns for making your tests bulletproof.
This talk guides frontend developers in writing stable Vitest/Jest tests by addressing common mistakes and exploring effective patterns. It covers optimal component testing levels, integration meanings, and effective mocking, aiming to simplify test maintenance and enhance readability for valuable testing scenarios.
Łukasz Nowak
talkDetail.whenAndWhere
Friday, September 26, 10:30-11:10
Concert Hall
This talk is dedicated to all frontend developers willing to write Vitest/jest tests not being flaky or failing unexpectedly with any code change delivered. We go through several most common mistakes and dive a little bit deeper into battle tested patterns helping to write value providing and readable tests scenarios. We discuss things like what is the most optimal level testing for components, what integration really means for them as well as what should effectively be mocked. You’ll be surprised at how many mistakes you’ve been making so far, usually turning test maintenance into a never ending nightmare. And you’ll get even more surprised realising how straight forward it really can be.
Łukasz Nowak
Well, I’m a senior frontend developer with nearly 15 years of professional experience. I love React for its simplicity and high-quality frontend testing for confidence it gives. I love sharing my knowledge, which makes me very often a speaker during internal company meetups. After a few initial attempts I felt like I’d like to spread this activity outside too, that’s why I responded to your CoP.
I work for a tech hub of a financial giant of the British market - Hargreaves Lansdown. I’m less and less a developer as recently I focus more on frontend architecture, testing shift left or helping less experienced colleagues to level up their expertise. During an uncountable amount of interviews and inductions I received a lot of feedback that we’ve introduced quality patterns to our ecosystem. That made me think of sharing it, or maybe even challenging by other developers outside.
I work for a tech hub of a financial giant of the British market - Hargreaves Lansdown. I’m less and less a developer as recently I focus more on frontend architecture, testing shift left or helping less experienced colleagues to level up their expertise. During an uncountable amount of interviews and inductions I received a lot of feedback that we’ve introduced quality patterns to our ecosystem. That made me think of sharing it, or maybe even challenging by other developers outside.
talkDetail.shareFeedback
talkDetail.feedbackExpired
talkDetail.feedbackPeriodExpired
occupancy.title
occupancy.votingClosed
occupancy.votingWindowExpired
comments.speakerNotEnabledComments