Elytron

DevOps

Usually, QA gets the build once it is deployed in a designated environment and follows the test execution (function and regression testing) process. When the build has been verified by QA, it then goes into the production. This process usually takes a couple of days in the QA environment, but this is not the case in DevOps.

DevOps is an extension of agile software development approach that enables software development and testing to happen simultaneously with continuous collaboration between all stakeholders. Enterprises today are witnessing a rapid adoption of DevOps to accelerate time to market and to better respond to, and meet the ever-changing customer needs. DevOps has emerged from the necessity of businesses to respond more quickly to market changes to attain competitive advantage and rapid business growth.

When implementing DevOps, many leading organizations are leveraging new practices and automation to increase both speed and quality. Even when organizations don't start DevOps with an eye toward improved automated testing, they quickly learn through QA and integration bottlenecks that this is step one toward achieving continuous delivery of code.

DevOps

QA Responsibilities in DevOps:

  • QA should aim to detect a bug at the earliest point in the cycle and also prevent potential bugs from reappearing in the production environment.
  • QA should make sure that all environments required for testing should be standardized and deployments automated. There is no room for manual testing.
  • QA should not limit their role to only finding and preventing defects, but should also highlight problems in the processes and recommend changes wherever necessary. This practice is only possible if QA takes ownership of the improvement process in DevOps.
  • Being a quality advocate, QA has influence on both development and operations. They should not just only find defects but also notice any opportunity to improve the quality of the product. In this way, quality will be checked at every stage.