The book starts by a very generic discussion about testing and continues by defining Integration Testing in comparison to Unit Testing. The next chapter compares the respective merits of #JUnit and #TestNG . It is followed by complete description on how to make a design testable: what works for Unit Testing works also for Integration Testing. Testing in software relies on automation, so that specific usage of the #Maven build tool is described in regard to Integration Testing – as well as #Gradle . Dependencies on external resources make integration tests more fragile so faking those make them more robust. Those resources include: databases, the file system, #SOAP and #REST web services, etc. The most important dependency in any application is the container. The last chapters are dedicated to the Spring framework, including #Spring MVC and #JavaEE .
In this journey, I also dared ask of Spring fame and team lead of the #Arquillian project to write a foreword to the book – and I’ve been delighted to have them both answer positively. Thank you guys!
I’ve also talked on the subject at some JUG and European conferences: JavaDay Kiev, Joker, Agile Tour London, and JUG Lyon and will again at JavaLand, DevIt, TopConf Romania and GeeCon. I hope that by doing so, Integration Testing will be used more effectively on projects and with bigger ROI.
Should you want to go further, the book is available in multiple formats:
- A paperback version on #Amazon for $49.99 (http://www.amazon.com/Integration-Testing-Trenches-Nicolas-Frankel/dp/2955021431/)
- Electronic versions for Mac, Kindle and plain old PDF on #Leanpub (https://leanpub.com/integrationtest). The pricing here is more open, starting from $21.10 with a suggested price of $31.65. Note you can get it in all formats to read on all your devices.
If you’re already a reader and you like it, please feel free to recommend it. If you don’t, I welcome your feedback in the comments section. Of course, if neither – I encourage you to get a book and see for yourself!