Abstract: The Java ecosystem has myriads of libraries and projects that can be used to create the features our customers require, there's no shortage of options everywhere you look when it comes to writing production code. But what about the testing code? If you ascribe to the Clean Code ideals then you know that testing code is as important as production code. Luckily there are a good number of libraries that can be used with popular testing frameworks. In this session we'll discover how to write better-parameterized tests; take care of concurrency-related events; spy/mock/stub out collaborators to ensure the cleaner and isolated tests; fake out REST APIs to test out client code; fake out REST clients to test out server code, and more.
Andres Almiray (JSR377 Spec lead, Groovy aficionado, Griffon project lead, Java Champion, JavaOne Rockstar, JCP EC)
Andres is a Java/Groovy developer and a Java Champion with more than 19 years of experience in software design and development. He has been involved in web and desktop application development since the early days of Java. Andres is a true believer in open source and has participated in popular projects like Groovy, Griffon, and DbUnit, as well as starting his own projects (Json-lib, EZMorph, GraphicsBuilder, JideBuilder). Founding member of the Griffon framework and Hackergarten community event.
JUG Leader, JUGBD