UI automated testing refers to the use of automated testing tools or scripts to run the system or application on the front-end interface of the software that needs to be tested under preset conditions and the existing test data and to obtain the data results displayed on the front-end pages for verification, evaluation and test conclusions.
Where can UI automated testing be used?
1. Based on the test channel, it can be divided into mobile Apps, Pc web, mobile web, etc.
2. Based on the testing phase, can be divided into the smoke test, regression test, production acceptance test, and compatibility test.
Why use UI to automate testing?
1. At present, due to the excessive number of test cases, it takes too long to execute the test cases manually, and there will be test cases that cannot complete the execution so that the version cannot be launched as expected.
2. The steps of the case are tedious, the scene is complex, and the process of making test data is complex, which leads to long manual execution time.
3. The requirements are simple, and the requirements of development without front-end functions can be tested and concluded by using UI automation.
4. It can help developers to self-test.
Which tests can perform UI automation?
1. Projects that are already mature, projects that do not require any major changes for the time being.
2. Manual execution of projects that take a long time and tedious process.
3. Simple data check, list function check
How to perform automated testing.
1. Develop your use before testing, configure the environment and automated testing tools, download script execution, and view the implementation and results through the test report.
2. In the smoke test, the test is executed after the development test, and the execution and test results are checked through the test report.
3. In regression testing, testers execute test scripts that are included in the regression test and execute.
4. Production acceptance, UI automated test script can be used in production acceptance, without manual operation to verify the production situation.
For regression testing, generally speaking, many of the cases in the regression test are those in the previous version. After more iterations, the number of cases in the regression test will slowly increase, and finally there will be a situation that will not be finished when the regression test case is executed after the board is sealed. After using UI automated testing, the previous regression test case can be executed without manual execution. After the script has been executed, look at the script test report and screenshots, the success or failure is clear at a glance, and then the tester can focus on the requirements of the current iteration.
For smoke testing (without front-end changes), developers need to conduct self-testing before testing. After configuring the UI automated testing environment on their computers, they can use tools to execute self-testing; testers can also use scripts to conduct self-testing after development and testing.