This article is for anyone who wants to better understand project quality assurance processes. Check out 7 different testing approaches and their benefits.
Join the DZone community and get the full member experience. Originally published on August 17, 2020 This article will be interesting for IT directors, product managers, project managers, and anyone who wants to understand the processes of project quality assurance better. At Qualitica, we test large web and mobile projects, both commercial and national ones. Before a separate testing agency has been established, I spent 10 years as a specialist and head of several digital studios. Usually, in any IT project (websites, applications, games, corporate software), you start by treating testing as a formal procedure. However, normally the testing also evolves with the project: the more people are involved, the more complex is the process. There are 7 testing evolution stages that may differ in different companies: Let’s learn about each stage in more detail. It’s the simplest, « instinctive » approach to testing. It is common in small companies. When it is impossible or presumably unwanted to hire a professional tester, this part of the work is performed in-house. However, this is an inappropriate and problematic approach for the following reasons: An extreme case is when no testing is done in the company and the error report goes from the client. Then more and more errors/bugs appear. Thus, clients become testers at their expense. Checking the entire project at the pre-release is a classic method when working with the Waterfall model. The project is divided into global stages (sometimes the entire project is single-stage). At each stage, the software is made and then tested in place, which is good. But there are also specific problems: Thus, this approach is logical but takes into account no global errors. Therefore, testing evolves further. Then the company understands that it is better to detect errors as they accumulate. Therefore, we switch from the Waterfall model to the Agile method. At this point, testers are deeply integrated into the development. All tasks are tested repeatedly and sequentially: separately, as part of the release, in the field.
