Daniel Wagner-Hall set up and maintains the continuous integration server for the Selenium project; every check in runs several hundred tests in 30+ browser/version/OS combinations, totaling 3.5 days of tests every day!

This presentation discusses problems and solutions that were made in solving problems such as size (about 100 people in total, more than 5 years long), multi-location (Vilnius, China, US), remote PO (teams in Eastern Europe, PO in US), ~550 000 LOC’s, multiple customers. It will present techniques used to maintain the project quality in shape: Continuous Integration, Code Review, Static Code Quality.

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.

Martin Flower defines legacy code as code without tests. You test your server-side code, but if you are working on a site with a fair amount of non-trivial JavaScript (ajax call, extensive callbacks, etc.) you really should be testing your JavaScript as well. All the untested JavaScript code we are writing today is, in effect, legacy code, but we can address this with JavaScript unit testing!

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 …

This website presents a list of open source and commercial continuous integration tools.
http://www.continuousintegrationtools.com/

San Francisco, Calif., JavaOne and Oracle Develop 2010 – September 21, 2010 Electric Cloud®, the leading provider of software production management (SPM) solutions, released ElectricCommander Workgroup Edition at JavaOne and Oracle Develop 2010, providing smaller teams and workgroups with the enterprise-class features and flexibility of ElectricCommander. ElectricCommander Workgroup Edition (ECWE) allows smaller organizations to automate and manage their software build-test-deploy processes, freeing developers from maintaining homegrown, script-based systems, or adjusting their processes to fit …

Software engineering met Continuous Integration (CI) years ago. Tools like Hudson, Bamboo, Collabnet TeamForge, and Cruise Control automate the build and deploy cycle. Now, PushToTest drives an innovative way to achieve Continuous Testing (CT) in your organization.