Building great software requires a thorough understanding of the real needs of our customer. Techniques such as ATDD, BDD and Specification by Example help us understand the requirements by describing how the software has to behave in a language understood by all stakeholders. These specifications are made executable; creating automated acceptance tests. This suite of executable specifications forms the living documentation of the software system as it is guaranteed to be up to date.
There are several tools available that can help you with this. Well known examples are: Cucumber, JBehave, Spock, REST-Assured... Finding out how to apply those tools is essential to success. In this Hands-on lab you'll learn how to complete your test automation stack from unit level to executable specifications.
After a brief introduction of the available tools, you will make specifications executable with a selection of these tools. This will give you the opportunity to compare them, check out their strengths and weaknesses, see what they have in common and most of all: see how they can help you to create better software, and can form the missing piece in the automation puzzle.