Show Description

The whole point of testing in development is so you don't write some new code that ends up affecting other code, causing it to fail or otherwise do something unexpected. You write some code, then you write a test to ensure the code you write does what you expect it to (you might even write the test first!). It should pass right when you create the test, which can make it seem like a weird waste of time. But there the test will set, ready in waiting to catch any new code that interferes.

Chris, Tim, and Alex talk about the testing we do on CodePen. Mostly "unit tests", as described above. Some in Ruby-land, some in JavaScript-land. Our recent foray into React (and friends) has made our JavaScript testing game much stronger. We used to do some integration testing too, and we'll talk about how that was problematic for us.

Show Links