Shulou(Shulou.com)06/03 Report--

Generally speaking, projects with the following characteristics are called suitable for automation.

1) Task testing is clear and will not change frequently

2) Test verification after daily construction

3) more frequent regression tests

4) the interface of the software system is stable with little change.

5) you need to run the same test cases, combined ergodic tests, and a large number of repeated test tasks on the platform.

6) long maintenance cycle of the software

7) there is little pressure on the progress of the project

8) the development of the system under test is relatively standardized, which can ensure the testability of the system.

9) have a large number of automated test platforms

10) testers have strong programming ability

Of course, it is not necessary to meet the above 10 situations in order to carry out automated testing. Generally speaking, automated testing of the project can be carried out if the following three points are met.

1. Software requirements do not change frequently

The size and frequency of changes in automated test scripts determine the cost of test script maintenance. If software requirements change too frequently, testers need to constantly update automated test cases according to changing requirements in order to adapt to new functions. The maintenance of the script itself is a process of developing code, which requires extension, modification, debugging, and, where appropriate, adjustments to the architecture. If the maintenance cost is higher than the test cost saved, then automated testing loses its value and meaning.

The appropriate way is to automatically test the relatively stable modules and functions in the system, and test the parts with great changes by hand.

two。 The project cycle is long.

Due to the determination of automation testing requirements, the design of automation framework, the development and debugging of scripts all take time to complete, and this process itself is a process of software development, if the project cycle is short, if there is not enough time to support such a process, then automation must not work.

3. Automated test scripts can be reused

Reuse should be considered from these three aspects:

1. Whether there is a big difference between the projects tested (for example, the Cpicurus S architecture and the Bripple S architecture)

Second, whether the selected testing techniques and tools can adapt to this difference.

Third, whether the testers have the ability to design and develop an automated testing framework suitable for differences.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.