CN112306877A - Power system fault operation and maintenance method and system - Google Patents
Power system fault operation and maintenance method and system Download PDFInfo
- Publication number
- CN112306877A CN112306877A CN202011195977.5A CN202011195977A CN112306877A CN 112306877 A CN112306877 A CN 112306877A CN 202011195977 A CN202011195977 A CN 202011195977A CN 112306877 A CN112306877 A CN 112306877A
- Authority
- CN
- China
- Prior art keywords
- fault
- analysis
- test
- software
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000012423 maintenance Methods 0.000 title claims abstract description 20
- 238000012360 testing method Methods 0.000 claims abstract description 85
- 238000004458 analytical method Methods 0.000 claims abstract description 70
- 238000004590 computer program Methods 0.000 claims description 5
- 230000006870 function Effects 0.000 abstract description 9
- 238000007726 management method Methods 0.000 description 8
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000012216 screening Methods 0.000 description 5
- 238000013100 final test Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000005070 sampling Methods 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Abstract
The present disclosure provides a method and a system for operating and maintaining a fault of a power system, including: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software; selecting analysis software with different versions from the analysis version library to analyze fault files in test cases in the test case library to obtain an analysis result of each fault file; and comparing the analysis result of each fault file with the standard test report of the fault file corresponding to the fault database to obtain the test result of the corresponding analysis software. The method comprises the steps of establishing a fault library and an analysis program version library, classifying different faults, analyzing various fault data by using analysis software, comparing obtained analysis reports, and judging whether the functions of new analysis software are complete. The method and the device can improve the checking efficiency of the fault operation and maintenance management and the analysis software function.
Description
Technical Field
The disclosure belongs to the technical field of power system software monitoring, and particularly relates to a power system fault operation and maintenance method and system.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
The method comprises the steps that a plurality of operation data can be generated in an electric power system, if the operation data can reflect the fault situation at that time, a computer is required to write corresponding software for analyzing the operation data, however, with the diversification of the operation data change, the corresponding software, namely an analysis program version library, can be changed frequently, but the inventor finds that the processed problem is easy to ignore in the modification process, the problem B is changed, and the problem A is also released, so that the analysis software in the analysis program version library cannot meet the requirement of the actual fault analysis which changes continuously.
Disclosure of Invention
In order to overcome the defects of the prior art, the present disclosure provides a power system fault operation and maintenance method, so that finally, analysis software obtains a fault analysis result by analyzing a waveform file uploaded when a fault occurs.
In order to achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
in a first aspect, a power system fault operation and maintenance method is disclosed, which includes:
establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
selecting analysis software with different versions from the analysis version library to analyze fault files in test cases in the test case library to obtain an analysis result of each fault file;
and comparing the analysis result of each fault file with the standard test report of the fault file corresponding to the fault database to obtain the test result of the corresponding analysis software.
According to a further technical scheme, the fault database comprises various types of fault data, including the region to which the fault device belongs, the fault type, the fault phase and the weather condition when the fault occurs.
In a further technical solution, the establishing and maintaining of the analysis version library includes: and if the case library for the fault test to be analyzed does not exist, the case library is a new fault, and the analysis version library is updated.
According to the further technical scheme, when the analysis result is failed, the analysis software of the corresponding version is changed and processed in time, the failure data can be partially changed along with the upgrading of the corresponding device and the difference of device manufacturers, and the analysis software is upgraded in time.
According to the further technical scheme, after the analysis result of each fault file is obtained, whether the analysis software meets the use requirement or not is judged by comparing the test result with the standard result, and on the premise of ensuring that the determined fault result is not changed, other fault information in the assumption is obtained, so that the software is ensured to be upgraded successfully.
According to the further technical scheme, when the test result meets the requirement, the test result is used as a new test result corresponding to the fault data, and the new test result is used for comparing the results of the new analysis software in the later period and inquiring the analysis result during fault maintenance.
In a further technical scheme, a parameter file required by analysis software in analyzing a waveform file consists of two parts: one part is a recording file recorded by the device when the fault occurs, the other part is a model file matched with the fault device, and the analysis software needs to analyze the waveform file through the model file so as to obtain an analysis result.
According to a further technical scheme, the fault database performs unified storage management on the faults according to the phase, the type, the line and the region to which the faults belong, so that the national fault distribution condition is obtained.
According to the further technical scheme, when a test case library required by test software is established, fault files under one or more different conditions are analyzed in a unified mode, when faults are selected, screening is needed according to the phase, the fault type and the region to which the faults belong, and when the faults under severe weather need to be analyzed, screening is needed under the condition of specific weather.
According to the further technical scheme, in the analysis version base, the analysis software of each version records corresponding relevant characteristics, sequence numbers and creation time, so that query is facilitated, each version base needs to upload the corresponding analysis program, and the analysis program file can be updated and maintained in the process of maintaining the analysis version base.
In a second aspect, a power system fault operation and maintenance system is disclosed, which includes:
a library building module configured to: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
an analysis module configured to: selecting analysis software with different versions from the analysis version library to analyze fault files in test cases in the test case library to obtain an analysis result of each fault file;
a comparison module configured to: and comparing the analysis result of each fault file with the standard test report of the fault file corresponding to the fault database to obtain the test result of the corresponding analysis software.
The above one or more technical solutions have the following beneficial effects:
the technical scheme is that the operation and maintenance management tool for fault maintenance and analysis management in the power system can obtain the fault condition when a fault occurs by analyzing the operation data of the power system, corresponding analysis software also frequently performs version iteration along with the improvement of the technology and the diversification of the operation data, the problem that the modification is possible to occur in the version iteration process is reoccurred, different faults are classified by establishing a fault library and an analysis program version library, various fault data are analyzed by using the analysis software, and the obtained analysis report is compared to judge whether the function of new analysis software is complete. The method and the device can improve the checking efficiency of the fault operation and maintenance management and the analysis software function.
Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure and are not to limit the disclosure.
Fig. 1 is a flow chart of an embodiment of the disclosure.
Detailed Description
It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments according to the present disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.
The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
Example one
The embodiment discloses a power system fault operation and maintenance method, which comprises the steps of establishing a fault library, analyzing all problems in the fault library by using software (how many test results corresponding to how many test items are used by one test case), obtaining N results, aggregating the results and classifying the results, storing the results in a specified mysql database, creating a new analysis program version library during subsequent calling, analyzing the test function with the corresponding test case combination to obtain a test analysis result, and then automatically analyzing whether the test analysis result is matched with the previous analysis result or not when the analysis program version library is modified.
Specifically, the analysis software obtains a fault analysis result by analyzing a waveform file uploaded when the fault occurs. The parameter file required by software when analyzing the waveform file consists of two parts: one part is a wave recording file recorded by the device when a fault occurs, the wave recording file consists of three files, namely hdr, dat and cfg, the three files are slightly different according to different recorded information of a standard version by referring to a table, and the hdr file records basic description of the fault and comprises information such as first wave head time, device state and communication state; recording the used standard version, recording data of all lines on the device and sampling frequency by the dat file; the cfg file comprises the name of each line on the device and the starting time of wave recording; dmf, the analysis software needs to parse the waveform file through the dmf file to obtain the analysis result.
The method comprises the steps of establishing a fault library by counting historical recording data, performing unified storage management on faults according to phase types, lines and regions to which the faults belong to obtain national fault distribution conditions, performing unified analysis on fault files under one or more different conditions in order to test the performance of analysis software when establishing a test case, screening according to the phase types, the fault types and the regions to which the faults belong when selecting the faults, and screening according to specific weather conditions when analyzing the faults under severe weather.
Recording the analysis software of each version at present, and establishing a software analysis program version library. The analysis software of each version records corresponding related characteristics (mainly comprising version number, time, serial number and private description of the analysis software of the version), serial number and creation time, so that developers can conveniently inquire. Each version library needs to upload the corresponding analysis program, and the analysis program file can be updated and maintained in the process of maintaining the analysis program version libraries.
Analyzing the same fault data by using different versions of analysis software to obtain a new analysis result, and comparing the analysis result with a standard result to obtain a test report of the tested software.
By establishing a fault library and an analysis program version library, corresponding test cases can be established according to different test requirements. The test case library consists of two parts: and selecting a corresponding fault file from the fault information base and selecting an analysis program from the analysis program version base. Test cases are divided into two categories: single ended test cases and double ended test cases. The single-ended test case needs to select the single-ended case when configuring basic information, the matched fault information comprises all fault recording files, the double-ended test case needs to select the double-ended case when configuring the basic information, the matched fault is a double-ended line fault, and the double-ended fault has fault files of a local device and an opposite device and is mainly used for fault location analysis. According to different test contents of test cases of analysis software, a fault library meeting conditions, such as fault data in thunderstorm weather or fault data of a certain type in a certain area, can be established through screening, in order to test the analysis results of the analysis software on various fault files, a plurality of test cases need to be established in a targeted manner, and a final test report is generated through unified testing.
After the use case type and the specific fault data are selected, an analysis program to be tested is selected. The number of the analysis program reflects the generation time and the specific version of the program, so that a tester can conveniently select the program, and an analysis program version library of a corresponding version needs to be created and uploaded to the analysis program before testing. One test case can select one or more analysis programs, and test results are not influenced mutually. Besides establishing a new test case, the established test case can be selected, the configuration of a fault library is not required to be changed, and only the version of the analysis program version library to be tested needs to be added to the analysis program version library part.
After the test case is generated, a test report is generated through a test program. The test report is obtained by comparing the test result obtained by the analysis of the test software with the standard fault analysis result and judging whether the analysis function of the tested program is complete or not by comparing different data obtained by the analysis, so that the determined analysis function can be at least ensured not to be lost. And if no corresponding standard file exists, the test result is used as the standard file and is pointed out in the test report, and finally the final test report of the tested analysis software is obtained.
There are three cases of comparing test procedure results with standard results: one is that the analysis results are completely consistent, in which case the newly generated test report will automatically become the standard analysis report of the corresponding fault; the second situation is that the number of the faults of the analysis report is more than that of the standard report, at the moment, the power engineering personnel is required to analyze the newly appeared faults by combining with the operation data, and when the fault information is determined to be correct, the fault report is manually set as a new standard detection report of the analysis software of the series, and meanwhile, the version characteristic description of the corresponding analysis program is updated; the last situation is that when the number of faults in the analysis report is less than the standard test result or the fault result does not meet the actual situation of the corresponding fault data, the analysis software of the corresponding version needs to be checked, the problem of the software is found out according to the actual situation of the analysis, developers are assisted to quickly process the problem, and the main function of assisting the management and analysis software is achieved.
After the software test is completed, the test result of each software test is classified according to the test time, the number of the test software and the version of the test software, all test records of the analysis software with specific version can be quickly inquired through the test report inquiry function, and the modification and update records of the corresponding analysis program and the difference between programs with other versions in the series can be intuitively reflected. Meanwhile, in the process of checking the test result, the test result of a certain fault can be manually set as the standard analysis result of the corresponding analysis program.
In the aspect of fault management, the current fault operation and maintenance management system establishes a regional/field station/equipment/line multi-stage fault data management mode by referring to the use habits of field operation and maintenance personnel, and meets the practical requirement of power engineering software design.
Example two
The present embodiment is directed to a computing device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the specific steps of the method.
EXAMPLE III
An object of the present embodiment is to provide a computer-readable storage medium.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out specific steps of the above-mentioned method.
Example four
The purpose of this embodiment is to provide a power system trouble operation and maintenance system, realize based on the server, include:
a library building module configured to: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
an analysis module configured to: selecting analysis software with different versions from the analysis version library to analyze fault files in test cases in the test case library to obtain an analysis result of each fault file;
a comparison module configured to: and comparing the analysis result of each fault file with the standard test report of the fault file corresponding to the fault database to obtain the test result of the corresponding analysis software.
The steps involved in the apparatuses of the above second, third and fourth embodiments correspond to the first embodiment of the method, and the detailed description thereof can be found in the relevant description of the first embodiment. The term "computer-readable storage medium" should be taken to include a single medium or multiple media containing one or more sets of instructions; it should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor and that cause the processor to perform any of the methods of the present disclosure.
Those skilled in the art will appreciate that the modules or steps of the present disclosure described above can be implemented using general purpose computer means, or alternatively, they can be implemented using program code executable by computing means, whereby the modules or steps may be stored in memory means for execution by the computing means, or separately fabricated into individual integrated circuit modules, or multiple modules or steps thereof may be fabricated into a single integrated circuit module. The present disclosure is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure, and various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Although the present disclosure has been described with reference to specific embodiments, it should be understood that the scope of the present disclosure is not limited thereto, and those skilled in the art will appreciate that various modifications and changes can be made without departing from the spirit and scope of the present disclosure.
Claims (10)
1. A power system fault operation and maintenance method is characterized by comprising the following steps:
establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
selecting analysis software with different versions from the analysis version library to analyze fault files in test cases in the test case library to obtain an analysis result of each fault file;
and comparing the analysis result of each fault file with the standard test report of the fault file corresponding to the fault database to obtain the test result of the corresponding analysis software.
2. The method as claimed in claim 1, wherein the fault database comprises various types of fault data including a region to which the fault device belongs, a fault type, a fault phase, and a weather condition when the fault occurs.
3. The method according to claim 1, wherein the creating and maintaining of the analysis version library comprises: if the fault to be analyzed does not exist in the test case library, the fault is a new fault, and the analysis version library is updated;
when the analysis result is failed, the analysis software of the corresponding version is changed in time, the failure data can be partially changed along with the upgrading of the corresponding device and the difference of device manufacturers, and the analysis software is upgraded in time.
4. The method for operation and maintenance of faults of an electric power system as claimed in claim 1, wherein after the analysis result of each fault file is obtained, whether the analysis software meets the use requirement is judged by comparing the test result with the standard result, and on the premise of ensuring that the determined fault result is not changed, other fault information in the assumption is obtained to ensure the success of software upgrade;
and when the test result meets the requirement, the test result is used as a new test result corresponding to the fault data for the result comparison of the new analysis software in the later period and the analysis result query in the fault maintenance.
5. The method as claimed in claim 1, wherein the parameter file required by the analysis software in analyzing the waveform file is composed of two parts: one part is a wave recording file recorded by the device when a fault occurs, the other part is a model file matched with the fault device, and analysis software needs to analyze the waveform file through the model file so as to obtain an analysis result;
and the fault database performs unified storage management on the faults according to the phase, the type, the line and the region to which the faults belong to obtain the national fault distribution condition.
6. The method as claimed in claim 1, wherein when the test case library required by the test software is established, the fault files under one or more different conditions are analyzed in a unified manner, when the fault is selected, the fault is screened according to the phase, the fault type and the region to which the fault belongs, and when the fault under the bad weather is analyzed, the fault is screened according to the condition of specific weather.
7. The method as claimed in claim 1, wherein the analysis version library includes the relevant features, sequence numbers and creation time recorded in the analysis software of each version, so as to facilitate query, and each version library needs to upload the corresponding analysis program, so that the analysis program file can be updated and maintained during the maintenance of the analysis version library.
8. A power system fault operation and maintenance system is characterized by comprising:
a library building module configured to: establishing a tested fault database and an analysis version library for managing different versions of analysis software, and establishing a test case library required by the test software;
an analysis module configured to: selecting analysis software with different versions from the analysis version library to analyze fault files in test cases in the test case library to obtain an analysis result of each fault file;
a comparison module configured to: and comparing the analysis result of each fault file with the standard test report of the fault file corresponding to the fault database to obtain the test result of the corresponding analysis software.
9. A computing device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method of any of claims 1-7 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011195977.5A CN112306877B (en) | 2020-10-30 | 2020-10-30 | Power system fault operation and maintenance method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011195977.5A CN112306877B (en) | 2020-10-30 | 2020-10-30 | Power system fault operation and maintenance method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112306877A true CN112306877A (en) | 2021-02-02 |
| CN112306877B CN112306877B (en) | 2024-02-20 |
Family
ID=74333222
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011195977.5A Active CN112306877B (en) | 2020-10-30 | 2020-10-30 | Power system fault operation and maintenance method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112306877B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113011606A (en) * | 2021-01-30 | 2021-06-22 | 河南帅臣停车设备科技有限公司 | Operation and maintenance management method and system for mechanical parking equipment |
| CN113051582A (en) * | 2021-04-28 | 2021-06-29 | 重庆电子工程职业学院 | Computer software technology development and debugging system |
| CN113626288A (en) * | 2021-08-12 | 2021-11-09 | 杭州朗和科技有限公司 | Fault processing method, system, device, storage medium and electronic equipment |
| CN117130945A (en) * | 2023-10-26 | 2023-11-28 | 中国证券登记结算有限责任公司 | Test method and device |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651034B1 (en) * | 1999-10-28 | 2003-11-18 | General Electric Company | Apparatus and method for performance and fault data analysis |
| CN101014955A (en) * | 2004-10-01 | 2007-08-08 | 明导公司 | Feature failure correlation |
| US20100287535A1 (en) * | 2009-05-08 | 2010-11-11 | Electronics And Telecommunications Research Institute | System and method for testing software reliability using fault injection |
| CN102707195A (en) * | 2012-06-01 | 2012-10-03 | 江苏省电力公司检修分公司 | Oscilloscope fault analysis platform and establishment method thereof |
| CN103853765A (en) * | 2012-12-04 | 2014-06-11 | 天津市电力公司 | Method for comparing waveform features of power system faults |
| CN108804301A (en) * | 2017-04-27 | 2018-11-13 | 株洲中车时代电气股份有限公司 | A kind of train control system software testing system and method based on E & FR data |
| CN109813999A (en) * | 2019-01-22 | 2019-05-28 | 山东大学 | A kind of Fault Diagnosis of Distribution Network algorithm automatically testing platform, method and application |
-
2020
- 2020-10-30 CN CN202011195977.5A patent/CN112306877B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651034B1 (en) * | 1999-10-28 | 2003-11-18 | General Electric Company | Apparatus and method for performance and fault data analysis |
| CN101014955A (en) * | 2004-10-01 | 2007-08-08 | 明导公司 | Feature failure correlation |
| US20100287535A1 (en) * | 2009-05-08 | 2010-11-11 | Electronics And Telecommunications Research Institute | System and method for testing software reliability using fault injection |
| CN102707195A (en) * | 2012-06-01 | 2012-10-03 | 江苏省电力公司检修分公司 | Oscilloscope fault analysis platform and establishment method thereof |
| CN103853765A (en) * | 2012-12-04 | 2014-06-11 | 天津市电力公司 | Method for comparing waveform features of power system faults |
| CN108804301A (en) * | 2017-04-27 | 2018-11-13 | 株洲中车时代电气股份有限公司 | A kind of train control system software testing system and method based on E & FR data |
| CN109813999A (en) * | 2019-01-22 | 2019-05-28 | 山东大学 | A kind of Fault Diagnosis of Distribution Network algorithm automatically testing platform, method and application |
Non-Patent Citations (3)
| Title |
|---|
| L. BAM 等: "Review: power system analysis software tools", 《IEEE POWER ENGINEERING SOCIETY GENERAL MEETING , 2005》, vol. 1, pages 139 - 144 * |
| P. BERNARDI 等: "Facilitating Fault-Simulation Comprehension through a Fault-Lists Analysis Tool", 《2019 IEEE 10TH LATIN AMERICAN SYMPOSIUM ON CIRCUITS & SYSTEMS (LASCAS)》, pages 77 - 80 * |
| 丁昊: "基于多信号流图的系统测试性建模分析及软件设计", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 138 - 411 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113011606A (en) * | 2021-01-30 | 2021-06-22 | 河南帅臣停车设备科技有限公司 | Operation and maintenance management method and system for mechanical parking equipment |
| CN113051582A (en) * | 2021-04-28 | 2021-06-29 | 重庆电子工程职业学院 | Computer software technology development and debugging system |
| CN113051582B (en) * | 2021-04-28 | 2023-03-14 | 重庆电子工程职业学院 | Computer software technology development and debugging system |
| CN113626288A (en) * | 2021-08-12 | 2021-11-09 | 杭州朗和科技有限公司 | Fault processing method, system, device, storage medium and electronic equipment |
| CN113626288B (en) * | 2021-08-12 | 2023-08-25 | 杭州朗和科技有限公司 | Fault processing method, system, device, storage medium and electronic equipment |
| CN117130945A (en) * | 2023-10-26 | 2023-11-28 | 中国证券登记结算有限责任公司 | Test method and device |
| CN117130945B (en) * | 2023-10-26 | 2024-02-09 | 中国证券登记结算有限责任公司 | Test method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112306877B (en) | 2024-02-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112306877A (en) | Power system fault operation and maintenance method and system | |
| US9116779B2 (en) | Test management domain asset discovery and analysis | |
| CN106708718B (en) | Service framework interface test method and device | |
| CN111400198B (en) | Self-adaptive software testing system | |
| CN110008123B (en) | Method for automatically deploying test software and corresponding device | |
| CN111274154A (en) | Automatic testing method, device, equipment and storage medium | |
| US11704186B2 (en) | Analysis of deep-level cause of fault of storage management | |
| CN112416803A (en) | Automatic testing method and device | |
| CN117009243A (en) | Chip performance automatic test method, device, computer equipment and storage medium | |
| CN114757142A (en) | Self-error-correction chip verification method, device, equipment and computer readable medium | |
| CN113448826A (en) | Software automation test system and method | |
| CN108009086B (en) | System automation test method based on case decomposition and function learning | |
| CN113126993A (en) | Automatic testing method and system applied to vehicle detection software | |
| CN108595323A (en) | A kind of system detection method and relevant apparatus | |
| CN112148587A (en) | Software test management system and method | |
| CN114860619B (en) | Database audit program regression testing method and device | |
| CN116383021A (en) | Software package performance testing method, system, computing device and readable storage medium | |
| CN113238901B (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN114817300A (en) | Log query method based on SQL (structured query language) statements and application thereof | |
| CN112380121A (en) | Automatic testing method and system for Internet of things equipment | |
| CN112231202A (en) | Automatic Bug lifting method based on log monitoring and monitored module monitoring | |
| CN107102938B (en) | Test script updating method and device | |
| CN111240999A (en) | Method and system for improving script test execution efficiency | |
| US20230216727A1 (en) | Identification of root causes in data processing errors | |
| CN114448851B (en) | Automatic data testing method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |