CN117609029A - Software failure data fusion method and system based on data acquisition - Google Patents
Software failure data fusion method and system based on data acquisition Download PDFInfo
- Publication number
- CN117609029A CN117609029A CN202311561249.5A CN202311561249A CN117609029A CN 117609029 A CN117609029 A CN 117609029A CN 202311561249 A CN202311561249 A CN 202311561249A CN 117609029 A CN117609029 A CN 117609029A
- Authority
- CN
- China
- Prior art keywords
- test
- reliability
- rate
- met
- failure data
- 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.)
- Pending
Links
- 238000007500 overflow downdraw method Methods 0.000 title claims abstract description 21
- 238000012360 testing method Methods 0.000 claims abstract description 255
- 238000000034 method Methods 0.000 claims abstract description 44
- 238000011156 evaluation Methods 0.000 claims abstract description 24
- 239000013589 supplement Substances 0.000 claims description 17
- 230000001502 supplementing effect Effects 0.000 claims description 16
- 238000012795 verification Methods 0.000 claims description 16
- 238000003860 storage Methods 0.000 claims description 15
- 238000012790 confirmation Methods 0.000 claims description 11
- 238000007418 data mining Methods 0.000 claims description 11
- 230000004927 fusion Effects 0.000 claims description 7
- 230000000295 complement effect Effects 0.000 claims description 4
- 238000001514 detection method Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 5
- 238000004590 computer program Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 11
- 238000010200 validation analysis Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000009826 distribution Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 1
- 239000000543 intermediate Substances 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010998 test method Methods 0.000 description 1
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/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/008—Reliability or availability analysis
-
- 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/3676—Test management for coverage analysis
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software failure data fusion method and system based on data acquisition, wherein the method comprises the following steps: performing system test; judging whether the preset passing rate of the system test is met or not; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test; judging whether a reliability test preset passing rate is met or not; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied. Through the processing scheme disclosed by the invention, the efficiency of the software reliability test can be effectively improved, and the reliability test task can be completed better and faster within a limited progress range.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a software failure data fusion method and system based on data acquisition.
Background
Software reliability, one of the general quality characteristics of software, is an important characteristic for measuring the quality level of software. To verify whether the software reliability meets the user requirements, a software reliability assessment needs to be performed.
Software failure data is an input to reliability assessment, which is not performed if there is not enough failure data to meet specifications as support. In current practice, the problem of failure data has become the biggest impediment to software reliability assessment landing, mainly in terms of both quantity and quality.
In quantity, the current software has a relatively tight test working time schedule, and cannot support the software reliability test with a relatively long duration. The software reliability test is generally implemented after the software passes through a conventional test, and the software has basically the capability of running stably for a period of time, so that the software cannot easily fail within a limited test time range. In a short time, insufficient reliability test is difficult to fully expose potential problems in software, and the collected failure data cannot meet the requirement of developing software reliability evaluation in quantity.
In terms of quality, for large-scale software with huge volume and complex structure, recording failure time and collecting failure data by manpower are difficult, the problems of data missing, irregular and the like are easy to occur, and the applicability of the data is poor. In addition, failure data generated in the testing, testing and using stages can be collected at present, and the problem that more missing items exist in the data due to the fact that the need of software reliability evaluation is not considered in the demonstration stage is solved, and the utilization rate of the data is not high.
The existing problems of the quantity and quality of the failure data are difficult to support the development of reliability evaluation, and the problem of solving the failure data is a key for promoting the landing of the software reliability evaluation.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide a software failure data fusion method based on data acquisition, which at least partially solves the problems existing in the prior art.
In a first aspect, an embodiment of the present disclosure provides a software failure data fusion method based on data acquisition, where the method includes the following steps:
performing system test;
judging whether the preset passing rate of the system test is met or not; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test;
judging whether a reliability test preset passing rate is met or not; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied.
According to a specific implementation of an embodiment of the disclosure, the method further includes:
and evaluating the test cases, failure data and test passing rate generated in the system test stage, detecting the code coverage condition of the test cases in the system test stage by a code coverage rate detection tool, and supplementing extra test cases for the codes which are not covered.
According to a specific implementation of an embodiment of the present disclosure, the code coverage is calculated by the following formula:
P system and method for controlling a system ∪P Confirmation of ∪P Supplement and supplement ＝1
Wherein P is System and method for controlling a system Is the code coverage condition of the system test; p (P) Confirmation of Confirming the code coverage condition of the test; p (P) Supplement and supplement Is the code coverage case for the complementary case.
According to a specific implementation manner of the embodiment of the disclosure, the test cases, the failure data and the test passing rate generated in the system test stage are evaluated through the following formulas:
wherein P is System-System The pass rate of the system test case in the system test stage is the pass rate of the system test case in the system test stage; p (P) System-acknowledgement The pass rate of the system test case in the verification test stage is determined; f (F) System-System The total number of failures generated in the system testing stage is calculated; f (F) System-effective Is the number of failures that the system test phase is determined to be valid.
According to a specific implementation of an embodiment of the disclosure, the reliability evaluation includes:
checking and confirming code coverage condition of the test stage use cases;
supplementing use cases according to the code coverage conditions of the system and the verification test stage;
judging whether the code coverage rate of the overall use case reaches 100 percent; when the coverage rate does not reach 100%, supplementing use cases according to the code coverage conditions of the system and the verification test stage; the method comprises the steps of,
when the coverage rate reaches 100%, expanding the test on the overall use case;
evaluating the validity of failure data in a system test stage;
and outputting the total failure data.
In a second aspect, an embodiment of the present disclosure provides a software failure data fusion system based on data acquisition, where the system includes:
the system test module is configured for performing system tests; the method comprises the steps of,
judging whether the preset passing rate of the system test is met or not; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test;
the reliability test module is configured to judge whether a reliability test preset passing rate is met; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied.
According to a specific implementation of an embodiment of the disclosure, the system further includes:
the software reliability evaluation module is configured to check and confirm the code coverage condition of the test stage use cases;
supplementing use cases according to the code coverage conditions of the system and the verification test stage;
judging whether the code coverage rate of the overall use case reaches 100 percent; when the coverage rate does not reach 100%, supplementing use cases according to the code coverage conditions of the system and the verification test stage; the method comprises the steps of,
when the coverage rate reaches 100%, expanding the test on the overall use case;
evaluating the validity of failure data in a system test stage;
and outputting the total failure data.
In a third aspect, embodiments of the present disclosure further provide an electronic device, including:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor, which when executed by the at least one processor, cause the at least one processor to implement the method of software invalidation data fusion based on data mining as described in the first aspect or any implementation of the first aspect.
In a fourth aspect, the presently disclosed embodiments also provide a non-transitory computer-readable storage medium storing computer instructions that, when executed by at least one processor, cause the at least one processor to perform the software failure data fusion method of the foregoing first aspect or any implementation of the first aspect.
In a fifth aspect, embodiments of the present disclosure also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform the software failure data fusion method based on data mining in any one of the foregoing first aspect or the first aspect.
The software failure data fusion method based on the data acquisition can effectively solve the problems that the current test time is tension, failure data is insufficient and software reliability assessment cannot be carried out due to the fact that failure data is difficult to acquire, and the efficiency of software reliability test is effectively improved by fusing the acquisition information of test cases, test results and failure data in the system test and confirmation test stage, reliability test tasks are completed better and faster in a limited progress range, so that sufficient failure data are generated to support the development of subsequent reliability assessment work.
Drawings
The foregoing is merely an overview of the present invention, and the present invention is further described in detail below with reference to the accompanying drawings and detailed description.
FIG. 1 is a schematic diagram of a relationship flow of three stages of system testing, validation testing, and reliability testing in the prior art;
fig. 2 is a schematic flow chart of a software failure data fusion method based on data acquisition according to an embodiment of the disclosure;
FIG. 3 is a block diagram of a signaling flow of software failure data provided by an embodiment of the disclosure;
fig. 4 is a schematic diagram of a signaling flow for confirming software failure data in a test stage according to an embodiment of the disclosure;
fig. 5 is a schematic structural diagram of a software failure data fusion system based on data acquisition according to an embodiment of the present disclosure; and
fig. 6 is a schematic diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
Embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.
Other advantages and effects of the present disclosure will become readily apparent to those skilled in the art from the following disclosure, which describes embodiments of the present disclosure by way of specific examples. It will be apparent that the described embodiments are merely some, but not all embodiments of the present disclosure. The disclosure may be embodied or practiced in other different specific embodiments, and details within the subject specification may be modified or changed from various points of view and applications without departing from the spirit of the disclosure. It should be noted that the following embodiments and features in the embodiments may be combined with each other without conflict. All other embodiments, which can be made by one of ordinary skill in the art without inventive effort, based on the embodiments in this disclosure are intended to be within the scope of this disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the following claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the present disclosure, one skilled in the art will appreciate that one aspect described herein may be implemented independently of any other aspect, and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. In addition, such apparatus may be implemented and/or such methods practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
In addition, in the following description, specific details are provided in order to provide a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects may be practiced without these specific details.
In general engineering projects, system testing, validation testing and reliability testing of software should be three stages executed sequentially. That is, under the condition that the unit test is qualified, the software passes the system test of development group testers, and then the full-time testers perform the confirmation test, and after passing the tests of the two stages, the software can enter the software reliability test stage. Only the test results of each stage, i.e. the pass rate of the test at that stage, are passed down in three stages, and no other test process intermediates are passed.
As shown in fig. 1, the test is performed according to a mode that three test stages are sequentially executed, the process is more detailed, and the reliability of the test result is higher, but in actual production work, the method is difficult to meet the progress requirement of the project. The software reliability test is also a random test, and is almost consistent with the system test and the confirmation test in the test method and the test environment.
Aiming at the problems of the quantity and the quality of the failure data, the patent provides a software failure data fusion method based on data acquisition. The method fully utilizes the process products and results generated in two testing stages of system testing and validation testing, and carries out letter acquisition on failure data in the two testing stages of system testing and validation testing based on data credibility, so as to obtain fused software failure data. The whole test time schedule is shortened, and meanwhile, failure data generated by the test can be guaranteed to meet the requirement of reliability evaluation as far as possible.
Fig. 2 is a schematic diagram of a software failure data fusion method flow based on data acquisition according to an embodiment of the disclosure.
Fig. 3 is a flow chart of a software failure data fusion method based on data acquisition corresponding to fig. 1.
As shown in fig. 2, at step S210, a system test is performed.
More specifically, step S220 is next passed.
At step S220, it is determined whether the system test preset pass rate is satisfied; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test.
In an embodiment of the present invention, the method further includes: and evaluating the test cases, failure data and test passing rate generated in the system test stage, detecting the code coverage condition of the test cases in the system test stage by a code coverage rate detection tool, and supplementing extra test cases for the codes which are not covered.
In the embodiment of the invention, the code coverage is calculated by the following formula:
P system and method for controlling a system ∪P Confirmation of ∪P Supplement and supplement =1 … … equation 1
Wherein P is System and method for controlling a system Is the code coverage condition of the system test; p (P) Confirmation of Confirming the code coverage condition of the test; p (P) Supplement and supplement Is the code coverage case for the complementary case.
In the embodiment of the invention, the test cases, the failure data and the test passing rate generated in the system test stage are evaluated by the following formulas:
wherein P is System-System The pass rate of the system test case in the system test stage is the pass rate of the system test case in the system test stage; p (P) System-acknowledgement The pass rate of the system test case in the verification test stage is determined; f (F) System-System The total number of failures generated in the system testing stage is calculated; f (F) System-effective Is the number of failures that the system test phase is determined to be valid.
More specifically, the test cases implement code full coverage.
In the actual reliability test, in order to meet the sufficiency of the reliability test, the possible potential problems in the software are fully exposed, reliable failure data are obtained, and the code coverage rate of the reliability test case should be as high as 100%. Therefore, the method provided by the application firstly evaluates the test cases, failure data and test passing rate generated in the system test stage, and detects the code coverage condition of the test cases in the system test stage and confirms the test stage through the code coverage rate detection tool, and supplements extra test cases for the uncovered codes. The method comprises the following steps:
P system and method for controlling a system ∪P Confirmation of ∪P Supplement and supplement ＝1
Wherein P is System and method for controlling a system Is the code coverage condition of the system test; p (P) Confirmation of Confirming the code coverage condition of the test; p (P) Supplement and supplement Is the code coverage case for the complementary case. The total reliability test case consists of the three parts of test cases together.
Failure data acquisition in the system test stage:
in general, the operations commonly used by users in actual use are mainly focused on functions related to a main path, and the main path of software is already tested by a system testing stage, so the application considers that failure data generated by the software system testing stage can be converted and utilized as a part of total failure data.
But the effect of the system test needs to be evaluated and converted when in use. The application considers that the trust degree of the failure number in the system test stage is positively related to the accuracy degree of the system test, and the trust degree is as follows:
wherein P is System-System The pass rate of the system test case in the system test stage is the pass rate of the system test case in the system test stage; p (P) System-acknowledgement The pass rate of the system test case in the verification test stage is determined; f (F) System-System The total number of failures generated in the system testing stage is calculated; f (F) System-effective Is the number of failures that the system test phase is determined to be valid.
Next, the process goes to step S230.
At step S230, it is determined whether the reliability test preset pass rate is satisfied; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied.
In an embodiment of the present invention, the reliability evaluation includes:
checking and confirming code coverage condition of the test stage use cases;
supplementing use cases according to the code coverage conditions of the system and the verification test stage;
judging whether the code coverage rate of the overall use case reaches 100 percent; when the coverage rate does not reach 100%, supplementing use cases according to the code coverage conditions of the system and the verification test stage; the method comprises the steps of,
when the coverage rate reaches 100%, expanding the test on the overall use case;
evaluating the validity of failure data in a system test stage;
and outputting the total failure data.
More specifically, the validation test phase failure data acquisition includes the steps of:
during the validation test phase, the tester needs to collect a sufficient amount of failure data for the development of the software reliability assessment while completing the conventional validation test work, as shown in fig. 4.
Firstly, checking and confirming the code coverage condition of the test case, supplementing the corresponding test case according to the code coverage condition of the system test case and the importance degree of operation, and ensuring that the code coverage rate of the overall case reaches 100%; then, expanding the test of the overall test case, evaluating the effectiveness of failure data generated by the system test, and receiving the failure data of the system test according to the proportion by checking the accuracy of the passing rate of the system test; and finally, summarizing the failure data generated by the three cases, and generating and outputting total failure data for subsequent evaluation work.
That is, the failure data determined to be valid by the system test, the failure data generated by the validation test, and the failure data generated by the supplementary use case together constitute the overall software failure data.
Fig. 5 shows a software failure data fusion system 500 based on data acquisition, which includes a system test module 510 and a reliability test module 520.
The system test module 510 is used for performing system test; the method comprises the steps of,
judging whether the preset passing rate of the system test is met or not; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test;
the reliability test module 520 is configured to determine whether a reliability test preset passing rate is satisfied; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied.
In an embodiment of the present invention, the system further includes:
the software reliability evaluation module is used for checking and confirming the code coverage condition of the test stage use case;
supplementing use cases according to the code coverage conditions of the system and the verification test stage; judging whether the code coverage rate of the overall use case reaches 100 percent; when the coverage rate does not reach 100%, supplementing use cases according to the code coverage conditions of the system and the verification test stage; and when the coverage reaches 100%, expanding the test on the overall use case; evaluating the validity of failure data in a system test stage; and outputting the total failure data.
Referring to fig. 6, an embodiment of the present disclosure also provides an electronic device 60, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the data mining-based software disablement data fusion method of the foregoing method embodiments.
The disclosed embodiments also provide a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the software failure data fusion method based on data mining in the foregoing method embodiments.
The disclosed embodiments also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform the data mining-based software disablement data fusion method in the foregoing method embodiments.
Referring now to fig. 6, a schematic diagram of an electronic device 60 suitable for use in implementing embodiments of the present disclosure is shown. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 6, the electronic device 60 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic device 60 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
In general, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; an output device 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 60 to communicate with other devices wirelessly or by wire to exchange data. While an electronic device 60 having various means is shown, it is to be understood that not all of the illustrated means are required to be implemented or provided. More or fewer devices may be implemented or provided instead.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via communication means 609, or from storage means 608, or from ROM 602. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by the processing device 601.
It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring at least two internet protocol addresses; sending a node evaluation request comprising the at least two internet protocol addresses to node evaluation equipment, wherein the node evaluation equipment selects an internet protocol address from the at least two internet protocol addresses and returns the internet protocol address; receiving an Internet protocol address returned by the node evaluation equipment; wherein the acquired internet protocol address indicates an edge node in the content distribution network.
Alternatively, the computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: receiving a node evaluation request comprising at least two internet protocol addresses; selecting an internet protocol address from the at least two internet protocol addresses; returning the selected internet protocol address; wherein the received internet protocol address indicates an edge node in the content distribution network.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The name of the unit does not in any way constitute a limitation of the unit itself, for example the first acquisition unit may also be described as "unit acquiring at least two internet protocol addresses".
It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof.
The foregoing is merely specific embodiments of the disclosure, but the protection scope of the disclosure is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the disclosure are intended to be covered by the protection scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.
Claims (9)
1. The software failure data fusion method based on data acquisition is characterized by comprising the following steps of:
performing system test;
judging whether the preset passing rate of the system test is met or not; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test;
judging whether a reliability test preset passing rate is met or not; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied.
2. The method of data mining-based software failure data fusion of claim 1, further comprising:
and evaluating the test cases, failure data and test passing rate generated in the system test stage, detecting the code coverage condition of the test cases in the system test stage by a code coverage rate detection tool, and supplementing extra test cases for the codes which are not covered.
3. The data mining-based software failure data fusion method of claim 2, wherein the code coverage is calculated by the following formula:
P system and method for controlling a system ∪P Confirmation of ∪P Supplement and supplement ＝1
Wherein P is System and method for controlling a system Is the code coverage condition of the system test; p (P) Confirmation of Confirming the code coverage condition of the test; p (P) Supplement and supplement Is the code coverage case for the complementary case.
4. The method for fusing software failure data based on data acquisition according to claim 2, wherein test cases, failure data and test passing rate generated in the system test stage are evaluated by the following formulas:
wherein P is System-System The pass rate of the system test case in the system test stage is the pass rate of the system test case in the system test stage; p (P) System-acknowledgement The pass rate of the system test case in the verification test stage is determined; f (F) System-System The total number of failures generated in the system testing stage is calculated; f (F) System-effective Is the number of failures that the system test phase is determined to be valid.
5. The software failure data fusion method based on data mining according to claim 1, wherein the reliability evaluation includes:
checking and confirming code coverage condition of the test stage use cases;
supplementing use cases according to the code coverage conditions of the system and the verification test stage;
judging whether the code coverage rate of the overall use case reaches 100 percent; when the coverage rate does not reach 100%, supplementing use cases according to the code coverage conditions of the system and the verification test stage; the method comprises the steps of,
when the coverage rate reaches 100%, expanding the test on the overall use case;
evaluating the validity of failure data in a system test stage;
and outputting the total failure data.
6. A software failure data fusion system based on data acquisition, the system comprising:
the system test module is configured for performing system tests; the method comprises the steps of,
judging whether the preset passing rate of the system test is met or not; when the preset passing rate of the system test is not met, the system test is carried out again; and when the preset passing rate of the system test is met, performing a reliability test;
the reliability test module is configured to judge whether a reliability test preset passing rate is met; when the reliability test preset passing rate is not met, the reliability test is conducted again; and outputting a reliability evaluation result when the reliability test preset pass rate is satisfied.
7. The data mining-based software disablement data fusion system of claim 6, wherein the system further comprises:
the software reliability evaluation module is configured to check and confirm the code coverage condition of the test stage use cases;
supplementing use cases according to the code coverage conditions of the system and the verification test stage;
judging whether the code coverage rate of the overall use case reaches 100 percent; when the coverage rate does not reach 100%, supplementing use cases according to the code coverage conditions of the system and the verification test stage; the method comprises the steps of,
when the coverage rate reaches 100%, expanding the test on the overall use case;
evaluating the validity of failure data in a system test stage;
and outputting the total failure data.
8. An electronic device, comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor, which when executed by the at least one processor, cause the at least one processor to perform the data mining-based software disablement data fusion method as claimed in any one of claims 1 to 5.
9. A non-transitory computer-readable storage medium storing computer instructions that, when executed by at least one processor, cause the at least one processor to perform the data mining-based software disablement data fusion method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311561249.5A CN117609029A (en) | 2023-11-22 | 2023-11-22 | Software failure data fusion method and system based on data acquisition |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311561249.5A CN117609029A (en) | 2023-11-22 | 2023-11-22 | Software failure data fusion method and system based on data acquisition |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117609029A true CN117609029A (en) | 2024-02-27 |
Family
ID=89943529
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311561249.5A Pending CN117609029A (en) | 2023-11-22 | 2023-11-22 | Software failure data fusion method and system based on data acquisition |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117609029A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109542761A (en) * | 2018-10-11 | 2019-03-29 | 平安科技（深圳）有限公司 | Evaluation of Software Quality, device and storage medium |
| CN115757169A (en) * | 2022-11-29 | 2023-03-07 | 德邦证券股份有限公司 | Interface automation test-based judgment method and device and storage medium |
-
2023
- 2023-11-22 CN CN202311561249.5A patent/CN117609029A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109542761A (en) * | 2018-10-11 | 2019-03-29 | 平安科技（深圳）有限公司 | Evaluation of Software Quality, device and storage medium |
| CN115757169A (en) * | 2022-11-29 | 2023-03-07 | 德邦证券股份有限公司 | Interface automation test-based judgment method and device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 朱丽: "嵌入式软件动态测试平台的研究与实现", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》, no. 2, 15 February 2014 (2014-02-15) * |
| 李思雨: "基于神经网络的软件可靠性模型研究及实现", 《中国优秀硕士学位论文全文数据库 (信息科技辑)》, no. 3, 15 March 2021 (2021-03-15), pages 17 - 23 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| CN112650685B (en) | Automatic test method, device, electronic equipment and computer storage medium | |
| CN112395188B (en) | Test-oriented software project development method and device, electronic equipment and storage medium | |
| CN112597047A (en) | Test method, test device, electronic equipment and computer readable medium | |
| CN113806212A (en) | Application program exception positioning method and device and electronic equipment | |
| CN104579830A (en) | Service monitoring method and device | |
| CN112988494A (en) | Abnormity testing method and device and electronic device | |
| CN111327913A (en) | Message processing method and device and electronic equipment | |
| CN111258803B (en) | Collapse positioning method and device and electronic equipment | |
| CN109491908B (en) | Page detection method and device, electronic equipment and storage medium | |
| CN112291121B (en) | Data processing method and related equipment | |
| CN109542743B (en) | Log checking method and device, electronic equipment and computer readable storage medium | |
| CN109408387B (en) | Page testing method and device | |
| CN117609029A (en) | Software failure data fusion method and system based on data acquisition | |
| CN114185805A (en) | Embedded point verification method, device, equipment and storage medium | |
| CN114499709A (en) | Antenna reception testing method and device, electronic equipment and storage medium | |
| CN113656301A (en) | Interface testing method, device, equipment and storage medium | |
| CN117251355A (en) | Performance test method, device, equipment, computer readable storage medium and product | |
| CN114547521A (en) | Authority-based interactive interface publishing method and device and electronic equipment | |
| CN116932373A (en) | Test case screening method, device, storage medium and program product | |
| CN116257422A (en) | Self-test case generation method and device and electronic equipment | |
| CN111382056B (en) | Service testing method and device, server and storage medium | |
| CN113760768A (en) | Test method, monitoring platform, electronic equipment and storage medium | |
| CN115941432A (en) | Domain name alarm information sending method and device, electronic equipment and computer readable storage medium | |
| CN115237816B (en) | System function verification method and device, electronic equipment and readable storage medium |
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 |