I am incredibly lucky to work with a very talented team of developers that have a passion for adopting Software Development best practices.
One of the practices we have adopted is Test Driven Development (TDD). This means that our developers have quite an extensive suite of tests that test various layers and functionality of the product we work on at AdInsight
With the development team writing a lot of tests there soon becomes the need to facilitate the automation of those tests.
The automation should have a few goals:
Continuously build application upon new source control changes
The next posts in this series will go through achieving most of those stages in the above cycle. They will outline how those stages can be achieved using Java and in particular a Spring based web application using the Maven build process.
The posts will assume that the reader is comfortable with Java, Maven and the Spring framework and for that reason wont go into too much detail on the code involved. They serve to provide an example of how you might architect an application for a transition to CI