Mathieu Bastian explores the mechanics of unit, integration, data and performance testing for large, complex data workflows, along with the tools for Hadoop, Pig and Spark.
Pawel Sawicz suggests putting tests to the test by mutating the code to see if the codebase is properly covered by tests and how errors are propagated.
Tammer Saleh talks about the mistakes made building microservices, when microservices are appropriate, where to draw the lines between services, performance issues, testing, debugging, failure, etc.
Rachel Reese talks about Jet.com's chaos testing methods and code in depth, but also lays out a path to implementation that everyone can use.
Russ Miles shows how we can build production-level confidence in our polyglot microservices by applying the test-driven approach to synchronous (REST) and asynchronous (Messaging) services.
Ken Kousen talks about Geb, which makes it easy to automate browser-based applications. Geb is based on the Spock testing framework, providing a straightforward syntax and easy execution model.
Iván López discusses the basics of Spock and how easily one can test a Java application. Spock is a Groovy-based testing and specification framework for Java and Groovy applications.
Brannen and Fränkel cover the latest testing features in Core Spring, Spring Boot, and Spring Security, and tips on integration testing with TestNG, DB transactions, SQL script execution, etc.
Katrina Clokie discusses how BNZ does web (SOAP, REST) services testing, the tools and practices employed and some of the resources and exercises their testers use to learn how to test.
Brian Westrich shows 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.
Allison Figus performs live demos of Geb tests driven by Spock. She takes a look at code and behind the code to understand what it means and why Geb is a great way to do functional automated testing.
John Hughes presents automated techniques that can improve testing, focusing on what the code should do rather than which cases should be tested, with war stories from Ericsson, Volvo Cars, and Basho.