Excerpt 12-Maintenance of automated test scripts

Excerpt 12-Maintenance of automated test scripts

Http://www.china-pub.com/196509

 

 

 

Project Review>

2008-5-27

At present, Project A's automated testing project is being carried out in an orderly manner. The test scripts of the Basic module are developed, and various common test operations are extracted as common functions, it lays a solid foundation for subsequent integration testing and automated testing Script Development in the system testing phase.

The current smoke test script is well integrated with the daily build framework to detect changes in the test version in a timely manner. You can open the automated smoke test report every morning to view the running logs, if "unable to find the object... "Error Log information, it is likely that the interface of the tested program version has changed, the programmer may have adjusted or renamed the interface control; of course, there may also be problems with writing test scripts.

In this case, you can locate the wrong code line and open the Object Browser in testcomplete to view the test objects in the new version of the program. Generally, you can find that either the control object name has changed, or the hierarchy of the control object has changed. For example, a parent control object of the container type such as panel or groupbox is added.

Modifying and maintaining these test objects will increase the workload in the early stage because the interface design at the unit module stage is not stable. However, if you can learn about these changes in a timely manner through the smoke test every day and correct the changes in time, the workload is not too large, because the workload is broken down into daily script maintenance work.

 

Project Review>

Today, the automated smoke test script fails to run. Xiao He sent an email explaining that this was caused by frequent modification of the interface elements of the main interface and some functional modules.

I replied to Xiao He and Xiao Li, saying:

You can understand the progress and plan of the interface adjustment. Otherwise, the maintenance workload of the automated test script will be high. You can perform unified maintenance after the adjustment, and then run the smoke test script.

This problem occurs during unit module development and testing. However, if this problem occurs frequently during integration testing and system testing, developers should be reminded.

This phase focuses on script development and function encapsulation for core test operations of functional modules submitted for testing.

 

Project Review>

2008-6-12

At present, the test scripts of various functional modules are constantly developed, and the old scripts are constantly reconstructed and improved. It proves that the framework we set up was reasonable. You do not need to spend too much effort on writing scripts and maintaining scripts. In addition to manual testing, you can easily complete these tasks.

In addition, we can see that Xiao Li's test script writing level is constantly improved, and the test script writing efficiency is also improved.

Currently, most functional test scripts for question library and courseware have been implemented. In addition, the team management, device management module, and selection dialog box scripts have been added. In addition, the script for the smoke test has been improved and supplemented, and the professional grade search, courseware addition, courseware deletion, and search functions have been added.

 

 

 

 

Excerpt 12-Maintenance of automated test scripts

Http://www.china-pub.com/196509