"Automated testing is essentially the same as the software development process. It is nothing more than using automated testing tools (equivalent to software development tools), after analyzing test requirements (requirements analysis in the software process), and designing automated test cases ( requirements specification in the software process), so as to build the framework of automated testing (summary design in the software process), design and write automated scripts (detailed design and coding), test the correctness of the scripts, and complete the set of test scripts (that is, the main The function is test application software). The following introduces the basic process of software automation test (with flow chart)
1. Develop a test plan
Before starting the automated test, it is best to make a test plan, clarify the test object, test purpose, test project content, test method, test progress requirements, and ensure that the manpower, hardware, data and other resources required for the test are fully prepared . After the test plan is developed, it is sent to the use case designer.
2. Analyze test requirements
The use case designer analyzes the test requirements according to the test plan and the requirement specification, and designs the test requirement tree, so that the use case design can cover all the demand points. Generally speaking, web-based functional testing needs to cover the following aspects:
1) Page link test to ensure that each link is normal;
2) Page control testing to ensure that each control is reliable;
3) Page function test to ensure that all operations are normal;
4) Data processing test to ensure accurate data display and accurate and reliable processing;
5) Module business logic test to ensure the smooth flow of each business process.
3. Design test cases
By analyzing test requirements, design test cases that can cover all demand points, and form special test case documents. Since not all test cases can be automated, it is necessary to aggregate the test cases that can be automated into automated test cases. When necessary, the user, password, product, customer and other parameter information of the login system should be separated to form test data, which is convenient for script development.
4. Build a test environment
Automated testers can start to build the test environment at the same time as the use case design work is carried out. Because the scripting of automated tests needs to record page controls and add objects. The construction of the test environment includes the deployment of the system under test, the invocation of test hardware, the installation box setting of test tools, and the layout of the network environment.
5. Write test scripts
According to the difficulty level of automated test cases and problems, take a proper script development approach to write tests thinner. Generally, the page controls required for the test are obtained by recording first, and then the execution of the script is controlled by structured statements, and checkpoints and exception judgment feedback statements are inserted to separate common and common functions into shared scripts, and wake up data parameters when necessary change. Of course you can also edit scripts with other advanced features. After the script is written, it needs to be executed repeatedly and debugged until it runs normally. The writing and naming of scripts must comply with management regulations for unified management and maintenance.
6. Analyze test results and record test questions
The results of automated testing should be analyzed in a timely manner. It is recommended that testers spend a certain amount of time every day to analyze the results of automated testing in order to find defects as early as possible. If an open source automated testing tool is used, it is recommended to carry out secondary development so as to be closely integrated with the defect management tool selected by the testing department. Ideally, after an automated test case fails, the automated test platform will automatically report a defect. Testers only need to take a certain amount of time every day to confirm whether these automatically reported defects are real system defects. If it is a system defect, submit it to the developer for repair. If it is not a system defect, check the automated test script or test environment.
7. Tracking and testing bugs
The BUG recorded by the test should be recorded in the defect management tool for regular tracking and processing. After the developer fixes it, it is necessary to perform a regression test for this problem, that is, repeat the corresponding thinner version of the problem, and close it if the execution passes, otherwise continue to modify. If the modification plan of the problem is agreed with the customer, but deviates from the original requirements, the script needs to be modified and debugged before the regression test.
8. Maintenance of automated scripts
If the system changes, maintain the automated test scripts and related documents including "Automated Test Cases" and "Automated Script Design Manual" to adapt to the changed system.
The figure below is the basic flowchart of automated testing, and the task owners for each stage, output, etc...
If the article is helpful to you, remember to like, bookmark, and add attention. I will share some dry goods from time to time...
END Supporting Learning Resources Sharing
Finally: In order to give back to the die-hard fans, I have compiled a complete software testing video learning tutorial for you. If you need it, you can get it for free 【保证100%免费】
加入我的软件测试交流qq群：110685036免费获取~（同行大佬一起学术交流，每晚都有大佬直播分享技术知识点）Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
How to obtain the full set of information:
