CN117749675A - A CMS communication protocol testing method and system - Google Patents

Abstract

The invention belongs to the field of communication protocol testing, and particularly relates to a CMS communication protocol testing method and system. According to the invention, by setting the test case capable of configuring the traversal attribute and the corresponding traversal test step, under the condition that the traversal attribute is configured by the test case, according to the test step corresponding to the traversal attribute value to be tested, continuously executing the current test step under the condition that the test step is not executed, executing the next test step after the execution is completed until each test step of the current traversal attribute value is executed, and then testing the new untested traversal attribute value until the untested traversal attribute value does not exist; therefore, after one test case is called, different traversal attribute values of the test case can be circularly tested, tests corresponding to all traversal attribute values are completed, the tests of a plurality of traversal attribute values can be realized without setting a plurality of test cases, reusability of the test cases is improved, a test case library is simplified, and therefore test efficiency is improved.

Description

A CMS communication protocol testing method and system

Technical field

The invention belongs to the field of communication protocol testing, and specifically relates to a CMS communication protocol testing method and system.

Background technique

In order to optimize the communication between secondary equipment in the substation, the new generation of autonomous and controllable substations adopts the station control layer communication protocol (CMS Communication Protocol: CommunicationMessage Specification) based on DL/T860 substation secondary system communication messages to replace the original The MMS protocol, on the premise of following the IEC61850 standard in the field of power system automation, realizes the localization of the communication service protocol between the substation station control layer and bay layer equipment. Most of the corresponding automatic test tools for substation communication protocols are limited to MMS protocol testing. They lack automatic testing methods for CMS communication protocols. Manual methods can only be used. The testing efficiency is low, and the accuracy and reliability cannot be guaranteed. Therefore, automatic testing of CMS communication protocols is not possible. The development of test methods is very important.

For example, the Chinese invention patent application with publication number CN115396352A discloses a CMS server-side protocol testing method, system, equipment and storage medium; this solution automatically analyzes and selects the tests that need to be performed by analyzing the device under test that has completed test data and service settings. Use the test case and execute the test according to the selected test case to realize automatic testing; specifically, in the step queue, step by step information is taken out to execute the corresponding service, and the actual results of the steps are put into the actual result queue until all steps in the queue are executed, and then in sequence Check the actual results of the steps. If all steps are as expected, the test case result passes, otherwise it fails; however, the CMS server-side protocol testing method in this solution relies on the device under test that completes the test data and service settings, that is, a single test Test cases can usually only be tested against the same set of test data and service settings. If you want to test different settings, you need to set up corresponding test cases separately. You may need to set up more different test cases to complete a communication function test, resulting in the need The number of test cases is large, the use case library is complex, and the testing efficiency is low.

Contents of the invention

The object of the present invention is to provide a CMS communication protocol testing method and system, which is used to solve the problem that the existing CMS communication protocol testing method may need to set different test cases separately during a communication function test process, resulting in the number of required test cases. Larger, use case libraries pose complex and less efficient testing problems.

In order to achieve the above object, the present invention provides a CMS communication protocol testing method, which includes a test case execution step in the test task execution process. It is characterized in that the test case execution step includes checking the configuration of the test case. According to the Carry out the traversal test of the test case accordingly; the configuration of the test case includes the configuration of the traversal attribute; when the test steps are executed normally, the traversal test includes the following steps:

1) Determine whether the test case is configured with the traversal attribute. If not, proceed to step 2) according to the corresponding setting test steps; otherwise, continue to determine whether there is an untested traversal attribute value in the configuration of the traversal attribute. If it does not exist, end the traversal. Test, otherwise proceed to step 2) according to the test steps corresponding to the traversal attribute value to be tested;

2) Continue to execute the current test step when the test step has not been completed. After the execution is completed, continue to execute the next test step until each test step is completed; when the test step corresponding to the current traversal attribute value is completed, repeat the steps The process of 1)-2) until the end of the traversal test.

The beneficial effects of the above technical solution are as follows: by setting test cases that can configure traversal attributes and corresponding traversal test steps, it is possible to perform loop testing on different traversal attribute values of the test case after calling a test case, thereby completing all traversal attribute values. Corresponding tests, that is, tests corresponding to multiple traversal attribute values can be implemented without setting up multiple test cases, which can improve the reusability of test cases. There is no need to set test cases separately according to different traversal attribute values, simplifying the test case library, and also It can reduce the number of calls, thereby comprehensively improving testing efficiency.

Further, the configuration of the test case also includes object grouping configuration and single frame transmission configuration. Operation object grouping refers to a collection of multiple operation objects of the same type. The configurable traversal attributes of operation objects of the same type are consistent; according to the test Methods for performing test case traversal testing based on the configuration attributes of the use case include:

a) Determine whether the test case is configured with object grouping and single frame transmission is not configured. If not, perform the traversal test corresponding to the set operation object; if so, continue to determine whether there is an untested operation object in the configuration of the object group. If it does not exist, then The traversal test will no longer be performed, otherwise the traversal test corresponding to the operation object to be tested will be performed;

b) After the traversal test corresponding to the operation object is completed, repeat the process of step a) until no more traversal tests are performed.

The beneficial effects of the above technical solution are as follows: through the setting of object grouping configuration and single frame transmission configuration, it is possible to perform loop testing on different operation objects of the test case after calling a test case, that is, multiple test cases of the same type can be completed through one test case. For tests corresponding to operating objects, there is no need to set up multiple test cases for multiple operating objects. On the basis of testing multiple operating objects, a relatively smaller number of test cases is ensured, further improving the reusability of test cases and simplifying use cases. library.

Further, the test task execution process includes:

A) Determine whether the current test task has been executed cyclically. If it has been executed cyclically, end the test. Otherwise, continue to execute the current test task and proceed to step B);

B) Determine whether the test module in the current test task has been executed. If it has been executed, proceed to step A) again. Otherwise, continue to execute the current test module and proceed to step C);

C) Determine whether all the test cases in the current test module have been executed. If not, continue to execute the current test case according to the test case execution steps and proceed to step D); otherwise, determine whether the current test module has been executed cyclically. If After the cycle execution is completed, select the next test module and repeat steps B)-C). If the cycle execution is not completed, continue to execute the current test module and repeat this step;

D) Determine whether the current test case has been cyclically executed. If not, continue execution. Otherwise, select the next test case and re-execute the judgment of steps C)-D);

Among them, the test task includes a test module and its cycle number information; the test module includes one or more test cases, and the test case includes one or more test steps and its cycle number information.

The beneficial effects of the above technical solution are as follows: through the test task execution process and the settings of test tasks, test modules, test cases and test steps, the test execution is divided into four levels, with the test task as the test as a whole, and each test task is called When testing, the test modules, test cases and test steps included in the test task can be tested accordingly according to the content of the test task, thereby further improving testing efficiency.

Furthermore, if the communication equipment under test corresponding to the test is interrupted during the test, first determine whether the next test step is a delay, association, operation prompt or other client service operation. If so, continue to execute the current test case, otherwise Prompt whether to wait for communication recovery or end the test; if you choose to wait for communication recovery, the test case will continue to be executed after the communication device under test recovers.

The beneficial effects of the above technical solution are as follows: it can facilitate timely and targeted processing of communication interruptions, and facilitate the reduction of subsequent test steps affected by abnormal communication status.

Further, if a certain test step execution exception occurs during the test, it is determined whether the test case has a failure to continue execution flag set. If it is set, it is determined that the test case has failed the test and continues to execute the subsequent test steps of the test case. Otherwise, it is determined that the test case has failed and the subsequent test steps of the test case are abandoned.

The beneficial effects of the above technical solution are as follows: it is possible to flexibly select follow-up processing measures corresponding to test step execution exceptions by setting the failure continuation flag, so as to facilitate the reduction of subsequent test steps being affected by step execution exceptions.

Further, the configuration of the traversal attribute includes the configuration of the traversal attribute type and the corresponding traversal attribute value; the traversal attribute type includes one or more of ACSI type, control block, FC function constraint and setting group number.

Further, the traversal attribute values corresponding to the ACSI type include data object DataObject, data set DATA-SET, cache report control block BRCB, non-cache report control block URCB, log control block LCB, log LOG, and setting group control block SGCB, GOOSE One or more of the control block GoCB and the multicast sample value control block MSVCB;

The traversal attribute value corresponding to the control block includes one or more of the cached report control block BRCB, the non-cached report control block URCB, the log control block LCB, the setting group control block SGCB, the GOOSE control block GoCB, and the multicast sampling value control block MSVCB. variety;

The traversal attribute values corresponding to the FC function constraints include one of status information ST, measurement value MX, control CO, description DC, configuration CF, replacement SV, setting group SG, editable setting group SE, and set point parameter SP. or more;

The traversal attribute value corresponding to the setting group number includes one or more values in the range starting from the set value to the maximum value. The maximum value is determined according to the number of setting groups in the test model corresponding to the test.

The beneficial effects of the above technical solution are as follows: it enables the traversal test corresponding to the test case to support multiple traversal attribute types, thereby improving the applicability of the test case.

Further, the test module includes one or more test cases with the same service type, and the service type includes one or more of the various service types specified in the substation secondary system communication message specification.

The beneficial effects of the above technical solution are as follows: it is equivalent to grouping test cases according to service types through the test module, which facilitates indexing according to service types to facilitate management and search of required test cases.

The invention also provides a CMS communication protocol testing system, which includes a processor, and the processor is used to execute program instructions to implement the above CMS communication protocol testing method.

The CMS communication protocol testing system can achieve the same beneficial effects as the above-mentioned CMS communication protocol testing method.

Description of drawings

Figure 1 is a flow chart of the traversal test of test cases in the CMS communication protocol testing method embodiment of the present invention;

Figure 2 is a flow chart of a method for performing test case traversal testing in the embodiment of the CMS communication protocol testing method of the present invention;

Figure 3 is a schematic block diagram of the overall process of CMS communication protocol testing in the embodiment of the CMS communication protocol testing method of the present invention;

Figure 4 is a structural block diagram of the GIS equipment intelligent monitoring and control system in the embodiment of the CMS communication protocol testing method of the present invention;

Figure 5 is a flow chart of the process of formulating a test plan in the embodiment of the CMS communication protocol testing method of the present invention;

Figure 6 is a flow chart of the loading test solution process in the embodiment of the CMS communication protocol testing method of the present invention;

Figure 7 is a flow chart of the historical task process of loading in the CMS communication protocol testing method embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

CMS Communication Protocol Test Method Example

This embodiment provides a technical solution for a CMS communication protocol testing method. The test method includes test case execution steps in the test task execution process. The test case execution steps include checking the configuration of the test case and proceeding accordingly according to the configuration. Test case traversal testing;

The configuration of the test case includes traversal attributes; referring to Figure 1, when the test steps are executed normally, the traversal test includes the following steps:

1) Determine whether the test case is configured with the traversal attribute. If not, proceed to step 2) according to the corresponding setting test steps; otherwise, continue to determine whether there is an untested traversal attribute value in the configuration of the traversal attribute. If it does not exist, end the traversal. Test, otherwise follow the test steps corresponding to the traversal attribute value to be tested and proceed to step 2); it should be noted that the "attribute value" mentioned in Figure 1 refers to the traversal attribute value.

The configuration of the traversal attribute includes the configuration of the traversal attribute type and the corresponding traversal attribute value; in this embodiment, the traversal attribute supports ACSI type, control block, FC function constraint, fixed value group number, etc. The configurable traversal attribute types include One or more of the ACSI type, control block, FC function constraint and setting group number, the configurable attribute value is one or more of the attribute values corresponding to the configured traversal attribute; configuring the traversal attribute means Configure the traversal attribute type and the attribute value corresponding to the traversal attribute type; specifically, the traversal attribute value corresponding to the ACSI type includes the data object DataObject, the data set DATA-SET, the cache report control block BRCB, the non-cache report control block URCB, and the log control One or more of block LCB, log LOG, setting group control block SGCB, GOOSE control block GoCB and multicast sample value control block MSVCB;

The traversal attribute value corresponding to the control block includes one or more of the cached report control block BRCB, the non-cached report control block URCB, the log control block LCB, the setting group control block SGCB, the GOOSE control block GoCB and the multicast sampling value control block MSVCB. indivual;

The traversal value corresponding to the FC function constraint attribute includes one or more of status information ST, measurement value MX, control CO, description DC, configuration CF, replacement SV, setting group SG, editable setting group SE, and set point parameter SP. multiple; multiple;

The traversal attribute value corresponding to the fixed value group number includes one or more numerical ranges starting from the set value (starting from 1 in this embodiment) to the maximum value. The maximum value is based on the fixed value in the test model corresponding to the test. The number of value groups is determined.

2) Initialize the test status information of the test case (the test status information itself is used to determine the test results. The test status information of the initialized test case resets or clears the parameters or sets saved or changed during the last test to facilitate a new traversal. The test corresponding to the attribute value), continue to execute the current test step when the test step has not been completed, and continue to execute the next test step until the execution of each test step is completed; when the test step corresponding to the current traversal attribute value is executed In this case, repeat steps 1)-2) until the traversal test is completed.

Therefore, the CMS communication protocol testing method in this embodiment can set up test cases that can configure traversal attributes and corresponding traversal test steps, and can perform different traversal attribute values of different traversal types of the test case after calling a test case. Loop testing to complete the tests corresponding to all configured traversal attribute values. That is, you can implement multiple traversal attribute value tests without setting up multiple test cases. This can improve the reusability of test cases and does not need to be set separately according to different traversal attribute values. Test cases simplify the test case library, while also reducing the number of test case calls and comprehensively improving testing efficiency.

In this embodiment, the configuration of the test case also includes object grouping configuration and single frame sending configuration. Operation object grouping refers to a collection of multiple operation objects of the same type. The configurable traversal attributes of operation objects of the same type are consistent; then refer to Figure 2. Methods for performing test case traversal testing based on the configuration attributes of the test case include:

a) Determine whether the test case is configured with object grouping and single frame transmission is not configured. If not, perform the traversal test corresponding to the set operation object; if so, continue to determine whether there is an untested operation object in the configuration of the object group. If it does not exist, then The traversal test is no longer performed. Otherwise, after instantiating the operation object to be tested, the traversal test corresponding to the operation object is performed; since the configurable traversal properties of the same type of operation objects are consistent, the operation objects in the operation object group can all be applied to the same The configuration of the traversal attributes, so the traversal tests of each operation object in the operation object group of the same test case can share the same traversal test configuration and related test steps, thereby achieving the completion of the traversal test of multiple operation objects through the same test case Effect.

b) After the traversal test corresponding to the operation object is completed, repeat the process of step a) until no more traversal tests are performed.

The traversal test mentioned in the above steps a) and b) and shown in the box of Figure 2 corresponds to the traversal test step of the above steps 1)-2), in which the test case is configured with object grouping instructions to be tested. There are multiple operation objects. Configuring single frame transmission means that all operation objects will be sent in one frame of CMS message (if single frame transmission is not configured, each frame of CMS message only contains one operation object); therefore, As long as single frame transmission is configured or object grouping is not configured, it means that only one frame of CMS message containing the operation object will be sent to the test object, so only a single loop is needed to traverse the CMS message of the frame, that is, only Carry out the traversal test corresponding to the set operation object; if object grouping is configured and single frame transmission is not configured, it means that multiple frames of CMS messages containing the operation object will be sent to the test object, so multiple loops are needed to process each CMS frame. The packets are traversed separately, that is, each operation object is traversed separately.

In this embodiment, through the settings of object grouping configuration and single frame transmission configuration, it is possible to perform loop testing on different operation objects of the test case after calling a test case, that is, through one test case, the tests corresponding to multiple operation objects of the same type are completed. , there is no need to set multiple test cases for multiple operation objects, and a relatively smaller number of test cases is ensured on the basis of testing multiple operation objects, further improving the reusability of test cases and simplifying the use case library.

Moreover, referring to Figure 3, in this embodiment, the test task execution process including the above test case execution steps includes:

A) Determine whether the current test task has been executed cyclically. If it has been executed cyclically, end the test. Otherwise, continue to execute the current test task and proceed to step B);

B) Determine whether the test module in the current test task has been executed. If it has been executed, proceed to step A) again. Otherwise, continue to execute the current test module and proceed to step C);

C) Determine whether all the test cases in the current test module have been executed. If not, continue to execute the current test case according to the above test case execution steps (i.e. the above steps a)-b)) and proceed to step D); otherwise, judge Whether the loop execution of the current test module is completed. If the loop execution is completed, select the next test module and re-execute steps B)-C). If the loop execution is not completed, continue to execute the current test module and repeat this step;

D) Determine whether the loop execution of the current test case has been completed. If not, continue execution. Otherwise, select the next test case and re-execute the judgment of steps C)-D).

Among them, the test task includes the test module and its cycle number information; the test module includes one or more test cases. In this embodiment, it is one or more test cases with the same service type. The test case includes one or more test steps and Its cycle number information; it can be seen that the test task execution process and the settings of test tasks, test modules, test cases and test steps in this embodiment are equivalent to dividing the test execution into four levels, with the test task as the overall test , every time a test task is called for testing, the test modules, test cases and test steps included in it can be tested according to the content of the test task, thereby further improving testing efficiency. In addition, in this embodiment, the test case library is set as a communication protocol rule knowledge base divided into three levels: test module, test case, and test step, to facilitate the selection of corresponding test cases.

Specifically, the service types include various service types stipulated in the substation secondary system communication message specifications, such as association services, directory services, data services, data set services, fixed value services, report services, and log services. , control services, file services, test services, association negotiation services, remote procedure call services, etc.

In this embodiment, the configuration of the test case can also include information such as a globally unique use case number, that is, a description. The types of operation objects used in the test steps in the test case are divided into logical devices, logical nodes, data objects, data sets, and cache report controls. block, non-cached report control block, log control block, setting group control block, log, etc. A test step is the smallest execution unit of a test case. A test step implements a basic service. The configuration related to the test step includes the unique step number, description, basic service type code, client list, number of repeated executions, and operations within the use case. Objects, operating parameters, expected responses and other information; specifically, for the CMS communication protocol, the test step types include association, abnormal abort, release association, read server directory, read logical device directory, read logical node directory, read all data values, read All data definitions, Read all control block values, Read data values, Set data values, Read data directory, Read data definitions, Create data set, Delete data set, Read data set directory, Read data set values, Set data set values, Select , with value selection, undo, execution, time activation operation, select to activate setting group, select to edit setting group, set and edit setting group value, confirm editing setting group value, read and edit setting group value, read setting group Control block value, read cache report control block value, set cache report control block value, read non-cache report control block value, set non-cache report control block value, read log control block value, set log control block value, query log by time , Query the log after the specified entry, read log status value, read file, write file, delete file, read file attribute value, list file directory, delay, start report simulation, stop report simulation, start report collection, stop report collection, Blocking report collection, pure judgment, operation prompts, replacement, replacement setting value, replacement setting quality, writing system setting value, combination control, general call report, periodic report, recording entry number, etc.

In this embodiment, refer to Figure 4 for the overall process principle when testing the CMS communication protocol. First, load the test case library and the model configuration file corresponding to the test object (i.e., the IED object, which is equivalent to the server model corresponding to the CMS communication protocol test); Then develop or load the test plan through the test plan process or load test plan process, and select the IED object to be tested; or load historical tasks through the load historical task process; then start and test; you can pause at any time during the test execution process During the test, in the paused state, you can choose to save the historical tasks and then end the test, or you can choose to continue the test or terminate the test; the test report is automatically output when the test is completed.

Specifically, referring to Figure 5, the test plan formulation process in the CMS communication protocol testing method of this embodiment includes the following steps:

Create a new test task and set the number of test task cycles; select the test module required for the test task and set the number of cycles of the test module; select the required test case in the selected test module and set the number of test case cycles; so After all the test cases corresponding to the required test modules are selected, the test task is saved to complete the formulation of the test plan.

Referring to Figure 6, the loading test solution process in the CMS communication protocol testing method of this embodiment includes the following steps:

First load the test plan. If you need to modify the test plan (i.e. test task), modify the test module and test case settings in the test plan. After the modification is completed, you can save it to cover other test plans or save it as a new test plan.

Referring to Figure 7, the loading history task process in the CMS communication protocol testing method of this embodiment includes the following steps:

Load the saved historical task and restore the task execution progress information. The task execution progress information includes the current cycle number of the test task, the current cycle number of each test module, the current cycle number of each test case, the currently executed test case, and the historical tests of each test case. Results and other data.

In addition, the CMS communication protocol testing method of this embodiment is also provided with an abnormal state self-recovery processing mechanism, such as processing of communication abnormal states and abnormal execution of a certain step in the test case. Among them, the processing method of communication abnormal states is Including: If the communication device under test (i.e. IED device) corresponding to the test is interrupted during the test, first determine whether the next test step is a delay, association, operation prompt or other client service operation, and if so, continue to execute the current test step. Test case, otherwise it will prompt whether to wait for communication recovery or end the test; if you choose to wait for communication recovery, the test case will continue to be executed after the communication device under test recovers. This can facilitate timely and targeted processing of communication interruptions, and reduce the impact of subsequent test steps from abnormal communication status.

The handling method for an execution exception of a certain step in the test case includes: if an execution exception of a certain test step occurs during the test process, determine whether the test case has a failure to continue execution flag set, and if it is set, determine that the test case has failed the test. And continue to execute the subsequent test steps of the test case, otherwise it is determined that the test case has failed the test and gives up executing the subsequent test steps of the test case; thus, the failure to continue execution flag can be set, and the test step can be flexibly selected to perform subsequent processing corresponding to the exception. Measures can be taken to reduce the impact of abnormal step execution in subsequent test steps.

CMS Communication Protocol Test System Implementation

This embodiment provides a technical solution for a CMS communication protocol testing system, which includes a processor. The processor is used to execute program instructions to implement the CMS communication protocol testing method in the above CMS communication protocol testing method embodiment.

Since the specific working methods and principles of the CMS communication protocol testing system in this embodiment have been described in detail in the above-mentioned CMS communication protocol testing method embodiment, they will not be described again here.

The invention has the following characteristics:

1) By setting up test cases that can configure traversal attributes and corresponding traversal test steps, it is possible to perform loop tests on different traversal attribute values of different traversal types of the test case after calling a test case, thereby completing all traversal attribute values corresponding to Testing, that is, you can implement tests corresponding to multiple traversal attribute values without setting up multiple test cases, which can improve the reusability of test cases. There is no need to set test cases separately according to different traversal attribute values, simplifying the test case library, and at the same time Reduce the number of calls, thus comprehensively improving testing efficiency.

2) Through the settings of object grouping configuration and single frame transmission configuration, it is possible to perform loop testing on different operating objects of the test case after calling a test case, that is, completing the testing corresponding to multiple operating objects of the same type through one test case call. , there is no need to set multiple test cases for multiple operation objects, and a relatively smaller number of test cases is ensured on the basis of testing multiple operation objects, further improving the reusability of test cases and simplifying the use case library.

3) Through the test task execution process and the settings of test tasks, test modules, test cases and test steps, the test execution is divided into four levels. The test task is the test as a whole. Each time a test task is called for testing, it can be based on According to the content of the test task, the test modules, test cases and test steps included in it are tested, thereby further improving the testing efficiency.

It should be understood that the above-described specific embodiments of the present invention are only used to illustrate or explain the principles of the present invention, and do not constitute a limitation of the present invention.

Claims (9)

1. The CMS communication protocol testing method comprises a test case execution step in a test task execution flow, and is characterized in that the test case execution step comprises the steps of checking the configuration condition of the test case and correspondingly performing traversal test of the test case according to the condition; the configuration of the test case comprises the configuration of the traversal attribute; under the condition that the test step is executed normally, the traversal test comprises the following steps:

1) Judging whether the test case is configured with the traversal attribute, if not, performing the step 2) according to the corresponding set test step; otherwise, continuing to judge whether an untested traversal attribute value exists in the configuration of the traversal attribute, ending the traversal test if the untested traversal attribute value does not exist, otherwise, executing the step 2 according to the testing step corresponding to the traversal attribute value to be tested;

2) Continuously executing the current test step under the condition that the test step is not executed, and continuously executing the next test step until each test step is executed after the execution is completed; and (3) repeating the processes of the steps 1) -2) until the traversal test is finished under the condition that the test step corresponding to the current traversal attribute value is executed.

2. The CMS communication protocol testing method of claim 1, wherein the configuration of the test cases further comprises an object grouping configuration and a single frame transmission configuration, the operation object grouping refers to a set of multiple operation objects of the same type, and configurable traversal attributes of the operation objects of the same type are consistent; the method for correspondingly performing the test case traversal test according to the configuration attribute condition of the test case comprises the following steps:

a) Judging whether the test case is configured with object grouping and is not configured with single frame transmission, if not, performing traversal test corresponding to the set operation object; if yes, continuing to judge whether an untested operation object exists in the configuration of the object group, if not, not performing the traversal test, otherwise, performing the traversal test corresponding to the operation object to be tested;

b) And d) after the traversing test corresponding to the operation object is finished, repeating the process of the step a) until the traversing test is not performed.

3. The CMS communication protocol testing method of claim 1 or 2, wherein the test task execution flow comprises:

a) Judging whether the current test task is circularly executed, ending the test if the current test task is circularly executed, otherwise, continuing to execute the current test task and performing the step B);

b) Judging whether the test module in the current test task is executed completely, if so, re-executing the step A), otherwise, continuing to execute the current test module and executing the step C);

c) Judging whether all the test cases in the current test module are executed, if not, continuing to execute the current test cases according to the test case execution step and performing the step D); otherwise, judging whether the current test module is completely circularly executed, if so, selecting the next test module and repeating the steps B) -C), and if not, continuing to execute the current test module and repeating the steps;

d) Judging whether the current test case is circularly executed, if not, continuing to execute, otherwise, selecting the next test case and repeating the judgment of the steps C) -D);

the test task comprises a test module and cycle number information thereof; the test module comprises one or more test cases, and the test cases comprise one or more test steps and cycle number information thereof.

4. The CMS communication protocol testing method of claim 1 or 2, wherein if the communication interruption occurs in the corresponding communication device under test during the testing, it is first determined whether the next testing step belongs to a delay, association, operation prompt or service operation of other clients, if yes, the current test case is continuously executed, otherwise, whether the communication is waiting for recovery or ending the testing is prompted; if the communication waiting is selected to be recovered, the tested communication equipment continues to execute the test case after the communication is recovered.

5. The CMS communication protocol test method of claim 1 or 2, wherein if an abnormal execution of a certain test step occurs during the test, it is determined whether the test case has set a fail continue flag, if so, it is determined that the test case fails the test and continues to execute the subsequent test step of the test case, otherwise, it is determined that the test case fails the test and the subsequent test step of the test case is abandoned.

6. The CMS communication protocol testing method of claim 1 or 2, wherein the configuration of the traversal attribute comprises configuration of a traversal attribute type and a corresponding traversal attribute value; the traversal attribute types include one or more of ACSI type, control block, FC function constraint, and constant value group number.

7. The method according to claim 6, wherein the traversal attribute values corresponding to the ACSI type include one or more of a DATA object DataObject, a DATA SET DATA-SET, a buffer report control block BRCB, a non-buffer report control block URCB, a LOG control block LCB, a LOG, a constant value group control block SGCB, a GOOSE control block gcb, and a multicast sample value control block MSVCB;

the traversal attribute values corresponding to the control blocks comprise one or more of a buffer report control block BRCB, a non-buffer report control block URCB, a log control block LCB, a fixed value group control block SGCB, a GOOSE control block GoCB and a multicast sampling value control block MSVCB;

the traversal attribute values corresponding to the FC function constraint comprise one or more of state information ST, measured value MX, control CO, description DC, configuration CF, substitution SV, fixed value group SG, editable fixed value group SE and set point parameter SP;

the traversal attribute values corresponding to the constant value group numbers comprise one or more of a numerical range formed from a set numerical value to a maximum value, and the maximum value is determined according to the constant value group number in the test model corresponding to the test.

8. The CMS communication protocol testing method of claim 3, wherein the testing module comprises one or more test cases of the same service type, the service type comprising one or more of the service types specified by the substation secondary system communication message specification.

9. A CMS communication protocol testing system comprising a processor for executing program instructions to implement the CMS communication protocol testing method of any of claims 1-8.