One of the main trends in software development is to deliver software more quickly. DevOps, continuous delivery or continuous integration are some of the approaches that have been promoted recently to achieve this goal. In their article “DevOps Advantages for Testing”, Gene Gotimer and Thomas Stiehm discusses the advantages that these approaches could provide to software testing and software quality.
As DevOps is now a new important approach for rapid software delivery, how do you perform software testing in this context of reduced cycle times. In his article, Gopinath C H explains how to perform testing in continuous integration and continuous deployment workflows, providing examples based on the Visual Studio 2015 and Team Foundation Server tools.
With Selenium and Jenkins, you can extend Selenium processes to include screenshot comparisons, enabling automatic UX compliance at the speed of your Continuous Integration workflow. Learn how to compare screenshots from one Jenkins run to a repository of known quality, in order to insure that not only does your website work well, it also looks well.
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.