Software automation testing is the development direction of software testing. however, if we pursue automated testing blindly, it may lead to the failure of software testing. This chapter introduces how to carry out software automation testing projects and the management methods of software automation testing.
Manual testing and automated testing are two testing methods discussed by many testers. Some people flock to automated testing, while others scoff at automated testing. Before making a decision on how to view automated testing, you must first have a clear concept of automated testing.
Before automating a project, consider the following five aspects, which need to be considered for successful automated testing, and can also be used to measure whether the current project has sufficient conditions for automated testing:
(1) Test automation is similar to software development process.
Recording / playback script development is impossible to meet the needs of all automated tests, therefore, testers must master the necessary development knowledge and coding skills.
(2) Test automation is a long process.
First of all, automated testing can't be expected to find a lot of Bug in a short period of time, and automated testing can only show its value after running it multiple times over a long period of time. Second, don't think that as long as you buy the automated test tools and record some scripts, you can rest easy to watch the automated tests achieve the desired results, and you need to consider the maintenance cost of the automated test scripts. as the functionality of the application under test increases and modifies, the maintenance workload of the test script increases dramatically.
(3) ensure resources for test automation, including personnel and skills.
It is best to have a special automated test engineer to ensure that the test automation continues continuously and smoothly. The automated test engineer should be responsible for the test automation of the project, design the test framework and script structure, solve the development problems of various test scripts, and ensure that automated tests are planned, designed and developed, and maintained in an orderly manner.
(4) Carry out automated testing step by step.
Don't imagine automated testing as big in the first place, which is often impossible. Start from an early age, familiarize yourself with the basic skills of tools and automated testing, and then integrate resources to implement some basic automated test cases. For example, automated test scripts for smoke test types. First, realize the automatic testing of those functional modules that are easy to implement and relatively stable, and then consider gradually expanding and replenishing other functional modules that are relatively difficult to achieve or relatively unstable.
(5) ensure the maturity of the testing process.
If the capability maturity of the testing process and project management process of software enterprises is relatively low, the success rate of automated testing is also relatively low. Before carrying out automated testing, look at all aspects of the management capabilities of the software company, for example, whether testing is conducted independently. Is there configuration management? What is the schedule control ability? If all aspects of capability maturity are poor, do not blindly introduce test automation.