Where QA/Automation /Manual Test Engineer Fits in Software Industry.
Who is Developer
Developer is the person who is responsible for Development of the software (writes the code, does the unit test etc.) whereas Operations are responsible primarily for activities like code / release deployment during Go-Live, seamless deployment and much more.
So, the question is, what is the role of a Quality Analyst (Especially Manual tester) in DevOps. Is the role redundant now?
Any software (or a piece of code) that needs to go live has to go through an efficient testing for its success, which is a continuing process. Software Development Life Cycle (SDLC) is incomplete without thorough testing which needs an efficient Quality Analyst.
DevOps is based on Continuous Integration and Delivery (CI / CD). CI/CD is a concept that enables effective merge of newly developed features into the main code base. It fulfills the integration aspect by running different tests at each sprint stage and provides delivery aspect by deploying the committed code into the software available for the end-user.1
CI/CD is the cumulative responsibility of Developers, QE’s, Product Owners, Business Analyst and Release Managers so as to contribute towards successful delivery of product in a timely manner.
The change required in Quality Analysts while working in DevOps world
Popular belief is that Quality Analysts need not understand the technical perspective of a product as it is expected from a developer or a designer. A Quality Analyst just needs to break the system and find defects.
Some part of the above statement stands true, where the job of a Quality Analyst is to find defects. This job can be done more efficiently when the Quality Analyst is involved in SDLC process right from the design stage through the development of the product.
Listed below are some key takeaways which need to be considered while implementing Quality Analysis in DevOps world:
1. Team Formation: Quality Analysts should have control during the product development and Delivery cycle so as to ensure the product quality.
2. Communicator/ Early Defect Detection: If a Quality Analyst is involved from the design stage then it can be ensured that the team is not deviating from the requirement and defects are detected that may rise due to miscommunication.
3. CT (Continuous Testing): When the Quality Analyst is involved with the Developer right from the start, the team can implement continuous testing and point out defects from an early stage. The Quality Analyst need not wait for a test window as efficient delivery of a quality product should be the aim of the team.
4. Collaboration with Operations: The Quality Analyst needs to collaboratively work with the Operations team. This ensures that the Product is in line with the requirement that was logged by the product owner, fit for cause and qualifies for deployment.
5. Automation: Regression defects are equally important in functional defects, hence having an automation suite is an important aspect. Once a functionality is developed, Delivery/Quality Analyst should look into automating that test. This ensures that the next release focus can be on delivered functionality and Regression suite can enable the detection of Regression defects.
With Automation in demand, what can a Manual Quality Analyst / Quality Engineer offer in DevOps?
“The Only Thing That is Constant is Change”
Quality Analysis experts must rethink and change their traditional mindset.
Some of the effective transitions proposed based upon success stories @ Expleo:
1. Quality Analyst as part of Operations: We have developed our Quality Analysis consultants on competencies related to Operations role which has benefited our clients significantly. Operations is a role in which any Quality Analyst can make an easy shift.
2. Quality Analyst as a Consultant: Quality Analyst has an eye for defects and knows when something is not right. If this is well complimented by business / domain knowledge, then such consultant can easily identify loopholes in the requirements. This would help the business to refine requirements to the desired level resulting in a better software / product. This also enables them to roll out a Quality Analysis driven approach, having more emphasis on replicating the user experience into the real world resulting in minimal UAT / BAT defects.
There are many such roles that one can think of for a Quality Analyst in DevOps world. All we need to do is embrace the change, rethink and take the next step forward.
Source: https://www.thegatewaydigital.com/devops-model-the-role-of-quality-assurance-redefined/
