Using Groovy & Spock to Develop Tests as Assets Not Afterthoughts

October 2, 2015
Recorded at SpringOne2GX 2015 Presenter: Brian Westrich Groovy Ecosystem Talk This talk is based on my experiences writing unit tests in a large code base with a team of accomplished test-driven developers. I'll share how we wrote tests that became an essential asset of the code base, not just an afterthought. These tests not only verified our code, they also improved our design, helped us learn how the existing code base worked, and helped new developers come on board. The tests were easy to find and run, and didn't break when we refactored unrelated functionality or changed implementation internals. In short, these were tests that developers WANTED to write. I'll also show examples of testing anti-patterns, including redundant testing, white box testing, and using the wrong type of test double. All examples are in Groovy and Spock. Example source code and a Test Driven Development crib sheet will also be provided to help you and your teammates write tests that are truly assets of your project.
Previous
Ratpack Web Framework
Ratpack Web Framework

Recorded at SpringOne2GX 2015 Presenter: Dan Woods Groovy Ecosystem Track Ratpack is a high-through, react...

Next Presentation
Spring Integration Java DSL
Spring Integration Java DSL

Recorded at SpringOne2GX 2015 Presenter: Artem Bilan Data & Integration Spring Integration Java DSL is an ...