Generally, a project with the following characteristics is called suitable for automation.
1) The task test is clear and will not change frequently
2) The daily post-build test verification
3) The more frequent regression testing
4) The software system interface is stable and less changes
5) The same test case needs to be run on the platform, combined traversal type
6) The maintenance cycle of the software is long 7
) The progress of the project is not under pressure
8) The development of the system under test is relatively standardized, which can ensure the testability of the system
9) There are a large number of automated test platforms
10) Testing Personnel with strong programming skills
Of course, it is not necessary to meet the above 10 conditions to carry out automated testing work. Generally, if the following three points are satisfied, automated testing can be carried out on the project.
1. Infrequent changes in software requirements
The size and frequency of changes in automated test scripts determine the cost of test script maintenance. If the software requirements change too frequently, the testers need to continuously update the automated test cases according to the changing requirements to adapt to the new functions. The maintenance of the script itself is a process of developing the code, which needs to be extended, modified, debugged, and the structure needs to be adjusted if it is suitable. If the maintenance cost is higher than the test cost it saves, then automated testing loses its value and meaning.
The appropriate method is to first automate the testing of relatively stable modules and functions in the system, and manually test the parts with large changes.
2. The project cycle is long.
Due to the determination of automated testing requirements, the design of the automation framework, and the development and debugging of scripts all take time to complete, and this process itself is a software development process. If the project cycle is short, there is not enough time. Time to support such a process, then automation will definitely not work.
3. The automated test script can be reused. The
reuse should be considered from these three aspects:
1. Whether there is a big difference between the tested projects (such as C/S architecture and B/S architecture)
2. The selected test Whether the technology and tools can adapt to this difference
3. Whether the tester has the ability to design and develop an automated testing framework that applies to the difference