Automated testing is usually divided into interface testing and UI testing. From the perspective of testers, it is very hopeful that there will be sufficient interface testing to ensure the quality of the proposed test version, but the actual situation is often the unit test and interface test maintained by the development team. Very inadequate, and some developers do not even do unit testing.
One: UI automation
1. Under what circumstances will UI automation be implemented?
- The company has a need for UI automation
- The platform tends to be stable and there is no need for frequent releases
- Automatic regression verification after release
- Testers have coding skills and sufficient manpower
- Long platform maintenance cycle
2. What is the purpose of UI automation?
- Frequently talked about problems, solve the repetitive work of functional testers, and release hands
- Regularly verify the basic process of the platform
- The basic process of the verification platform is automatically triggered after the version is released
3. The sequelae of UI automation
- Huge use cases
- Very unstable and difficult to maintain
- Input and output are not proportional
- Need full-time staff to maintain and update
4. Thinking about common problems of UI automation
-
git: If you use git, you need to be very familiar with the git command, otherwise it is very tricky to handle the exception information in the code submission (the error cannot be processed in time after the error is reported, resulting in a long time for resolution and affecting work efficiency)
-
Selenium: In the process of script execution, we must think more about abnormal information, find out the key points that cause the abnormal information, and find solutions to the key points, instead of blindly solving, remember, think more, and solve the problem. Very important
-
Summary, summarize and record common errors, such as blog, OneNote
Two: Interface automation
1. Under what circumstances will interface automation be implemented?
- Too many interfaces, slow manual testing
- The interface involves encryption processing, manual testing cannot be performed
2. What is the purpose of interface automation?
- Interface regression verification (normal and abnormal)
3. What are the advantages of automated interface testing?
- Improve test efficiency during project iterative development
- Improve the efficiency of regression testing, and increase the coverage of test scenarios and code coverage
- Solve the problem of repeated test data in the project
4. Thinking about common problems of interface automation
- Construction of the overall framework
- Data-driven issues, such as excel
Recommend good articles:
10 years of software testing engineers' perceptions-to friends who are still in confusion
What kind of person is suitable for software testing?
Knowledge to understand python automated testing(3)
Which is more suitable for automated testing, Python or Java?
The daily work of software testers
Play with Python+Selenium automated testing in 10 minutes, and teach you a quick start!
Finally: Welcome to follow the editor to receive a summary of the core knowledge of Python automated test engineers with a 300-page pdf document! Software testing technology exchange group: (313782132) The content of these materials are all the knowledge points that the interviewer must ask during the interview. The chapter includes many knowledge points, including basic knowledge, Linux essentials, Shell, Internet program principles, Mysql Database, package capture tool topics, interface testing tools, advanced testing-Python programming, Web automation testing, APP automation testing, interface automation testing, advanced continuous integration testing, testing architecture development testing framework, performance testing, security testing, etc.