Front-end Testing is Tough!
Eddie and I have spent a lot of time thinking about how to write front-end tests.
Sure, we learned how to write them almost immediately when we started our first developer jobs, but we didn't know how to write them correctly.
It's painful trying to learn front-end testing on your own. It's incredible easy to write bad front-end tests.
So we're always on the lookout for testing gurus to interview to teach us how to do things the right way. We've talked to a few guests about testing JavaScript before, but we never discussed front-end testing explicitly. ...Until now!
Enter Tomasz
Tomasz is a senior front-end engineer that knows a thing or two about writing front-end tests. We get into Jest, Cypress, and React-testing-library, as well as the right attitudes and strategies to bring into your testing practices.
Tomasz also likes jQuery, so we talk about that too.
Show Notes:
- 1:01 - Intro
-
3:36 - What tools do you use to test React?
- 5:40 - Test Coverage
- 9:55 - Mocking with Jest
- 11:15 - How Jest renders the component tree
- 13:40 - React-testing-library and Accessibility
- 14:10 - E2E Tests and Cypress
- 16:42 - What types of things would you test with Cypress?
- 19:08 - "Smoke Tests"
- 20:48 - Cross-browser testing
- 24:39 - Why you have to trust your tests
- 25:31 - Preventing deploys when tests fail
- 27:46 - Peace of mind from testing
- 30:11 - How to ensure your E2E tests aren't brittle
- 34:16 - How do you handle API calls in Cypress?
-
35:54 - Integration tests
- Write tests. Not too many. Mostly integration. by Kent C Dodds - Article
- 40:18 - Advice for people that are brand-new to testing
- 44:11 - Test Driven Development
- 46:10 - Who owns the code? Pushing for tests on your team
-
47:12 - React VR
- 51:59 - jQuery??
-
55:26 - Plugs! Follow Tomasz on:
-
56:23 - Nerd Minute!
- Super Mario Speedruns
- Webpack configs suck
- Outer Worlds
- Doom Patrol
- Joker