Summary of qtp automated software testing framework

It is found that writing automated test scripts is not difficult. What is difficult is that you cannot find the direction of the test framework. Without a good test framework, the written test scripts are very difficult to maintain, if the software interface or function changes slightly, there will be great changes.

I found a framework that is very good. I personally think that my current understanding of the framework is not in place.

Http://www.cnblogs.com/nckiki/articles/244202.html

1. Data-driven framework

This framework is basically used as a sub-framework, because whatever framework is used, it is basically included, this framework separates the test data from the test script to facilitate data modification.

2. Test script Modularization

The modular framework of the test script must be created to represent the application under the test. Program (Application-under-test) module, small and independent scripts of parts and functions. Then, these scripts are grouped into larger tests in a hierarchical manner to implement a specific test case. Among all the frameworks I will mention, such frameworks should be the easiest to master. Building an abstraction layer in front of a component to hide other components of the application is a well-known programming strategy. It isolates applications from component modifications and specifies the adequacy in application design. To improve the maintainability and measurability of the test suite, the test script modular framework applies the principles of abstraction or encapsulation. When the control is moved or changed, you only need to modify the underlying script of the call control, instead of all test cases of the Control. 3. the framework of the Test Library module test library is very similar to the modular framework of the test script and has the same advantages. However, it divides the test application into processes and functions, rather than scripts. This framework requires the creation of library files (sqabasic libraries, APIs, DLLs, etc.) that represent the application modules, parts, and functions under the test ). Then these library files are directly called by the test case script. If the control changes, you only need to modify the library file and update all scripts that call the control.