The State of Testing survey investigates how the testing profession develops. The State of Testing 2020 report has been published. As a blog collaborator for this survey, I highly recommend reading it!
2020 State of Testing™ is now live – and there are so many new insights!
PractiTest and TeaTimeWithTesters are happy to present the 7th edition of the annual State of Testing™ report. The State of Testing™ is not just about numbers, it also reveals trends that are starting to point out concrete changes that are relevant to everyone in the QA world.
I did an interview with the organizers of the State of Testing survey for InfoQ which explores how trends have developed in the testing profession and provide visibility into different angles of testing and technical aspects of testing.
One of the questions that I asked was about how the adoption of continuous integration and continuous deployment impact testing:
Bhamare: The way I look at it, it warrants testers (or anybody who tests in the team) to have reliable and optimum automation in testing in place so that the time saved can be used more for finding risks not known yet. And they can find those risks as early in SDLC as possible.
I feel it makes testers critically think about the automation strategy they can have that best suits their context and make it reliable and meaningful. The flip side of it that I see sometimes is that if their automation strategy is not smart enough (or say if their CI/CD infrastructure is lame) testers end up just writing more automation and spending enormous time in just maintaining it for the sake of keeping the pipeline green. These efforts hardly contribute to the user-facing quality of the product and add no meaningful value.
Montvelisky: In my mind they are helping us to be part of the larger Quality Assurance process. The most immediate factor is the inclusion of Unit Tests and the Product Integration activities as part of the testing and quality process – getting testers to be part of the definition and analysis of these activities, something that up to now had been out of reach to our teams.
In the longer run, and specially within organizations working with Continuous Deployment, it means the inclusion of the Testing Team as part of the DevOps group, as we also have eyes, ears, arms and legs in the deployment and monitoring operations of Production Environments.
Read the full interview on InfoQ: 2020 State of Testing Report.