A team that releases every commit needs to take software testing seriously. This talk explains what kinds of testing a team needs when working with Continuous Delivery. It will need to evolve new ways of testing. It will have new dynamics of testers working with developers. It will find new ways of of interacting with customers, stakeholders and product owners. And it will have completely new demands that require the testing mindset.
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.
Although it could appear like a counterintuitive concept, the idea of performing software testing in production has gained more and more visibility in a software development world that aims for rapid delivery of new features and where it could be more and more difficult to reproduce the full complexity of applications in a separate environment. In this article, Marc van ’t Veer discusses the concept of testing in production and why it should be performed.
What kind of software testing do we need to have in a continuous deployment pipeline? What does it take to push a commit all the way to deployment? Fully automated. Several times a day.
How do you perform software testing in a continuous deployment environment where you have more than 10 releases a day? How can you be confident that the code running in production is still reliable? In this blog post, Andy Hume explains the software quality process the Guardian uses for continuous deployment mode.