First of all, what is suitable for automated testing?
Highly repetitive test cases, such as quick version update, basic function verification, regression test and so on.
Unavailable or extremely laborious, such as 10000 registration, click, etc.
Methodology of automated testing
1. Test automation is similar to software development.
The development mode of recording/playback script can't meet all the requirements of automatic testing, and testers need to master the necessary development knowledge and coding knowledge.
2. Test automation is a long-term process.
First of all, we can't expect automated testing to find many bugs in a short time. Automated testing can only show its value after long-term and repeated operation. Secondly, don't think that as long as you buy tools and record some scripts, you can sit back and watch the automated test achieve the expected results. You need to consider the maintenance cost of automated test scripts. With the increase and modification of the tested application functions, the number of maintenance tools for test scripts will increase dramatically.
3. Ensure the resources of test automation, including personnel and skills.
It is best to have a special automation test engineer to ensure the continuous and smooth progress of test automation. Automated test engineers need to be responsible for project test automation, design test framework and script structure, solve the development problems of various test scripts, and ensure that automated tests can be planned, designed, developed and maintained in an orderly manner.
4. Conduct automatic testing step by step.
Don't think too much about automation from the beginning, it is often impossible. You should be familiar with the basic skills of tools and automated testing since childhood, and then integrate resources to realize some basic automated test cases, such as smoke testing-type automated test scripts. First, realize the automatic testing of those functional modules that are easy to realize and relatively stable, and then consider gradually expanding and supplementing other functional modules that are relatively difficult to realize or relatively unstable.
5. Ensure the maturity of the testing process
If the capability maturity of software enterprise's testing process and project management process is relatively low, the success rate of automated testing is also relatively low. Before conducting automated testing, we should first examine the management capabilities of all aspects of software enterprises. For example: Is the test conducted independently? Is there configuration management? How is the progress control ability? Don't blindly introduce test automation if the capability maturity of all aspects is poor.
The goal of automation:
Automated testing should look like this:
Automation As A Service, and all testers and developers should be able to run automation conveniently by themselves.
The running results of automated tests should be analyzed automatically, taking up little time.
The success rate of automated testing should be very high (for example, above 95%).
Automation should be written once and run many times.