Traditional Culture Encyclopedia - Traditional customs - What is the difference between agile testing and traditional testing, and outline the process of agile testing.

What is the difference between agile testing and traditional testing, and outline the process of agile testing.

The differences between agile testing and traditional testing are as follows:

The 1. project is equivalent to parallel development and testing, and the overall project time is relatively fast. The module is submitted quickly, and there is a sense of oppression when testing. Clear division of tasks and high efficiency. Project planning should be reasonable, otherwise there will be duplication in the testing process, which will increase the workload. When you find a problem, you need to follow it closely. People in the project are very busy, and problems are easily forgotten.

2. Problems that are time-consuming or difficult to solve and have little impact on the project will generally be left to the next stage. Bugs found can be solved quickly, which has little impact on the testing of related modules. Frequent version changes will affect the speed of testing. Communicate with developers more. Pay attention to the update of the version. Testers will attend almost all meetings of the whole project team.

The process of agile testing is:

Agile testing should be a new testing process, method and practice that adapts to agile methods. It is tailor-made for the traditional testing process, with different emphases, such as reducing the proportion of test plan and test case design, and increasing communication and cooperation with product designers and developers.

In the process of agile testing, we participate in unit testing, pay attention to the new functions that are constantly iterative, and fully accept and test these new functions, while the regression test of the original functions depends on automatic testing. Due to the short iteration period in agile methods, testers should start testing as soon as possible, including timely evaluation of requirements, development and design, and more importantly, timely and continuous feedback of product quality.