Stop finding bugs in production. TDD's 'test-first' approach forces you to write cleaner, more robust code from the start.
#1about 3 minutes
The problem with traditional development cycles
Traditional development, where tests are written after implementation, often leads to bugs slipping through QA and into production.
#2about 3 minutes
Understanding the Red-Green-Refactor TDD cycle
TDD inverts the traditional process by first writing a failing test (Red), then writing just enough code to make it pass (Green), and finally cleaning up the code (Refactor).
#3about 8 minutes
Demo: Writing the first failing test for a health endpoint
The demo begins by creating a test for a server health endpoint, which fails because the endpoint and server configuration do not exist yet.
#4about 9 minutes
Demo: Implementing an addition feature using TDD
A calculator's 'add' endpoint is built by writing a failing test, implementing minimal code to pass, and then refactoring the test with multiple cases to ensure correct logic.
#5about 5 minutes
Evaluating the pros and cons of adopting TDD
TDD leads to more testable solutions and cleaner architecture but requires discipline and team buy-in to overcome the initial temptation to write implementation code first.
Related jobs
Jobs that call for the skills explored in this talk.
WeAreDevelopers LIVE days are changing - get ready to take partStarting with this week's Web Dev Day edition of WeAreDevelopers LIVE Days, we changed the the way we run these online conferences. The main differences are:Shorter talks (half an hour tops)More interaction in Q&AA tips and tricks "Did you know" sect...
What Developers Really Need to Create Great Code DemosEvery developer on earth has, at some point, had another developer to thank for a breakthrough, a success, an aha moment they wouldn’t have had without coming across that blog post, that open-source contribution, that reply on socials or that humble ...
From learning to earning
Jobs that call for the skills explored in this talk.