DevOps is intended to allow a culture where development and operations come together to develop, test and deploy applications in order to reduce overall deployment time. As the DevOps movement gathers pace, some might conclude that it makes Quality Assurance obsolete.
What Does Devops Do With QA?
While waterfall development was a natural home for QA, where it matches into DevOps and agile is not as clear. Most of the people lump it into themes like continuous integration, continuous development, and continuous delivery, but there’s another way to look at it.
Enter test automation. In a world of regularly or weekend regression runs, the volume of software app testing company has improved substantially.
And with this improved volume of testing comes the requirement for test automation. DevOps can simply not succeed if it still needs a large number of test cases to be run manually.
The Shared Courtyard Of Testing Automation
With DevOps, everybody is getting worried about quality. In theory, that’s great news. But, there’s a great Chinese proverb which changes to “The shared courtyard never gets swept”. If something is everybody’s issue, then it’s actually no one’s problem. And therein lies the danger.
Test automation is not something that magically appears on its own, as any experienced agile developer or tester will tell you.
The hard work in test automation comes at the start, in developing out the test cases. Of course, you can work with outside specialists to handle and complete setup. But still, whose responsibility is it internally?
No comments:
Post a Comment