What kind of project is suitable for automated testing
Although, when you got this book, you have already done some analysis and consideration of the project to be tested, but it is still necessary for the author to do it here.
Not all projects are suitable for the implementation of automated testing, so that readers will not find difficulties in the process of implementing automation of the project.
It took a lot of manpower and time without getting the benefits it deserved.
1. The task test is clear and will not change frequently
2. Test verification after daily build
3. Frequent regression testing
4. The software system interface is stable and less changes
5. The same test cases that need to be run on multiple platforms, combined traversal tests, a large number of repetitive tasks
6. Long software maintenance cycle
7. The project schedule pressure is not too great
8. The development of the software 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 skills
Of course, not all of the above 10 have the conditions to carry out the test work. This requires the reader to make a comprehensive trade-off. at me
In our general experience, automated testing can be carried out on a project as long as three conditions are met:
Infrequent programming of software requirements
The stability of test scripts determines the maintenance cost of automated tests. If software requirements change too frequently, testers need to root
Update test cases and related test scripts according to changing requirements, and script maintenance itself is a process of code development, which requires
To modify, debug, and if necessary, modify the framework of automated testing, if the cost is not less than the test saved by using it
cost, the automated test will fail.
Some modules in the project are relatively stable, while some module requirements are highly variable. We can automatically automate the relatively stable modules
However, manual testing is still used for larger changes.
Long project cycle
Due to the determination of automated testing requirements, the design of automated testing frameworks, and the writing and debugging of test scripts, it takes a considerable amount of time.
time to complete. Such a process itself is a test software development process, which takes a long time to complete. If the cycle of the project
Relatively short, there is not enough time to support such a process, then automated testing becomes a joke.
Automated test scripts are reusable
The reuse of automated test scripts should be considered from three aspects.
differences between C/S systems and B/S systems); whether the selected test tool accommodates this difference; and finally, whether the testers have the ability to develop suitable
An automated testing framework that should respond to this difference.