What Is CT and How Do Traditional Test Teams Fit In?
Continuous testing grows from Continuous Integration, and the success of continuous testing is in its ability to get everyone involved and not just the test team.
Join the DZone community and get the full member experience.Join For Free
It wasn’t long ago that the Dev and test teams would work late hours, focused and rushed to meet a deadline: rapid fixing, reprioritizing and deferring bugs to close out the bug list, move everything to the staging server, do one last run of the regression and pass it over to Ops and IT to move to production. What happened after? No one knew. For most Dev and test team members, Ops is a black box. More often than not, they are oblivious to what happens at Ops, the roles, responsibilities, and timelines. One day — long after the drop-dead deadline for Dev and test teams — after delays, questions, and changes, the product went live.
Does this scenario sound familiar? Well, DevOps is supposed to be a game changer.
DevOps means many things to many people. But for test teams, continuous testing (CT) is the primary task in DevOps. Additionally, CT is not merely rerunning the same set of “full regression” tests over and over as products get delivered and deployed. This is actually a recipe for disaster and not the intent of continuous testing.
Recently, test teams were challenged to ramp up their practices by moving to agile and scrum. DevOps will propel the teams to now ramp their practices up even more—more automation, more technical testing and more tools to leverage. If your test team already has mature agile practices, with continuous testing, they can mature further to eventually accelerate the product release.
Continuous testing grows from Continuous Integration (CI), and the success of CT is in its ability to get everyone involved and not just the test team.
Continuous testing is a Lean process of quality at every step. It includes quality user stories, quality environments, quality unit tests and quality performance tests. It is “testing at every step” and not “QA” at the end. It is also shifting testing tasks from Ops at the end, by testing earlier and testing all along the way. CT is adding more tasks as well.
Everyone in the enterprise benefits by bringing Ops and IT and its processes into the dev process much earlier by shifting left and taking advantage of the advances in virtualization and infrastructure automation.
Read the full article to learn how to leverage Continuous Testing. This article was originally published on DevOps.com
Published at DZone with permission of Thanh Phan, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.