In this episode, Bouwe and Rich discuss and give some guidelines on how to make testing more useful and (who knows!) more fun.
As a developer, writing tests is a necessity. It automates the confidence that our code (or our app) works now, and will keep on working. And if you use TDD, it can even guide you in structuring code well. However, despite these benefits, many developers consider testing to be a necessary evil, sometimes not even useful, and definitely not fun. So let's talk about how we can make testing more useful and even perhaps fun, by deciding WHAT and HOW to test.
Recources:
- Book: Kent Beck - TDD by Example
- Kent C. Dodds' https://kentcdodds.com/blog/testing-implementation-details blog post
---
Do you want to go live with us and discuss some hotness, or do you have any other questions? We are curious about it! Just shoot us a message on Twitter: @bouwe or @RichStoneIO
More good stuff about JavaScript, Ruby, Rails, test-driven development, Elm, React, career, developer content creation, developer marketing, and everything else in the tech industry from your hosts:
