Software Testing Process

What is Software Testing?

The internet defines Software Testing as the process of executing a program or application with the intent of identifying bugs. I like to define Testing as the process of validating that a piece of software meets its business and technical requirements. Testing is the primary avenue to check that the built product meets requirements adequately.

Whatever the methodology, you need to plan for adequate testing of your product. Testing Helps You Ensure That The End Product Works As Expected, And Helps Avoid Live Defects That Can Cause Financial, Reputational And Sometimes Regulatory Damage To Your Product/Organisation.

Who are the key parties involved?

Testing needs to be a way of life, and be part of every conversation and task that a project team performs.
Everyone involved in a project is a key party. Developers do DIT, Product owners review copy and do hands on testing, BAs are constantly reviewing requirements, Project managers and Scrum masters regularly review plans to re-align priorities and extract best value. In their own way, everyone is testing all the time. As they should.

To bring it all together, you have the Test Manager and Test Leads/Coordinators, Project Manager/Scrum Master, Project Sponsor/Product Owner, and Business Analyst overseeing the Test phases of a project — with the support of Development Leads, Testers, Architects, and other support teams (like the Environments team).

Read more: https://tudip.com/blog-post/software-testing-process/