A data analysis management method and system for unattended test system

By collecting fault propagation chain diagrams and test case status comparison tables in an unattended testing system, calculating important indexes and impact indexes of test cases, dynamically adjusting the execution order, the problems of low test efficiency and redundancy in the existing technology are solved, and the problem of low test efficiency and redundancy in the existing technology is realized. More efficient protection logic testing.

CN118503127BActive Publication Date: 2024-11-26THREE GORGES JINSHA RIVER CHUANYUN HYDROPOWER DEV CO LTD YONGSHAN XILUODU POWER PLANT
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410726222.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-06-06
Publication Date
2024-11-26
Estimated Expiration
2044-06-06

AI Technical Summary

Technical Problem

The existing protection logic testing technology has problems such as manual setting execution order, machine cannot be adjusted in real time, resulting in low testing efficiency and redundancy.

Method used

An unattended testing system is adopted to collect fault propagation chain diagrams and test case status comparison tables, calculate the important index and impact index of each test case, dynamically adjust the execution order, and optimize the test process.

Benefits of technology

Accurate execution selection, intelligent status setting and dynamic sequence arrangement are realized, which improves testing efficiency and accuracy and reduces the test duration.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118503127B_ABST
    Figure CN118503127B_ABST
Patent Text Reader

Abstract

The invention discloses a data analysis management method and system for an unattended test system, and belongs to the field of automated test technology. The system includes a data acquisition module, an execution planning module, a result evaluation module and a storage warning module; the data acquisition module is used to collect a fault propagation chain diagram, a test case status comparison table, a test log and a test item; the execution planning module is used to calculate the important index and influence index of each indicator under the test item, as well as the priority index of each test case, and select the test case with the largest priority index for execution; the result evaluation module is used to analyze the execution result of the test case, set the state of the indicator and the execution state of the test case, call the execution planning module to recalculate the priority index of other test cases and execute, and stop the test until all test items are executed; the storage warning module is used to generate historical execution records and store them in the test log, and issue a warning when the execution is unexpectedly terminated.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of automated testing, and in particular to a data analysis management method and system for an unattended testing system. Background Art

[0002] In recent years, with the development of science and technology and the advancement of manufacturing technology, the automatic test project of protection logic has begun to enter people's field of vision. The relay protection tester can complete fast, convenient and safe wiring through the standardized package test line interface, automatically test the logic verification project, greatly reduce the protection logic verification time, and improve the on-site work efficiency.

[0003] At present, the verification of protection devices usually adopts the method of manually configuring the test plan and then letting the machine execute it automatically. This method has certain disadvantages. On the one hand, in the planning of test cases where there is no mandatory requirement for the execution order, the fixed execution order set manually is often rigid, and the machine cannot adjust the execution order in real time according to the test results to optimize the test efficiency during the execution process. On the other hand, the machine only executes mechanically according to the test plan and cannot understand the logical relationship between the various indicators. When it is determined that a certain indicator is abnormal, it will continue to test other indicators that must be abnormal, resulting in redundant testing. Therefore, at this stage, a more intelligent and efficient protection logic testing technology solution is needed to solve the above problems. Summary of the invention

[0004] The object of the present invention is to provide a data analysis management method and system for an unattended test system to solve the problems raised in the above background technology.

[0005] In order to solve the above technical problems, the present invention provides the following technical solutions: a data analysis and management method for an unattended test system, the method comprising the following steps:

[0006] S100, collect fault propagation chain diagram, test case status comparison table and test log, and the administrator selects test items in the solution library according to business needs and plans their execution order.

[0007] S200, obtaining the test cases that need to be executed in the test project, first calculating the importance index and influence index of each indicator under the test case, then calculating the priority index of each test case, and selecting the test case with the largest priority index to execute.

[0008] S300, obtain the execution result of the test case, set the status of the indicator by analyzing the fault propagation chain diagram, set the execution status of the test case according to the test case status comparison table, enter step S200 to recalculate the priority index of other test cases and execute them, and stop the test until all test items are executed.

[0009] S400. When the execution status of the test case is set, the indicator information is packaged into the indicator result and the execution status as a historical execution record and stored in the test log. If the execution is terminated unexpectedly, the administrator is automatically warned.

[0010] In S100, the fault propagation chain diagram includes various types of abnormal indicator chains, which are composed of indicators with different codes and are unidirectionally propagated, and all indicators under each abnormal indicator chain are of the same type. The test case status comparison table includes the judgment conditions of all test cases, which are used to judge the execution status of the test cases, and the judgment conditions include the judgment basis and the judgment result.

[0011] The test log refers to the historical execution record of the test case. Each historical execution record includes the execution status and indicator results. The execution status is normal or abnormal. The indicator results include the code, type, status, measured value and target range of each indicator. The status is normal or abnormal. The administrator refers to the relay protection test scheme administrator. The scheme library contains protection logic verification schemes for different relay protection devices. Each protection logic verification scheme contains different test items. Each test item contains different test cases. Each test case contains different indicators. Each indicator includes code, type and target range. The administrator selects p test items in the corresponding protection logic verification scheme according to business needs and plans the execution order of these test items, establishes a project collection, and puts the selected test items into the project collection in sequence according to the execution order.

[0012] The test item is a test of the protection device to achieve a specific function. The test case is a test of the performance of each component of the protection device to achieve a specific function, and the indicator is a specific parameter test of the performance of each component of the protection device to achieve a specific function. The execution order of the test items is planned by the administrator, and the execution order of each test case under the test item is not required.

[0013] The fault propagation chain diagram is used to describe the different types of fault propagation paths in the unattended test system. It is established by the administrator in advance with reference to the relationship between the relay protection logic. There are several abnormal indicator chains of the same type in the fault propagation chain diagram. The type of each abnormal indicator chain is the same as the type of all indicators under the abnormal indicator chain, including current, voltage, resistance and capacitance. The type of abnormal indicator chain is the same concept as the type of indicator.

[0014] The number of indicators under the abnormal indicator chain is related to the relay protection logic. All indicators exist in the fault propagation chain diagram and each indicator can only appear in one of the abnormal indicator chains. If one indicator in the abnormal indicator chain is abnormal, all indicators after it will inevitably be abnormal. The abnormal indicator chain is also divided based on this feature.

[0015] In S200, the specific steps are as follows:

[0016] S201. Obtain the top test project CX in the project set, establish a use case set, and put all test cases under the test project CX into the use case set; establish an indicator set, and put all indicators under the test project CX into the indicator set.

[0017] S202: Establish a coding set, obtain the codes of all indicators in the indicator set, remove duplicate codes and put them into the coding set in sequence, and calculate the importance index and influence index of the indicator corresponding to each code in the coding set. The steps are as follows:

[0018] S202-1. The number of statistical indicator codes Zbm in the indicator set ZJH Zbm , and the number of all indicators in the indicator set ZJH sum , ZJH Zbm Divide by ZJH sum Get the importance index ZhZ.

[0019] There may be indicators with the same code in different test cases, so there are also indicators with the same code in the indicator set. The importance index is related to the frequency of the indicator in the indicator set. The higher the frequency, the greater the importance index.

[0020] S202-2. Retrieve and count the number of historical execution records containing indicator code Zbm in the test log And analyze the number of historical execution records where the indicator code Zbm corresponds to an abnormal state

[0021] S202-3. Find the abnormal indicator chain containing the indicator coded as Zbm in the fault propagation chain diagram Statistical anomaly indicator chain The number of all indicators after the corresponding indicator in the indicator code Zbm Substitute into the formula to calculate the impact index:

[0022]

[0023] Where YiZ is the influence index, k and w are constants.

[0024] The impact coefficient is related to the abnormal probability of the indicator in the test log. The higher the abnormal probability, the greater the impact coefficient. At the same time, due to the one-way propagation characteristics of the abnormal indicator chain, if the front indicator is abnormal, there is no need to repeat the test of the subsequent indicators. Therefore, the more indicators after the indicator, the greater the impact coefficient.

[0025] S203: Count the number of all codes in the code set BM sum, compare the codes of all indicators under each test case in the use case set with the code set, count the number of identical codes m, obtain the importance index and influence index of the indicators corresponding to the identical codes, substitute them into the formula to calculate the priority index of each test case, and execute the test case CY with the largest priority index; the formula is as follows:

[0026]

[0027] In the formula, YoZ is the priority index, ZhZ n and YiZ n They are the importance index and influence index of the corresponding indicator of the nth same code under the test case.

[0028] In S300, the specific steps are as follows:

[0029] S301. After the execution is completed, obtain the measured values ​​of all indicators under the test case CY, set the state of the corresponding indicator whose measured value is within the target range to normal, and set the state of the remaining indicators to abnormal. Find the abnormal indicator chains containing abnormal state indicators in the fault propagation chain diagram, set the states of all indicators after the abnormal state indicators in these abnormal indicator chains to abnormal; mark all indicators that have been set to the state.

[0030] S302. Retrieve the judgment conditions of each test case in the test case set from the test case standard comparison table, compare and judge the status of all marked indicators with the judgment conditions of each test case, and set the execution status of the corresponding test case according to the judgment result if the judgment conditions are met; mark all test cases for which the execution status has been set.

[0031] The judgment basis includes several indicators, and the judgment result is normal or abnormal. Meeting the judgment condition means that when the status of all indicators in the judgment basis is normal, the judgment result is normal, and the execution status of the corresponding test case is set to normal. Or when one or more of the corresponding indicators in the judgment basis are abnormal, the judgment result is abnormal, and the execution status of the corresponding test case is set to abnormal. In other cases, the judgment condition is not met, and the execution status of the corresponding test case is not set.

[0032] S303. Delete all indicators with the same code as the marked indicator from the indicator set, and delete all marked test cases from the use case set. Determine whether the use case set is an empty set. If not, proceed to step S202 to recalculate the priority index of the remaining test cases and execute them. If yes, delete the top test item in the project set, and determine whether the project set is an empty set. If not, proceed to step S201 to calculate the priority index of each test case in the next test item and execute it. If yes, it means that all test items have been executed and the test is stopped.

[0033] By deleting all indicators in the indicator set that have the same code as the marked indicator, we can avoid the subsequent repeated calculation of the importance index and influence index of the indicator, and at the same time, the priority index of other test cases will not be affected by the indicators with set status. The priority index is closely related to the importance index, influence index and quantity of the indicators with unset status, thereby improving the efficiency of the testing process.

[0034] In S400, whenever the execution status of a test case is set, the code, type, status, measured value and target range of each indicator are packaged as an indicator result, and the execution status and indicator results of the test case are stored in the test log as historical execution records; when the execution is terminated unexpectedly, an automatic warning is sent to the administrator's smart terminal.

[0035] When the marked test case is a completed test case, the code, type, status, measured value and target interval of all indicators under the test case can be obtained and packaged as an indicator result. When the marked test case is not a completed test case, only the code, type, status, measured value and target interval of all corresponding indicators under the satisfied judgment conditions can be obtained and packaged as an indicator result.

[0036] A data analysis and management system for an unattended test system comprises a data acquisition module, an execution planning module, a result evaluation module and a storage early warning module.

[0037] The data acquisition module is used to collect fault propagation chain diagrams, test case status comparison tables, test logs, and test items. The execution planning module is used to calculate the importance index and impact index of each indicator under the test item, as well as the priority index of each test case, and select the test case with the largest priority index for execution. The result evaluation module is used to analyze the execution results of the test case, set the status of the indicator and the execution status of the test case, call the execution planning module to recalculate the priority index of other test cases and execute them, and stop the test until all test items are executed. The storage warning module is used to generate historical execution records and store them in the test log, and issue a warning when the execution is unexpectedly terminated.

[0038] The data collection module includes a project information collection unit, a test log collection unit and a chart information collection unit.

[0039] The project information collection unit is used to collect test projects. The administrator selects p test projects in the solution library and plans the execution order, establishes a project set, and puts the selected test projects into the project set in sequence according to the execution order.

[0040] The test log collection unit is used to collect test logs; test logs refer to the historical execution records of test cases. Each historical execution record includes the execution status and indicator results. The execution status is normal or abnormal. The indicator results include the code, type, status, measured value and target range of each indicator. The status is normal or abnormal.

[0041] The chart information collection unit is used to collect fault propagation chain diagrams and test case status comparison tables. The fault propagation chain diagram includes various types of abnormal indicator chains, which are composed of indicators with different codes and are unidirectional. All indicators under each abnormal indicator chain are of the same type. The test case status comparison table includes the judgment conditions of all test cases. The judgment conditions are used to determine the execution status of the test cases. The judgment conditions include the judgment basis and the judgment result.

[0042] The execution planning module includes a test analysis unit, an indicator analysis unit, and a use case planning unit.

[0043] The test analysis unit is used to divide test cases and indicators.

[0044] Get the top test project CX in the project collection, establish a use case collection, and put all test cases under the test project CX into the use case collection; establish an indicator collection, and put all indicators under the test project CX into the indicator collection.

[0045] The indicator analysis unit is used to calculate the importance index and impact index of the indicator.

[0046] First, establish a coding set, remove duplicate codes of all indicators in the indicator set and put them into the coding set, and divide the number of indicator codes Zbm in the indicator set by the number of all indicators in the indicator set to get the importance index ZhZ. Secondly, count the number of historical execution records containing indicator code Zbm in the test log And the number of historical execution records where the indicator code Zbm corresponds to an abnormal state Finally, count the number of all indicators SLr after the indicator in the abnormal indicator chain containing the coded Zbm indicator e h , substitute into the formula: , calculate the impact index YiZ; where k and w are constants.

[0047] The use case planning unit is used to select test cases for execution.

[0048] Count the number of all codes in the code set BM sum , compare the codes of all indicators under each test case in the use case set with the code set, count the number of identical codes m, obtain the importance index and influence index of the indicators corresponding to the identical codes, and substitute them into the formula: In the above example, the priority index of each test case is calculated, and the test case CY with the largest priority index is executed; where YoZ is the priority index, ZhZ is the priority index, n and YiZ n They are the importance index and influence index of the corresponding indicator of the nth same code under the test case.

[0049] The result evaluation module includes a state setting unit and a progress analysis unit.

[0050] The state setting unit is used to set the execution state of the test case and the state of the indicator.

[0051] When the test case CY is executed, obtain the measured values ​​of all indicators under the test case CY, set the status of the corresponding indicators whose measured values ​​are within the target range to normal, and set the status of the remaining indicators to abnormal. Set the status of all indicators after the abnormal status indicator in each abnormal indicator chain to abnormal, and mark all indicators that have been set. Compare and judge the judgment conditions of each test case with the status of the marked indicator. If the judgment conditions are met, set the execution status of the corresponding test case according to the judgment result. Mark all test cases that have been set to execute.

[0052] The progress analysis unit is used to determine whether to continue execution. Delete all indicators with the same code as the marked indicator in the indicator set, delete all marked test cases in the use case set, and determine whether the use case set is an empty set. If the result is yes, call the indicator analysis unit and the use case planning unit to recalculate the priority index of the remaining test cases and execute them. If the result is yes, delete the top test item in the project set, and determine whether the project set is an empty set. If the result is no, call the execution planning module to calculate the priority index of each test case in the next test item and execute it. If the result is yes, it means that all test items have been executed and the test is stopped.

[0053] When the execution status of each test case is set, the storage warning module packages the code, type, status, measured value and target range of each indicator into an indicator result, and stores it in the test log together with the execution status as a historical execution record; it automatically warns the administrator when the execution is terminated unexpectedly.

[0054] Compared with the prior art, the beneficial effects achieved by the present invention are:

[0055] 1. Accurate execution selection: In this application, the importance index is calculated by the frequency of occurrence of the indicator in the test plan, and the impact index is calculated according to the abnormal probability of the indicator in the test log and the number of subsequent indicators under the abnormal indicator chain, so as to calculate the priority index of each test case. Compared with the mechanical selection of traditional technology, it is more accurate and reliable, and improves the test efficiency.

[0056] 2. Intelligent status setting: In this application, the results of each execution are obtained, the status of other indicators is set through the fault propagation chain diagram, and the status of each test case is set according to the test case status comparison table. Compared with the traditional technology, each execution only sets the status of the test case, which is more intelligent and reduces redundant testing.

[0057] 3. Dynamic order arrangement: In this application, for each execution result, the indicators or test cases with status settings are deleted from the indicator set or use case set, so that the indicators that have not been set to status are calculated each time, and the priority index of the test cases is continuously optimized and adjusted. Compared with the fixed execution order of traditional technologies, it is more dynamic and flexible, and reduces the test time.

[0058] In summary, compared with traditional technologies, the present invention has the advantages of precise execution selection, intelligent state setting and dynamic sequence arrangement, and can improve the test speed. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0060] Figure 1 It is a flow chart of a data analysis management method for an unattended test system of the present invention;

[0061] Figure 2 The present invention is a structural schematic diagram of a data analysis and management system for an unattended test system. DETAILED DESCRIPTION

[0062] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0063] See also Figure 1 The present invention provides a data analysis and management method for an unattended test system, the method comprising the following steps:

[0064] S100, collect fault propagation chain diagram, test case status comparison table and test log, and the administrator selects test items in the solution library according to business needs and plans their execution order.

[0065] S200, obtaining the test cases that need to be executed in the test project, first calculating the importance index and influence index of each indicator under the test case, then calculating the priority index of each test case, and selecting the test case with the largest priority index to execute.

[0066] S300, obtain the execution result of the test case, set the status of the indicator by analyzing the fault propagation chain diagram, set the execution status of the test case according to the test case status comparison table, enter step S200 to recalculate the priority index of other test cases and execute them, and stop the test until all test items are executed.

[0067] S400. When the execution status of the test case is set, the indicator information is packaged into the indicator result and the execution status as a historical execution record and stored in the test log. If the execution is terminated unexpectedly, the administrator is automatically warned.

[0068] In S100, the fault propagation chain diagram includes various types of abnormal indicator chains, which are composed of indicators with different codes and are unidirectionally propagated, and all indicators under each abnormal indicator chain are of the same type. The test case status comparison table includes the judgment conditions of all test cases, which are used to judge the execution status of the test cases, and the judgment conditions include the judgment basis and the judgment result.

[0069] The test log refers to the historical execution record of the test case. Each historical execution record includes the execution status and indicator results. The execution status is normal or abnormal. The indicator results include the code, type, status, measured value and target range of each indicator. The status is normal or abnormal. The administrator refers to the relay protection test scheme administrator. The scheme library contains protection logic verification schemes for different relay protection devices. Each protection logic verification scheme contains different test items. Each test item contains different test cases. Each test case contains different indicators. Each indicator includes code, type and target range. The administrator selects p test items in the corresponding protection logic verification scheme according to business needs and plans the execution order of these test items, establishes a project collection, and puts the selected test items into the project collection in sequence according to the execution order.

[0070] The test item is a test of the protection device to achieve a specific function. The test case is a test of the performance of each component of the protection device to achieve a specific function, and the indicator is a specific parameter test of the performance of each component of the protection device to achieve a specific function. The execution order of the test items is planned by the administrator, and the execution order of each test case under the test item is not required.

[0071] The fault propagation chain diagram is used to describe the different types of fault propagation paths in the unattended test system. It is established by the administrator in advance with reference to the relationship between the relay protection logic. There are several abnormal indicator chains of the same type in the fault propagation chain diagram. The type of each abnormal indicator chain is the same as the type of all indicators under the abnormal indicator chain, including current, voltage, resistance and capacitance. The type of abnormal indicator chain is the same concept as the type of indicator.

[0072] The number of indicators under the abnormal indicator chain is related to the relay protection logic. All indicators exist in the fault propagation chain diagram and each indicator can only appear in one of the abnormal indicator chains. If one indicator in the abnormal indicator chain is abnormal, all indicators after it will inevitably be abnormal. The abnormal indicator chain is also divided based on this feature.

[0073] In S200, the specific steps are as follows:

[0074] S201. Obtain the top test project CX in the project set, establish a use case set, and put all test cases under the test project CX into the use case set; establish an indicator set, and put all indicators under the test project CX into the indicator set.

[0075] S202: Establish a coding set, obtain the codes of all indicators in the indicator set, remove duplicate codes and put them into the coding set in sequence, and calculate the importance index and influence index of the indicator corresponding to each code in the coding set. The steps are as follows:

[0076] S202-1. The number of statistical indicator codes Zbm in the indicator set ZJH Zbm , and the number of all indicators in the indicator set ZJH sum , ZJH Zbm Divide by ZJH sum Get the importance index ZhZ.

[0077] There may be indicators with the same code in different test cases, so there are also indicators with the same code in the indicator set. The importance index is related to the frequency of the indicator in the indicator set. The higher the frequency, the greater the importance index.

[0078] S202-2. Retrieve and count the number of historical execution records LZX containing the indicator code Zbm in the test log s Z u b m m , and analyze the number of historical execution records where the indicator code Zbm corresponds to an abnormal state

[0079] S202-3. Find the abnormal indicator chain containing the indicator coded as Zbm in the fault propagation chain diagram Statistical anomaly indicator chain The number of all indicators after the corresponding indicator in the indicator code Zbm Substitute into the formula to calculate the impact index:

[0080]

[0081] Where YiZ is the influence index, k and w are constants.

[0082] The impact coefficient is related to the abnormal probability of the indicator in the test log. The higher the abnormal probability, the greater the impact coefficient. At the same time, due to the one-way propagation characteristics of the abnormal indicator chain, if the front indicator is abnormal, there is no need to repeat the test of the subsequent indicators. Therefore, the more indicators after the indicator, the greater the impact coefficient.

[0083] S203: Count the number of all codes in the code set BM sum , compare the codes of all indicators under each test case in the use case set with the code set, count the number of identical codes m, obtain the importance index and influence index of the indicators corresponding to the identical codes, substitute them into the formula to calculate the priority index of each test case, and execute the test case CY with the largest priority index; the formula is as follows:

[0084]

[0085] In the formula, YoZ is the priority index, ZhZ n and YiZ n They are the importance index and influence index of the corresponding indicator of the nth same code under the test case.

[0086] In S300, the specific steps are as follows:

[0087] S301. After the execution is completed, obtain the measured values ​​of all indicators under the test case CY, set the state of the corresponding indicator whose measured value is within the target range to normal, and set the state of the remaining indicators to abnormal. Find the abnormal indicator chains containing abnormal state indicators in the fault propagation chain diagram, set the states of all indicators after the abnormal state indicators in these abnormal indicator chains to abnormal; mark all indicators that have been set to the state.

[0088] S302. Retrieve the judgment conditions of each test case in the test case set from the test case standard comparison table, compare and judge the status of all marked indicators with the judgment conditions of each test case, and set the execution status of the corresponding test case according to the judgment result if the judgment conditions are met; mark all test cases for which the execution status has been set.

[0089] The judgment basis includes several indicators, and the judgment result is normal or abnormal. Meeting the judgment condition means that when the status of all indicators in the judgment basis is normal, the judgment result is normal, and the execution status of the corresponding test case is set to normal. Or when one or more of the corresponding indicators in the judgment basis are abnormal, the judgment result is abnormal, and the execution status of the corresponding test case is set to abnormal. In other cases, the judgment condition is not met, and the execution status of the corresponding test case is not set.

[0090] S303. Delete all indicators with the same code as the marked indicator from the indicator set, and delete all marked test cases from the use case set. Determine whether the use case set is an empty set. If not, proceed to step S202 to recalculate the priority index of the remaining test cases and execute them. If yes, delete the top test item in the project set, and determine whether the project set is an empty set. If not, proceed to step S201 to calculate the priority index of each test case in the next test item and execute it. If yes, it means that all test items have been executed and the test is stopped.

[0091] By deleting all indicators in the indicator set that have the same code as the marked indicator, we can avoid the subsequent repeated calculation of the importance index and influence index of the indicator, and at the same time, the priority index of other test cases will not be affected by the indicators with set status. The priority index is closely related to the importance index, influence index and quantity of the indicators with unset status, thereby improving the efficiency of the testing process.

[0092] In S400, whenever the execution status of a test case is set, the code, type, status, measured value and target range of each indicator are packaged as an indicator result, and the execution status and indicator results of the test case are stored in the test log as historical execution records; when the execution is terminated unexpectedly, an automatic warning is sent to the administrator's smart terminal.

[0093] When the marked test case is a completed test case, the code, type, status, measured value and target interval of all indicators under the test case can be obtained and packaged as an indicator result. When the marked test case is not a completed test case, only the code, type, status, measured value and target interval of all corresponding indicators under the satisfied judgment conditions can be obtained and packaged as an indicator result.

[0094] See also Figure 2 The present invention provides a data analysis and management system for an unattended test system, the system comprising a data acquisition module, an execution planning module, a result evaluation module and a storage warning module.

[0095] The data acquisition module is used to collect fault propagation chain diagrams, test case status comparison tables, test logs, and test items. The execution planning module is used to calculate the importance index and impact index of each indicator under the test item, as well as the priority index of each test case, and select the test case with the largest priority index for execution. The result evaluation module is used to analyze the execution results of the test case, set the status of the indicator and the execution status of the test case, call the execution planning module to recalculate the priority index of other test cases and execute them, and stop the test until all test items are executed. The storage warning module is used to generate historical execution records and store them in the test log, and issue a warning when the execution is unexpectedly terminated.

[0096] The data collection module includes a project information collection unit, a test log collection unit and a chart information collection unit.

[0097] The project information collection unit is used to collect test projects. The administrator selects p test projects in the solution library and plans the execution order, establishes a project set, and puts the selected test projects into the project set in sequence according to the execution order.

[0098] The test log collection unit is used to collect test logs; test logs refer to the historical execution records of test cases. Each historical execution record includes the execution status and indicator results. The execution status is normal or abnormal. The indicator results include the code, type, status, measured value and target range of each indicator. The status is normal or abnormal.

[0099] The chart information collection unit is used to collect fault propagation chain diagrams and test case status comparison tables. The fault propagation chain diagram includes various types of abnormal indicator chains, which are composed of indicators with different codes and are unidirectional. All indicators under each abnormal indicator chain are of the same type. The test case status comparison table includes the judgment conditions of all test cases. The judgment conditions are used to determine the execution status of the test cases. The judgment conditions include the judgment basis and the judgment result.

[0100] The execution planning module includes a test analysis unit, an indicator analysis unit, and a use case planning unit.

[0101] The test analysis unit is used to divide test cases and indicators.

[0102] Get the top test project CX in the project collection, establish a use case collection, and put all test cases under the test project CX into the use case collection; establish an indicator collection, and put all indicators under the test project CX into the indicator collection.

[0103] The indicator analysis unit is used to calculate the importance index and impact index of the indicator.

[0104] First, establish a coding set, remove duplicate codes of all indicators in the indicator set and put them into the coding set, and divide the number of indicator codes Zbm in the indicator set by the number of all indicators in the indicator set to get the importance index ZhZ. Secondly, count the number of historical execution records containing indicator code Zbm in the test log And the number of historical execution records where the indicator code Zbm corresponds to an abnormal state Finally, count the number of all indicators after the indicator in the abnormal indicator chain containing the coded Zbm indicator Substituting into the formula: , calculate the impact index YiZ; where k and w are constants.

[0105] The use case planning unit is used to select test cases for execution.

[0106] Count the number of all codes in the code set BM sum , compare the codes of all indicators under each test case in the use case set with the code set, count the number of identical codes m, obtain the importance index and influence index of the indicators corresponding to the identical codes, and substitute them into the formula: In the above example, the priority index of each test case is calculated, and the test case CY with the largest priority index is executed; where YoZ is the priority index, ZhZ is the priority index, n and YiZ n They are the importance index and influence index of the corresponding indicator of the nth same code under the test case.

[0107] The result evaluation module includes a state setting unit and a progress analysis unit.

[0108] The state setting unit is used to set the execution state of the test case and the state of the indicator.

[0109] When the test case CY is executed, obtain the measured values ​​of all indicators under the test case CY, set the status of the corresponding indicators whose measured values ​​are within the target range to normal, and set the status of the remaining indicators to abnormal. Set the status of all indicators after the abnormal status indicator in each abnormal indicator chain to abnormal, and mark all indicators that have been set. Compare and judge the judgment conditions of each test case with the status of the marked indicator. If the judgment conditions are met, set the execution status of the corresponding test case according to the judgment result. Mark all test cases that have been set to execute.

[0110] The progress analysis unit is used to determine whether to continue execution. Delete all indicators with the same code as the marked indicator in the indicator set, delete all marked test cases in the use case set, and determine whether the use case set is an empty set. If the result is yes, call the indicator analysis unit and the use case planning unit to recalculate the priority index of the remaining test cases and execute them. If the result is yes, delete the top test item in the project set, and determine whether the project set is an empty set. If the result is no, call the execution planning module to calculate the priority index of each test case in the next test item and execute it. If the result is yes, it means that all test items have been executed and the test is stopped.

[0111] When the execution status of each test case is set, the storage warning module packages the code, type, status, measured value and target range of each indicator into an indicator result, and stores it in the test log together with the execution status as a historical execution record; it automatically warns the administrator when the execution is terminated unexpectedly.

[0112] Embodiment 1:

[0113] Assume that there are two indicators A1 and A2 in a test case. The test log contains 20 historical execution records of the A1 indicator, of which 4 are abnormal. The test log contains 50 historical execution records of the A2 indicator, of which 15 are abnormal. The number of all indicators after the A1 indicator on the abnormal indicator chain in the fault propagation chain is 5, and the number of all indicators after the A2 indicator on the abnormal indicator chain is 8.

[0114] When k is 1 and w is 10, substitute the formula to calculate the impact index:

[0115] A1 indicator impact index:

[0116] A2 indicator impact index:

[0117] The impact index of the A1 indicator is 0.72; the impact index of the A2 indicator is 1.17.

[0118] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0119] Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein by equivalents. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A data analysis and management method for an unattended test system, characterized in that: The method comprises the following steps: S100, collect fault propagation chain diagram, test case status comparison table and test log, and the administrator selects test items in the solution library according to business needs and plans their execution order; S200, obtaining the test cases to be executed in the test project, first calculating the importance index and influence index of each indicator under the test case, then calculating the priority index of each test case, and selecting the test case with the largest priority index for execution; in S200, the specific steps are as follows: S201, obtaining the top test project CX in the project set, establishing a use case set, and putting all test cases under the test project CX into the use case set; establishing an indicator set, and putting all indicators under the test project CX into the indicator set; S202: Establish a coding set, obtain the codes of all indicators in the indicator set, remove duplicate codes and put them into the coding set in sequence, and calculate the importance index and influence index of the indicator corresponding to each code in the coding set. The steps are as follows: S202-1. The number of statistical indicator codes Zbm in the indicator set ZJH Zbm , and the number of all indicators in the indicator set ZJH sum , ZJH Zbm Divide by ZJH sum Get the important index ZhZ; S202-2. Retrieve and count the number of historical execution records containing indicator code Zbm in the test log And analyze the number of historical execution records where the indicator code Zbm corresponds to an abnormal state S202-3. Find the abnormal indicator chain containing the indicator coded as Zbm in the fault propagation chain diagram Statistical anomaly indicator chain The number of all indicators after the corresponding indicator in the indicator code Zbm Substitute into the formula to calculate the impact index: In the formula, YiZ is the influence index, k and w are constants; S203: Count the number of all codes in the code set BM sum , compare the codes of all indicators under each test case in the use case set with the code set, count the number of identical codes m, obtain the importance index and influence index of the indicators corresponding to the identical codes, substitute them into the formula to calculate the priority index of each test case, and execute the test case CY with the largest priority index; the formula is as follows: In the formula, YoZ is the priority index, ZhZ n and YiZ n They are the importance index and influence index of the corresponding indicator of the nth same code under the test case respectively; S300, obtaining the execution result of the test case, setting the status of the indicator by analyzing the fault propagation chain diagram, setting the execution status of the test case according to the test case status comparison table, entering step S200 to recalculate the priority index of other test cases and execute them, and stopping the test until all test items are executed; S400. When the execution status of the test case is set, the indicator information is packaged into the indicator result and the execution status as a historical execution record and stored in the test log. If the execution is terminated unexpectedly, the administrator is automatically warned.

2. The data analysis and management method for an unattended test system according to claim 1, characterized in that: In S100, the fault propagation chain diagram includes various types of abnormal indicator chains, which are composed of indicators with different codes and are unidirectionally propagated, and the types of all indicators under each abnormal indicator chain are the same; the test case status comparison table includes the judgment conditions of all test cases, and the judgment conditions are used to determine the execution status of the test cases, and the judgment conditions include the judgment basis and the judgment results; the test log refers to the historical execution record of the test case, and each historical execution record includes the execution status and the indicator result, and the execution status is normal or abnormal, and the indicator result includes the code, type, status, measured value and target interval of each indicator, and the status is normal or abnormal; the scheme library includes protection logic verification schemes for different relay protection devices, each protection logic verification scheme includes different test items, each test item includes different test cases, each test case includes different indicators, and each indicator includes the code, type and target interval; The administrator selects p test items in the corresponding protection logic verification scheme according to business needs and plans the execution order of these test items, establishes a project set, and puts the selected test items into the project set in sequence according to the execution order.

3. The data analysis and management method for an unattended test system according to claim 2, characterized in that: In S300, the specific steps are as follows: S301, after the execution is completed, the measured values ​​of all indicators under the test case CY are obtained, and the status of the corresponding indicators whose measured values ​​are within the target range is set as normal, and the status of the remaining indicators is set as abnormal; Find the abnormal indicator chains containing abnormal status indicators in the fault propagation chain diagram, set the status of all indicators after the abnormal status indicators in these abnormal indicator chains as abnormal; mark all indicators whose status has been set; S302, respectively search the judgment condition of each test case in the test case set in the test case standard comparison table, compare and judge the status of all marking indicators with the judgment condition of each test case, and set the execution status of the corresponding test case according to the judgment result if the judgment condition is met; mark all test cases for which the execution status has been set; S303, delete all indicators with the same code as the marked indicator in the indicator set, and delete all marked test cases in the use case set; determine whether the use case set is an empty set, and if the result is not, proceed to step S202, recalculate the priority index of the remaining test cases and execute them; If the result is yes, the top test item in the item set is deleted, and it is determined whether the item set is an empty set. If the result is no, the process proceeds to step S201 to calculate the priority index of each test case in the next test item and execute the result. If the result is yes, it means that all test items have been executed and the test is stopped.

4. The data analysis and management method for an unattended test system according to claim 3, characterized in that: In S400, whenever the execution status of a test case is set, the code, type, status, measured value and target interval of each indicator are packaged as an indicator result, and the execution status and indicator result of the test case are stored in the test log as a historical execution record; When the execution is terminated unexpectedly, an alert is automatically sent to the administrator's smart terminal.

5. A data analysis and management system for an unattended test system, characterized in that: The system includes a data acquisition module, an execution planning module, a result evaluation module and a storage warning module; The data collection module is used to collect fault propagation chain diagrams, test case status comparison tables, test logs and test items; the execution planning module is used to calculate the importance index and impact index of each indicator under the test item, as well as the priority index of each test case, and select the test case with the largest priority index for execution. The execution planning module includes a test analysis unit, an indicator analysis unit and a case planning unit; The test analysis unit is used to divide test cases and indicators; Get the top test project CX in the project set, establish a use case set, and put all test cases under the test project CX into the use case set; establish an indicator set, and put all indicators under the test project CX into the indicator set; The indicator analysis unit is used to calculate the importance index and impact index of the indicator; First, establish a coding set, remove duplicate codes of all indicators in the indicator set and put them into the coding set, divide the number of indicator codes Zbm in the indicator set by the number of all indicators in the indicator set to get the importance index ZhZ; secondly, count the number of historical execution records containing indicator code Zbm in the test log And the number of historical execution records where the indicator code Zbm corresponds to an abnormal state Finally, count the number of all indicators after the indicator in the abnormal indicator chain containing the coded Zbm indicator Substituting into the formula: , calculate the impact index YiZ; where k and w are constants; The use case planning unit is used to select test cases for execution; Count the number of all codes in the code set BM sum , compare the codes of all indicators under each test case in the use case set with the code set, count the number of identical codes m, obtain the importance index and influence index of the indicators corresponding to the identical codes, and substitute them into the formula: In the above example, the priority index of each test case is calculated, and the test case CY with the largest priority index is executed; where YoZ is the priority index, ZhZ is the priority index, n and YiZ n They are the importance index and influence index of the corresponding indicator of the nth same code under the test case respectively; The result evaluation module is used to analyze the execution results of the test cases, set the status of indicators and the execution status of the test cases, call the execution planning module to recalculate the priority index of other test cases and execute them until all test items are executed and the test is stopped; the storage warning module is used to generate historical execution records and store them in the test log, and issue a warning when the execution is terminated unexpectedly.

6. A data analysis and management system for an unattended test system according to claim 5, characterized in that: The data collection module includes a project information collection unit, a test log collection unit and a chart information collection unit; The project information collection unit is used to collect test projects; the administrator selects p test projects in the solution library and plans the execution order, establishes a project set, and puts the selected test projects into the project set in sequence according to the execution order; The test log collection unit is used to collect test logs; test logs refer to the historical execution records of test cases. Each historical execution record includes the execution status and indicator results. The execution status is normal or abnormal. The indicator results include the code, type, status, measured value and target range of each indicator. The status is normal or abnormal. The chart information collection unit is used to collect fault propagation chain diagrams and test case status comparison tables; the fault propagation chain diagrams include various types of abnormal indicator chains, the abnormal indicator chains are composed of indicators with different codes and are unidirectionally propagated, and the types of all indicators under each abnormal indicator chain are the same; the test case status comparison table includes the judgment conditions of all test cases, the judgment conditions are used to determine the execution status of the test cases, and the judgment conditions include the judgment basis and the judgment result.

7. The data analysis and management system for an unattended test system according to claim 6, characterized in that: The result evaluation module includes a status setting unit and a progress analysis unit; The state setting unit is used to set the execution state of the test case and the state of the indicator; When the test case CY is executed, the measured values ​​of all indicators under the test case CY are obtained, and the status of the corresponding indicators whose measured values ​​are within the target range is set as normal, and the status of the remaining indicators is set as abnormal; Set the status of all indicators after the abnormal status indicator in each abnormal indicator chain as abnormal, and mark all indicators that have been set; compare the judgment condition of each test case with the status of the marked indicator, and set the execution status of the corresponding test case according to the judgment result if the judgment condition is met; mark all test cases that have been set to execute; The progress analysis unit is used to determine whether to continue execution; delete all indicators with the same code as the marked indicator in the indicator set, delete all marked test cases in the use case set, and determine whether the use case set is an empty set. If the result is not, call the indicator analysis unit and the use case planning unit to recalculate the priority index of the remaining test cases and execute them; If the result is yes, delete the top test item in the item set, and determine whether the item set is an empty set. If the result is no, call the execution planning module to calculate the priority index of each test case in the next test item and execute it; If the result is yes, it means that all test items have been executed and the test is stopped.

8. The data analysis and management system for an unattended test system according to claim 7, characterized in that: When the execution status of each test case is set, the storage warning module packages the code, type, status, measured value and target interval of each indicator into an indicator result, and stores it in the test log as a historical execution record together with the execution status; Automatically alert administrators when execution terminates unexpectedly.