Testing Your Build Logic
All code should be tested, and your build logic is no different. Gradle's declarative-where-possible & imperative-where-necessary approach makes it possible for you to easily solve your own problems by plugging in your own logic, and this logic should be tested. What does it mean to test build logic? How do you go about it? If you've ever had these questions, this session is for you.
We'll look at how to structure your build logic for improved testability, APIs for implementing your tests and options for how to organise your build logic code and tests for execution.
We'll also look at what's in the Gradle pipeline for making the lives of build logic developers easier with regard to testing and the development process in general.
About Luke Daley
Luke works @ Gradle Inc. building Gradle Enterprise. He's also an open source tragic and is the creator of Ratpack https://ratpack.io. When not hitting the keyboard, he's likely drinking IPA or playing guitar.
More About Luke »
About Peter Niederwieser
Peter Niederwieser is a computer language enthusiast from Austria who has been using Java since the early days. Peter's work experience ranges from small start-ups to large enterprises like Siemens. His passion for software quality and continuous delivery invariably leads him to take the build master role on new projects, pushing project automation as far as he can. It also lead him to create Spock, an innovation-packed developer testing framework that is seeing increasing adoption around the globe.
Peter is an active member of the Groovy community, and can't sleep without his daily dose of Scala. When Peter isn't coding, you can find him speaking at conferences around the world, or pondering over a chess board.
More About Peter »