Network management automation test project practice Lenovo (GUI testing framework testing design)

Author: Sun zongtao, a member of TiB Studio

These days, the telecom network management automation test project has finally completed a phase of framework construction.

To sum up, the network management automation project is mainly divided

1. Operations and judgment of the network management Gui

2. Determine whether the configuration is delivered successfully.

The framework of the method combined with the previously considered script and recording playback is unsuccessful for several reasons:

1. The recording script has poor identification. The recording playback tool uses the static object ing mechanism to read the object attributes of its control, calculate and determine whether the interface can be identified based on the threshold value of the Object Property. Therefore, frequent changes in the interface control property may make it difficult to identify the interface object and cause frequent scripts to fail to run.

2. The recorded script is too difficult to maintain. For example, if a button is a "OK" button, if a project has 100 scripts, 50 scripts have the "OK" button. One day, the R & D department needs to change "OK" to "yes", so 50 script projects need to be changed, therefore, the maintenance volume is too large.

3. What's more, the flexibility and scalability of the recorded script are too poor. The script recording is mainly based on the test case. If the test case is changed, the script also needs to be changed. However, it takes a lot of time to change the script, and the script debugging process consumes a lot of time.

Therefore, in general, why does GUI automation fail in many companies? The main reason is that they believe in tools too much, but have no further concerns. There is no automated testing framework suitable for their own companies.

Therefore, based on the above defects, the requirements are analyzed, and a testing framework suitable for the network management product is summarized and designed:

1. Hierarchical. The object Layer, logic layer, and use case layer are separated, intuitive and clear.

2. Attention. Each layer only pays attention to the things of its own level, which greatly reduces the maintenance workload.

3. Coupling: there is no impact between layers, and the coupling between layers is low. parameters are transmitted through interfaces.

4. perform operations on the device and network management respectively by using scripts to complete the second part of the project.

Practice has proved that the testing project built using this framework is much better than the previous recording playback and some script technology. In practice, the recording method has been basically abandoned, but the object recognition technology of the tool and some classes and libraries are used.

Target development: When can we build a stable framework without tools or directly using open-source tools.