Marcus Martina explains in this blog post how to integrate FitNesse tests into the Jenkins continuous integration system. FitNesse is an open source testing framework that aims to implement integration testing in a collaborative way. It is easy to integrate FitNesse tests automatically with Maven and Jenkins. The post provides the code necessary to do this integration. It also identifies the different Maven plugins that are necessary to achieve this goal and recommends to trigger the execution of the integration tests in an individual build step.
In this blog post, Mark Prichard presents a solution on how to use Jenkins to give a “QA dashboard” view of a native Android application build. His goals were to show metrics for the results of unit test and code coverage in an Android build context on the Jenkins continuous integration system.
This article discusses how test automation can help achieving continuous delivery. It suggests to start small with a good investment on a robust automation suite, to give it your best people and to cultivate habits in your team that respect tests. Test automation reduces cycle times and also improves the cost of each deployment.This is achieved by earlier feedback to developer through automated tests improves the quality of builds that the testers work on, provided they pick up green builds. There is also a direct reduction in testing cost, as fewer people are needed to run the tests.
This website presents a list of open source and commercial continuous integration tools. http://www.continuousintegrationtools.com/