Method and device for testing relay protection equipment, electronic equipment and storage medium

Abstract

This application discloses a testing method, apparatus, electronic device, and computer-readable storage medium for relay protection equipment, which improves the test case reuse rate and reduces the difficulty of test case updates and maintenance. The method includes: obtaining a configuration file for the relay protection equipment; parsing the configuration file to obtain a test case table, a relay protection information table, and source and target identifiers; obtaining target test case script files from a test case library based on test case information in the test case table, the test case library including test case script files corresponding to each functional unit; obtaining relay protection information; associating the relay protection information with the source identifier in the relay protection information table; for each target test case script file, reading the target relay protection information, and performing tests based on the target relay protection information and the target test case script file to obtain test results, wherein the target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier of the target test case script file.

Description

Technical Field

[0001] This application belongs to the field of power technology, and in particular relates to a testing method, apparatus, electronic device and computer-readable storage medium for relay protection equipment. Background Technology

[0002] Currently, testing systems for various relay protection devices are designed with individual test cases for each specific model, resulting in a single large test case set for each model. While identical unit test cases can be copied across different models, updating or upgrading a unit test case requires updating the test cases for each model individually. Furthermore, current test case files are generated by the testing system software using a pre-defined syntax, making it difficult to visually verify differences between files and significantly hindering the maintenance and iteration of test case files.

[0003] In other words, existing testing methods for relay protection equipment have a low reusability rate for test cases, and it is difficult to update and maintain test cases. Summary of the Invention

[0004] This application provides a testing method, apparatus, electronic device, and computer-readable storage medium for relay protection equipment, which can solve the problems of low test case reuse rate and difficulty in updating and maintaining test cases in existing relay protection equipment testing methods.

[0005] In a first aspect, embodiments of this application provide a testing method for relay protection equipment, including:

[0006] Obtain the configuration file of the relay protection device;

[0007] The configuration file is parsed to obtain the test case table and the relay protection information table of the relay protection equipment, as well as the source identifier and target identifier of the relay protection information table, and the source identifier corresponds to the target identifier;

[0008] Based on the test case information in the test case table, the target test case script file is obtained from the test case library, which includes the test case script files corresponding to each functional unit.

[0009] Obtain relay protection information from relay protection devices;

[0010] Associate the relay protection information with the source identifier of the relay protection information table;

[0011] For each target test case script file, the target relay protection information is read, and tests are performed based on the target relay protection information and the target test case script file to obtain the test results. The target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier in the target test case script file.

[0012] As can be seen from the above, by breaking down the functions of various types of relay protection equipment and constructing test case script files for the smallest functional unit of each product, and then combining the test case script files of each functional unit into a test case library, the test case script file of the corresponding functional unit can be selected from the test case library according to the function of the relay protection equipment to be tested. Test case script files with the same function can be reused, thereby improving the reusability of test cases. Moreover, only offline updates and maintenance of the test case script files of each functional unit are required, which is relatively easy.

[0013] In some possible implementations of the first aspect, the relay protection information includes setting information, input / output interface information, and event information, and the relay protection information table includes a setting table, an input / output interface table, and an event table.

[0014] Among some possible implementations of the first aspect, the relay protection information is associated with the source identifier of the relay protection information table, including:

[0015] Associate the set value information with the set value table to determine the source identifier associated with the set value information;

[0016] Associate the input / output interface information with the input / output interface table to determine the source identifier associated with the input / output interface information;

[0017] Associate event information with the event table to determine the source identifier associated with the event information.

[0018] Among some possible implementations of the first aspect, after obtaining the test results, the method also includes:

[0019] Based on the test results, a test report is generated according to the title name and title level in the test case table.

[0020] In some possible implementations of the first aspect, the configuration file is an XML configuration file.

[0021] Secondly, embodiments of this application provide a testing apparatus for relay protection equipment, comprising:

[0022] The configuration file acquisition module is used to acquire the configuration files of relay protection devices;

[0023] The parsing module is used to parse the configuration file to obtain the test case table and the relay protection information table of the relay protection device, as well as the source identifier and target identifier of the relay protection information table, with the source identifier corresponding to the target identifier;

[0024] The test case script file acquisition module is used to obtain the target test case script file from the test case library based on the test case information in the test case table. The test case library includes test case script files corresponding to each functional unit.

[0025] The acquisition module is used to acquire relay protection information from relay protection devices.

[0026] The association module is used to associate relay protection information with the source identifier of the relay protection information table;

[0027] The testing module is used to read the target relay protection information for each target test case script file, and perform tests based on the target relay protection information and the target test case script file to obtain test results. The target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier in the target test case script file.

[0028] In some possible implementations of the second aspect, the relay protection information includes setting information, input / output interface information, and event information, and the relay protection information table includes a setting table, an input / output interface table, and an event table.

[0029] In some possible implementations of the second aspect, the association module is specifically used for:

[0030] Associate the set value information with the set value table to determine the source identifier associated with the set value information;

[0031] Associate the input / output interface information with the input / output interface table to determine the source identifier associated with the input / output interface information;

[0032] Associate event information with the event table to determine the source identifier associated with the event information.

[0033] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any of the first aspects above.

[0034] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method described in any of the first aspects above.

[0035] Fifthly, embodiments of this application provide a computer program product that, when run on an electronic device, causes the electronic device to perform the method described in any one of the first aspects above.

[0036] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 A flowchart illustrating a testing method for relay protection equipment provided in an embodiment of this application;

[0039] Figure 2 This is a schematic diagram illustrating the reference relationships of the test script files provided in the embodiments of this application;

[0040] Figure 3 A schematic block diagram of a test system for relay protection equipment provided in an embodiment of this application;

[0041] Figure 4 A structural block diagram of the testing device for relay protection equipment provided in the embodiments of this application;

[0042] Figure 5 A schematic block diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0043] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0044] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0045] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0046] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0047] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0048] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0049] Please see Figure 1 This is a flowchart illustrating a testing method for relay protection equipment provided in an embodiment of this application. The method may include the following steps:

[0050] Step S101: Obtain the configuration file of the relay protection device.

[0051] The configuration file mentioned above can be written in XML, i.e., an XML configuration file, or it can be written in other languages; there is no limitation here.

[0052] Typically, a corresponding configuration file is pre-written for each type of relay protection device. The configuration file may include a relay information protection table and a test case table.

[0053] The relay information protection table can include a setting table, an input / output interface table, and an event table. Each setting, input / output, and protection event is assigned a source identifier and a target identifier, which are unique and correspond one-to-one. For example, the source identifier and target identifier are specifically represented as a source ID and a target ID. In practical applications, the setting table of the relay protection device under test is collected, and a source ID and a target ID are assigned to the relevant setting information in the setting table. The source ID is used to associate with the setting read online by the test system; the target ID is used for reference in the test example script file.

[0054] Similarly, the input and output interface information of the relay protection device under test is collected, and a source ID and a target ID are assigned to the input and output interface information. The source ID is used to associate with the corresponding output of the test instrument, and the target ID is used for reference by the test example script file.

[0055] Collect event information from the relay protection device under test, and assign a source ID and a target ID to the event information. The source ID is used to associate with the signal received by the test instrument client, and the target ID is used for reference by the test example script file.

[0056] For example, the setpoint table can be shown in Table 1 below, the input / output interface table can be shown in Table 2 below, and the event table can be shown in Table 3 below.

[0057] Table 1

[0058] XML attribute name meaning type Value range description SetType Fixed value type string String / Integer desc Fixed value description string Chinese characters SouID Fixed value source ID string ID_SouSet001~ID_SouSet200 DesID Fixed Target ID string ID_DesSet001~ID_DesSet200

[0059] Table 2

[0060] XML attribute name meaning type Value range description IOType IO types string Input / Output desc IO Description string Chinese characters SouID IO Source ID string ID_SouIO001~ID_SouIO200 DesID IO target ID string ID_DesIO001~ID_DesIO200

[0061] Table 3

[0062]

[0063] The test case list includes test case information. Typically, based on the function of the relay protection device under test, the required test case script files are determined, and multiple test case script files are arranged and combined in a certain order to form a system test plan for a specific model of relay protection device.

[0064] Test case information can be specifically represented by a number and a test script name, which must be consistent with the script file name in the test case library. For example, 0001_Differential Current Setting Test.

[0065] For example, the test case table can be shown in Table 4 below.

[0066] Table 4

[0067]

[0068] As shown in Table 4 above, the CaseTAB table also has a CellOnOff attribute configured. When the test system executes test cases, it only runs test cases with the CellOnOff attribute configured as ON; when the CellOnOff attribute is configured as OFF, the test system automatically skips that test item. The CellOnOff attribute enables the test system to be compatible with various comprehensive or simplified test scenarios.

[0069] The test case table also includes Contents and Level attributes, which are used to automatically generate headings at various levels in the test report, facilitating a consistent test report format. Specifically, the Contents attribute specifies the content of the corresponding section for each test item in the test report, while the Level attribute specifies the heading level of the test item. After completing the tests, the test system software parses the Contents and Level attributes of the test case table in the XML configuration file and generates the corresponding test report sections.

[0070] Step S102: Parse the configuration file to obtain the test case table and the relay protection information table of the relay protection equipment, as well as the source identifier and target identifier of the relay protection information table, with the source identifier corresponding to the target identifier.

[0071] Step S103: Based on the test case information in the test case table, obtain the target test case script file from the test case library. The test case library includes test case script files corresponding to each functional unit.

[0072] In practical applications, the protection function of relay protection equipment can be broken down into N smallest logical units. Each logical unit has protection test cases prepared according to testing requirements, and these test cases are defined in script form. Each logical unit is saved as an independent script file, thus forming the test case script files for each functional unit.

[0073] Test case script files can be named in the format of "number + name", such as "0001_Differential Current Setting Test". Test case script files consisting of multiple smallest logical units collectively form the test case library for relay protection equipment. Test case script files for different types of protection equipment can be stored in the test case library, and script files with different functions should be named using different numbers.

[0074] Test case information can include a name and a number, and the name and number must be consistent with those in the test case library. Therefore, the target test case script file can be obtained from the test case library based on the test case information.

[0075] Understandably, script files in the test case library can reference relay protection settings, input / output operations, and event information via target IDs, achieving a one-to-one mapping between script logic references and relevant relay protection settings, input / output operations, and event information. For example, referencing test case script files can be done as follows: Figure 2 As shown.

[0076] Step S104: Obtain the relay protection information of the relay protection device.

[0077] Understandably, the test case library is offline, allowing for offline upgrades, updates, and maintenance of individual test case script files. However, what is being retrieved here is the relay protection information from online relay protection devices. This relay protection information includes setting information, input / output interface information, and event information.

[0078] Step S105: Associate the relay protection information with the source identifier of the relay protection information table.

[0079] In practical applications, setting information can be associated with a setting table to determine the source identifier associated with the setting information; input / output interface information can be associated with an input / output interface table to determine the source identifier associated with the input / output interface information; and event information can be associated with an event table to determine the source identifier associated with the event information. After this association, the test script file can reference the setting information, input / output interface information, and event information associated with the corresponding source identifier through the target identifier.

[0080] Step S106: For each target test case script file, read the target relay protection information, and perform tests based on the target relay protection information and the target test case script file to obtain the test results. The target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier in the target test case script file.

[0081] Each target test script file has an associated target identifier. Since the target identifier and source identifier are uniquely correlated, the target test script file can reference the relay protection information associated with the corresponding source identifier through the target identifier. This allows the target test script file to be run and the corresponding target relay protection information to be read for testing, thus obtaining the test results.

[0082] In some embodiments, such as Table 4 above, if the test table also includes a title and title level, a test report can be generated based on the test results, according to the title name and title level in the test case table.

[0083] To better illustrate the improved testing scheme in the embodiments of this application, the following is combined with... Figure 3 The system block diagram shown is used for explanation.

[0084] like Figure 3As shown, relevant information is extracted through the testing system, and a test case library is established based on this information. The test case library includes test case script files for each functional unit. Then, relevant information of the relay protection equipment, such as setting information, input / output interface information, and event information, is extracted to obtain the relay information protection table. The XML configuration file is parsed to obtain the setting table, input / output interface table, event table, and test case table, and the source ID of the relay protection information table and the XML configuration file are associated. Based on the test case table, the corresponding test case script file is obtained from the test case library, and the relay protection information associated with the source ID corresponding to the target ID is read. The test is then performed to obtain the test results and generate a test report.

[0085] As can be seen from the above, by breaking down the functions of various types of relay protection equipment and constructing test case script files for the smallest functional unit of each product, and then combining the test case script files of each functional unit into a test case library, the test case script file of the corresponding functional unit can be selected from the test case library according to the function of the relay protection equipment to be tested. Test case script files with the same function can be reused, thereby improving the reusability of test cases. Moreover, only offline updates and maintenance of the test case script files of each functional unit are required, which is relatively easy.

[0086] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0087] Corresponding to the test method for relay protection equipment described in the above embodiments, Figure 4 A structural block diagram of a test apparatus for relay protection equipment provided in an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiment of this application are shown.

[0088] Reference Figure 4 The device includes:

[0089] Configuration file acquisition module 41 is used to acquire the configuration file of the relay protection device;

[0090] Parsing module 42 is used to parse the configuration file to obtain the test case table and the relay protection information table of the relay protection device, as well as the source identifier and target identifier of the relay protection information table, and the source identifier and target identifier correspond to each other;

[0091] The test case script file acquisition module 43 is used to obtain the target test case script file from the test case library based on the test case information in the test case table. The test case library includes test case script files corresponding to each functional unit.

[0092] Module 44 is used to acquire relay protection information of relay protection equipment;

[0093] The association module 45 is used to associate relay protection information with the source identifier of the relay protection information table;

[0094] Test module 46 is used to read the target relay protection information for each target test case script file, and perform tests based on the target relay protection information and the target test case script file to obtain test results. The target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier in the target test case script file.

[0095] In some possible implementations, relay protection information includes setting information, input / output interface information, and event information, and the relay protection information table includes a setting table, an input / output interface table, and an event table.

[0096] In some possible implementations, the association module is specifically used to: associate setpoint information with a setpoint table to determine the source identifier associated with the setpoint information; associate input / output interface information with an input / output interface table to determine the source identifier associated with the input / output interface information; and associate event information with an event table to determine the source identifier associated with the event information.

[0097] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0098] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 5 of this embodiment includes: at least one processor 50 ( Figure 5 (Only one is shown in the diagram), memory 51, and computer program 52 stored in said memory 51 and executable on said at least one processor 50, wherein said processor 50 executes said computer program 52 to implement the steps in any of the above-described target tracking method embodiments.

[0099] The electronic device 5 can be a desktop computer, laptop, handheld computer, or cloud server, etc. This electronic device may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art will understand that... Figure 5 This is merely an example of electronic device 5 and does not constitute a limitation on electronic device 5. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0100] The processor 50 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0101] In some embodiments, the memory 51 may be an internal storage unit of the electronic device 5, such as a hard disk or memory of the electronic device 5. In other embodiments, the memory 51 may be an external storage device of the electronic device 5, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device 5. Furthermore, the memory 51 may include both internal and external storage units of the electronic device 5. The memory 51 is used to store the operating system, applications, bootloader, data, and other programs, such as the program code of the computer program. The memory 51 can also be used to temporarily store data that has been output or will be output.

[0102] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0103] This application also provides an electronic device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, wherein the processor executes the computer program to implement the steps in any of the above method embodiments.

[0104] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0105] This application provides a computer program product that, when run on an electronic device, enables the electronic device to perform the steps described in the various method embodiments above.

[0106] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0107] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0108] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0109] In the embodiments provided in this application, it should be understood that the disclosed devices, electronic devices, and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings or direct couplings or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0110] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0111] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A test method for relay protection equipment, characterized in that, include: Obtain the configuration file of the relay protection device; The configuration file is parsed to obtain the test case table and the relay protection information table of the relay protection device, as well as the source identifier and target identifier of the relay protection information table. The source identifier corresponds to the target identifier. The target identifier is used for reference by the test case script file. Based on the test case information in the test case table, the target test case script file is obtained from the test case library, which includes test case script files corresponding to each functional unit. Obtain the relay protection information of the relay protection device; Associate the relay protection information with the source identifier in the relay protection information table; For each target test case script file, target relay protection information is read according to the target identifier associated with the target test case script file, and tests are performed according to the target relay protection information and the target test case script file to obtain test results. The target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier associated with the target identifier associated with the target test case script file.

2. The method as described in claim 1, characterized in that, The relay protection information includes setting information, input / output interface information, and event information. The relay protection information table includes a setting table, an input / output interface table, and an event table.

3. The method as described in claim 2, characterized in that, Associating the relay protection information with the source identifier in the relay protection information table includes: The set value information is associated with the set value table to determine the source identifier associated with the set value information; The input / output interface information is associated with the input / output interface table to determine the source identifier associated with the input / output interface information; The event information is associated with the event table to determine the source identifier associated with the event information.

4. The method as described in claim 1, characterized in that, After obtaining the test results, the method further includes: Based on the test results, a test report is generated according to the title name and title level in the test case table.

5. The method as described in claim 1, characterized in that, The configuration file is an XML configuration file.

6. A testing device for relay protection equipment, characterized in that, include: The configuration file acquisition module is used to acquire the configuration files of relay protection devices; The parsing module is used to parse the configuration file to obtain the test case table and the relay protection information table of the relay protection device, as well as the source identifier and target identifier of the relay protection information table, wherein the source identifier corresponds to the target identifier; the target identifier is used for reference by the test case script file; The test case script file acquisition module is used to acquire the target test case script file from the test case library based on the test case information in the test case table. The test case library includes test case script files corresponding to each functional unit. The acquisition module is used to acquire the relay protection information of the relay protection device; The association module is used to associate the relay protection information with the source identifier of the relay protection information table; The testing module is used to read target relay protection information for each target test case script file according to the target identifier associated with the target test case script file, and to perform tests based on the target relay protection information and the target test case script file to obtain test results. The target relay protection information is the relay protection information associated with the source identifier corresponding to the target identifier associated with the target identifier associated with the target test case script file.

7. The apparatus as claimed in claim 6, characterized in that, The relay protection information includes setting information, input / output interface information, and event information. The relay protection information table includes a setting table, an input / output interface table, and an event table.

8. The apparatus as claimed in claim 7, characterized in that, The association module is specifically used for: The set value information is associated with the set value table to determine the source identifier associated with the set value information; The input / output interface information is associated with the input / output interface table to determine the source identifier associated with the input / output interface information; The event information is associated with the event table to determine the source identifier associated with the event information.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 5.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 5.

Images