CN110795342A - Error detection method and device - Google Patents
Error detection method and device Download PDFInfo
- Publication number
- CN110795342A CN110795342A CN201910963719.8A CN201910963719A CN110795342A CN 110795342 A CN110795342 A CN 110795342A CN 201910963719 A CN201910963719 A CN 201910963719A CN 110795342 A CN110795342 A CN 110795342A
- Authority
- CN
- China
- Prior art keywords
- error
- reason
- target
- error information
- information
- 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
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/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides an error detection method and device. The method is applied to software testing equipment and comprises the following steps: in the software testing process, if error information is tested currently, counting the times of the error information caused by each acquired error reason in a previous specified time period; and determining a target error reason causing the error information according to the times of causing the error information by each error reason in the previous specified period. According to the method and the device, after the error information is tested, the target error reason causing the current error information is determined according to the times of the error information caused by the error reasons in the past, so that the determination process of the target error reason is objective, the accuracy of determining the target error reason is improved to a certain extent, and the troubleshooting efficiency is improved.
Description
Technical Field
The application relates to the technical field of software testing, in particular to an error detection method and device.
Background
In the software testing process, if the testing environment, the testing script or the tested software has errors, error information is generated. After generating the error message, the tester needs to check the error reason causing the error message.
Due to the variety of error reasons, a tester usually determines the error reason which may cause the error information according to his own experience, and then checks the error reason. For example, after the error information 0000X1 occurs during the software testing process, the tester determines that it may be caused by the error of the test script, and then checks whether the error of the test script exists.
However, the tester only determines the error reason causing the error information according to the experience of the tester, and the accuracy of the determination is poor, so that the efficiency of troubleshooting the error reason is low.
Disclosure of Invention
In view of the above, the present application provides an error detection method and apparatus.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of embodiments of the present application, there is provided an error detection method, which is applied to a software test device, and includes:
in the software testing process, if error information is tested currently, counting the times of error information caused by each acquired error reason in a previous specified time period;
and determining a target error reason causing the error information according to the times of causing the error information by each error reason in the previous specified period.
Optionally, counting the number of times that each acquired error reason causes error information in a previous specified time period includes:
searching a target table item containing the keyword in an obtained error reason statistical table by taking the error information as the keyword, wherein the error reason statistical table is obtained when software testing is carried out in a specified time period, and the table items in the error reason statistical table comprise: error information, at least one error cause, and the number of times each error cause caused the error information;
and counting the times of error information caused by each error reason in the target table entry.
Optionally, determining the target error cause causing the error information according to the number of times that each error cause causes the error information in the previous specified period includes:
calculating the selected parameter value of each error reason according to the times of the error information caused by each error reason in the previous designated time period;
and determining a target error reason causing the error information according to the selected parameter value of each error reason.
Optionally, calculating the selected parameter value of each error cause according to the number of times that each error cause causes error information in the previous specified time period includes:
for each error reason, performing setting operation on the number of times of causing the error information by the error reason in a specified time period and M, wherein M is the sum of the obtained number of times of causing the error information by all the error reasons in the specified time period;
and determining the obtained operation result as the selected parameter value of the error reason.
Optionally, determining the target error cause causing the error information according to the selected parameter value of each error cause includes:
selecting a target selected parameter value with the largest value from the selected parameter values of all error reasons;
and determining the error reason corresponding to the target selected parameter value as the target error reason causing the error information.
According to a second aspect of embodiments of the present application, there is provided an error detection apparatus, which is applied to a software test device, the apparatus including:
the statistical unit is used for counting the times of error information caused by each acquired error reason in a previous specified time period if the error information is tested currently in the software testing process;
and a target error cause determination unit for determining a target error cause causing the error information according to the number of times each error cause causes the error information in a previous specified period.
Optionally, the counting, by the counting unit, the number of times that each acquired error reason causes error information in a previous specified time period includes:
searching a target table item containing the keyword in an obtained error reason statistical table by taking the error information as the keyword, wherein the error reason statistical table is obtained when software testing is carried out in a specified time period, and the table items in the error reason statistical table comprise: error information, at least one error cause, and the number of times each error cause caused the error information;
and counting the times of error information caused by each error reason in the target table entry.
Optionally, the determining, by the target error cause determining unit, the target error cause causing the error information according to the number of times that each error cause causes the error information in a previous specified period, includes:
calculating the selected parameter value of each error reason according to the times of the error information caused by each error reason in the previous designated time period;
and determining a target error reason causing the error information according to the selected parameter value of each error reason.
Optionally, the calculating, by the target error cause determining unit, the selected parameter value of each error cause according to the number of times that each error cause causes error information in a previous specified time period includes:
for each error reason, performing setting operation on the number of times of causing the error information by the error reason in a specified time period and M, wherein M is the sum of the obtained number of times of causing the error information by all the error reasons in the specified time period;
and determining the obtained operation result as the selected parameter value of the error reason.
Optionally, the determining, by the target error cause determining unit, the target error cause causing the error information according to the selected parameter value of each error cause includes:
selecting a target selected parameter value with the largest value from the selected parameter values of all error reasons;
and determining the error reason corresponding to the target selected parameter value as the target error reason causing the error information.
According to the method and the device, after the error information is tested, the target error reason causing the current error information is determined according to the times of the error information caused by the error reasons in the past, so that the determination process of the target error reason is objective, the accuracy of determining the target error reason is improved to a certain extent, and the troubleshooting efficiency is improved.
Drawings
Fig. 1 is a flowchart of an error detection method provided in the present application.
Fig. 2 is a flowchart of an implementation of step 101 provided in the present application.
Fig. 3 is a flowchart of an implementation of step 102 provided in the present application.
Fig. 4 is a schematic diagram of test information in HTML format exemplarily shown in the present application.
Fig. 5 is a schematic diagram of a test report exemplary illustrated in the present application.
Fig. 6 is a structural diagram of an error detection device according to the present application.
Fig. 7 is a hardware structure diagram of a software testing apparatus where the error detection apparatus of the present application is located.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in detail below with reference to the accompanying drawings and specific embodiments.
Referring to fig. 1, fig. 1 is a flowchart of an error detection method provided in the present application.
As an example, the flow shown in fig. 1 may be applied to a software testing device, on which a testing Framework for testing software may be run, such as a Robot Framework, a cuumber (Cucumber) testing Framework, or a SpecFlow testing Framework, and the software testing device running the Robot Framework is taken as an example for description herein.
As shown in fig. 1, the process may include the following steps:
step 101, in the software testing process, if the error information is tested currently, counting the times of error information caused by each acquired error reason in the previous specified time period;
as an embodiment, there are many implementation manners for obtaining error information occurring in the software testing process, which will be described in detail later, and will not be described herein again.
As an embodiment, the error reason may be set manually by a user, for example, the error reason may be set according to a position where the error occurs, and the error reason may be set to be a test environment error, a test script error, or a tested software error; the error cause may be set according to the type of the error, and may be set as a code stroke error or a code logic error. The error reasons are described as test environment errors, test script errors and tested software errors.
As one embodiment, the specified period of time before in step 101 refers to a certain period of time before the software testing process. As a simple example, if the software testing process is performed in 5/2019, the specified period of time before may be a period of time before 5/2019, for example, may be from 1/2019/5 to 4/2019. The designated time period can be flexibly set according to the self-demand of the user, and the application is not particularly limited.
As an embodiment, there are many implementation manners for counting the number of times that each error reason causes error information in a previous specified time period, and fig. 2 illustrates one implementation manner, which is not described herein again for the sake of example.
Step 102, determining a target error reason causing the error information according to the times of causing the error information by each error reason in the previous specified time period.
As one embodiment, there are many implementations of determining the target error cause causing the error information according to the number of times each error cause causes the error information in the previous specified period, for example, determining the error cause having the largest number of times the error information is caused in the previous specified period among the error causes as the target error cause. In addition, fig. 3 illustrates another implementation, which is not described herein for the sake of brevity.
Thus, the flow shown in fig. 1 is completed.
As can be seen from the flow shown in fig. 1, in the present application, after the error information is tested, the target error reason causing the current error information is determined according to the number of times that each error reason causes the error information before, so that the determination process of the target error reason is relatively objective, the accuracy of determining the target error reason is improved to a certain extent, and the troubleshooting efficiency is further improved.
How to obtain error information occurring in the software testing process in step 101 is described below:
in the process of carrying out software test on the tested software by the Robot Framework running on the software test equipment, test information can be continuously generated, wherein the test information comprises the running time of a test code, a test result, error information and the like. Since the Robot Framework is a software automation test Framework written based on python, the software test equipment can retrieve error information in the test information through python in a regular expression manner. Fig. 4 shows an example of test information in HTML format. Referring to fig. 4, the software testing device may find < td class "> < span > FAIL > </td > in the HTML-format test information shown in fig. 4 based on the FAIL field, that is, a table storing error information. After the table storing the error information is found, the error information recorded in the next row of information of the table can be extracted. For example, the information stored in the next row of the table is < td class ═ message ">0000X1</td >, and the message field can be used to extract the error information: 0000X 1.
Referring to fig. 2, fig. 2 is a flowchart of an implementation of step 101 provided in the present application. As shown in fig. 2, the process may include:
step 1011, using the error information as a keyword to find a target entry containing the keyword in the obtained error cause statistical table, wherein the error cause statistical table is obtained when software testing is performed in a specified time period, and entries in the error cause statistical table include: error information, at least one error cause, and the number of times each error cause caused the error information;
as an embodiment, the error cause statistical table is obtained when software testing is performed within a specified period. In the software testing process in the appointed time period, every time error information occurs, the error information and the error reason causing the error information are recorded into an error reason statistical table, 1 is added to the frequency of the error information caused by the error reason, and the error reason statistical table is obtained after the software testing in the appointed time period is finished. Table 1 is an exemplary error cause statistics table.
TABLE 1
In table 1, error information and the number of times of error information caused by an error in the test environment, an error in the test script, and an error in the software to be tested are recorded. Taking the currently tested error information as 0000X1 as an example, the entry with the error information including 0000X1 can be found.
In step 1012, the number of times of error messages caused by each error reason in the target entry is counted.
As an embodiment, after the target entry is found, the number of times that each error reason recorded in the entry causes error information may be counted, and the counted number may be used as the number of times that each error reason causes error information in a previous specified time period. Still taking the error information of 0000X1 as an example, after the table entry including 0000X1 is found in table 1, the number of times of error information caused by each error reason in the table entry may be counted, that is, the number of times of error information caused by an error in the test environment is 15 times, the number of times of error information caused by an error in the test script is 20 times, and the number of times of error information caused by an error in the tested software is 12 times.
Thus, the flow shown in fig. 2 is completed.
Referring to fig. 3, fig. 3 is a flowchart illustrating an implementation of step 102 provided herein. As shown in fig. 3, the process may include:
step 1021, calculating the selected parameter value of each error reason according to the times of the error information caused by each error reason in the previous designated time interval;
as an embodiment, the selected parameter value can be calculated in various ways, and two calculation ways are taken as examples and described below.
As an embodiment, for each error cause, performing a setting operation on the number of times that the error cause causes error information in a specified time period and M, where M is the sum of the obtained number of times that all error causes cause error information in the specified time period; and determining the obtained operation result as the selected parameter value of the error reason. The setting operation may be to calculate a ratio of the number of times that each error cause causes error information in a specified period to M, to calculate a difference between the number of times that each error cause causes error information in a specified period and M, or to calculate a sum of the number of times that each error cause causes error information in a specified period and M. Here, still taking the error information 0000X1 and the error cause statistical table as table 1 as an example, a description will be given of a calculation manner of selecting parameters when setting calculation to calculate a ratio of the number of times of causing error information in a specified period to M for each error cause. M is the sum of the number of times of error information caused by test environment errors, 15 times of error information caused by test script errors, 20 times of error information caused by test script errors and 12 times of error information caused by test software errors, namely 47 times. The selected parameters for testing environment errors are as follows: the ratio of the number of times of error-causing information of the test environment error 15 times to the calculated 47 times, i.e. 0.32. The selected parameters for testing the script errors are as follows: the ratio of the number of times 20 that the test script makes an error to the calculated 47 times, i.e., 0.43, is an error. The selected parameters of the tested software errors are as follows: the ratio of the number of times of error information caused by software to be tested being in error to 47 times is calculated, namely 0.26.
As another example, a difference between the number of times that the error cause causes error information in a specified period and N may be calculated for each error cause, where N may be an average of the acquired number of times that all error causes cause error information in the specified period; and determining the calculated difference value as the selected parameter value of the error reason.
Step 1022, determining a target error reason causing the error information according to the selected parameter value of each error reason.
As one embodiment, because there are many calculation methods for the selected parameter value, there are also many implementation methods for determining the target error reason causing the error information according to the selected parameter value of each error reason. However, in each method for determining the target error cause, the determined target error cause is the error cause which causes the error information the most frequently in the previous specified time period. Next, a method of calculating each selected parameter value exemplified in step 1021 will be described as an example.
As an embodiment, when the selected parameter value of the error cause is a ratio of the number of times that the error cause causes the error information in the specified time period to M, a target selected parameter value with a maximum value may be selected from the selected parameter values of the error causes, and the error cause corresponding to the target selected parameter value may be determined as the target error cause causing the error information. Still taking the error information of 0000X1 and the error cause statistical table as table 1 as an example, after the selected parameter of the test environment error is calculated to be 0.32, the selected parameter of the test script error is 0.43 and the selected parameter of the tested software error is 0.26, the target error cause can be selected as the test script error according to the selected parameters of the three.
As an embodiment, when the selected parameter value of the error cause is a difference between the number of times that the error cause causes the error information in the specified period and M, a target selected parameter value with a maximum value may be selected from the selected parameter values of the error causes, and the error cause corresponding to the target selected parameter value may be determined as the target error cause causing the error information.
As an embodiment, when the selected parameter value of the error cause is the sum of the number of times that the error cause causes the error information in the specified period and M, a target selected parameter value with the largest value may be selected from the selected parameter values of the error causes, and the error cause corresponding to the target selected parameter value may be determined as the target error cause causing the error information.
As an embodiment, when the selected parameter value of the error cause is a difference between the number of times that the error cause causes the error information in the specified period and N, a target selected parameter value with a maximum value may be selected from the selected parameter values of the error causes, and the error cause corresponding to the target selected parameter value may be determined as the target error cause causing the error information.
The flow shown in fig. 3 is completed.
In this application, once the target error reason is determined in step 1022, a test report may be generated based on the target error reason, which is described in detail below:
as one example, in generating a test report, error information, a target error cause, and selected parameter values for the target error cause may be added to the test report for reference by a user in troubleshooting the error cause that caused the error information. Referring to fig. 5, fig. 5 is a schematic diagram of a test report exemplarily shown in the present application, in which error information is 0000X1, a target error cause is a test script error, and selected parameters of the target error cause are recorded: 0.43. as another embodiment, on the basis of the foregoing embodiment, other error causes other than the target error cause and selected parameter values of other error causes may also be added to the test report, so that after the user eliminates the possibility that the target error cause causes the error information, the error cause may be checked according to the selected parameter values of other error causes.
Corresponding to the foregoing embodiments of the error detection method, the present application also provides embodiments of an error detection apparatus.
The embodiment of the error detection device can be applied to software test equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a device in a logical sense, the device is formed by reading a corresponding determining machine program instruction in a nonvolatile memory into an internal memory through a processor of software testing equipment where the device is located to operate. From a hardware aspect, as shown in fig. 7, the hardware structure diagram of the software testing apparatus where the error detection device is located in the present application is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 7, the software testing apparatus where the device is located in the embodiment may also include other hardware according to the actual function of the error detection device, which is not described again.
Referring to fig. 6, fig. 6 is a diagram illustrating the structure of the apparatus according to the present invention. The device includes:
a counting unit 610, configured to count, in a software testing process, the number of times that each acquired error reason causes error information in a previous specified time period if the error information is currently tested;
a target error cause determination unit 620 for determining a target error cause causing the error information according to the number of times each error cause causes the error information in the previous specified period.
Thus, the structure of the apparatus shown in FIG. 6 is completed.
As an embodiment, the counting unit 610 counts the number of times each acquired error cause causes error information in a previous specified period includes:
searching a target table item containing the keyword in an obtained error reason statistical table by taking the error information as the keyword, wherein the error reason statistical table is obtained when software testing is carried out in a specified time period, and the table items in the error reason statistical table comprise: error information, at least one error cause, and the number of times each error cause caused the error information;
and counting the times of error information caused by each error reason in the target table entry.
As one embodiment, the target error cause determining unit 620 determines the target error cause causing the error information according to the number of times each error cause causes the error information in the previous specified period, including:
calculating the selected parameter value of each error reason according to the times of the error information caused by each error reason in the previous designated time period;
and determining a target error reason causing the error information according to the selected parameter value of each error reason.
As an embodiment, the target error cause determination unit 620 calculates the selected parameter value for each error cause according to the number of times that each error cause causes error information in a previous specified period, including:
for each error reason, performing setting operation on the number of times of causing the error information by the error reason in a specified time period and M, wherein M is the sum of the obtained number of times of causing the error information by all the error reasons in the specified time period;
and determining the obtained operation result as the selected parameter value of the error reason.
As an embodiment, the target error cause determining unit 620 determines the target error cause causing the error information according to the selected parameter value of each error cause, including:
selecting a target selected parameter value with the largest value from the selected parameter values of all error reasons;
and determining the error reason corresponding to the target selected parameter value as the target error reason causing the error information.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
Referring to fig. 7, fig. 7 is a hardware structure diagram of a software testing device where the error detection apparatus of the present application is located, where the hardware structure includes: a processor and a memory.
Wherein the memory is to store machine executable instructions;
the processor is configured to read and execute the machine executable instructions stored in the memory to implement the error detection method shown in fig. 1.
For one embodiment, the memory may be any electronic, magnetic, optical, or other physical storage device that may contain or store information such as executable instructions, data, and the like. For example, the memory may be: volatile memory, non-volatile memory, or similar storage media. In particular, the Memory may be a RAM (random Access Memory), a flash Memory, a storage drive (e.g., a hard disk drive), a solid state disk, any type of storage disk (e.g., an optical disk, a DVD, etc.), or similar storage medium, or a combination thereof.
So far, the description of the apparatus shown in fig. 7 is completed.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. An error detection method, applied to a software test device, the method comprising:
in the software testing process, if error information is tested currently, counting the times of the error information caused by each acquired error reason in a previous specified time period;
and determining a target error reason causing the error information according to the times of causing the error information by each error reason in the previous specified period.
2. The method of claim 1, wherein the counting the number of times each acquired error cause causes the error information in a specified period of time comprises:
searching a target table item containing the keyword in an obtained error reason statistical table by taking the error information as the keyword, wherein the error reason statistical table is obtained when software testing is carried out in the specified time period, and the table item in the error reason statistical table comprises: error information, at least one error cause, and the number of times each error cause caused the error information;
and counting the times of the error information caused by each error reason in the target table entry.
3. The method according to claim 1 or 2, wherein the determining a target error cause causing the error information according to the number of times each error cause causes the error information within a previously specified period of time comprises:
calculating the selected parameter value of each error reason according to the times of the error information caused by each error reason in the previous designated time period;
and determining a target error reason causing the error information according to the selected parameter value of each error reason.
4. The method of claim 3, wherein calculating the selected parameter value for each error cause based on the number of times that each error cause caused the error message in a previously specified time period comprises:
setting and calculating the times of causing the error information by the error reason in the specified time period and M for each error reason, wherein M is the sum of the acquired times of causing the error information by all the error reasons in the specified time period;
and determining the obtained operation result as the selected parameter value of the error reason.
5. The method of claim 3, wherein determining a target error cause causing the error information based on the selected parameter value for each error cause comprises:
selecting a target selected parameter value with the largest value from the selected parameter values of all error reasons;
and determining the error reason corresponding to the target selected parameter value as the target error reason causing the error information.
6. An error detection apparatus, applied to a software test device, the apparatus comprising:
the statistical unit is used for counting the times of error information caused by each acquired error reason in a previous specified time period if the error information is tested currently in the software testing process;
and the target error reason determining unit is used for determining the target error reason causing the error information according to the times of causing the error information by each error reason in the previous specified time period.
7. The apparatus according to claim 6, wherein the counting unit counts the number of times each of the acquired error causes has caused the error information within a previously specified period of time, and comprises:
searching a target table item containing the keyword in an obtained error reason statistical table by taking the error information as the keyword, wherein the error reason statistical table is obtained when software testing is carried out in the specified time period, and the table item in the error reason statistical table comprises: error information, at least one error cause, and the number of times each error cause caused the error information;
and counting the times of the error information caused by each error reason in the target table entry.
8. The apparatus according to claim 6 or 7, wherein the target error cause determination unit determines the target error cause causing the error information according to the number of times each error cause causes the error information within a previously specified period of time includes:
calculating the selected parameter value of each error reason according to the times of the error information caused by each error reason in the previous designated time period;
and determining a target error reason causing the error information according to the selected parameter value of each error reason.
9. The apparatus according to claim 8, wherein the target error cause determination unit calculates the selected parameter value for each error cause according to the number of times that each error cause caused the error information within a previously specified period of time includes:
setting and calculating the times of causing the error information by the error reason in the specified time period and M for each error reason, wherein M is the sum of the acquired times of causing the error information by all the error reasons in the specified time period;
and determining the obtained operation result as the selected parameter value of the error reason.
10. The apparatus according to claim 8, wherein the target error cause determination unit determines the target error cause causing the error information based on the selected parameter value for each error cause includes:
selecting a target selected parameter value with the largest value from the selected parameter values of all error reasons;
and determining the error reason corresponding to the target selected parameter value as the target error reason causing the error information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910963719.8A CN110795342A (en) | 2019-10-11 | 2019-10-11 | Error detection method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910963719.8A CN110795342A (en) | 2019-10-11 | 2019-10-11 | Error detection method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110795342A true CN110795342A (en) | 2020-02-14 |
Family
ID=69439141
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910963719.8A Pending CN110795342A (en) | 2019-10-11 | 2019-10-11 | Error detection method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110795342A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035341A (en) * | 2020-08-11 | 2020-12-04 | 北京三快在线科技有限公司 | Automatic testing method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080109547A1 (en) * | 2006-11-02 | 2008-05-08 | International Business Machines Corporation | Method, system and program product for determining a number of concurrent users accessing a system |
| CN102479113A (en) * | 2010-11-30 | 2012-05-30 | 中国移动通信集团黑龙江有限公司 | Abnormal self-adapting processing method and system |
| CN106557398A (en) * | 2015-09-29 | 2017-04-05 | 腾讯科技（深圳）有限公司 | Information uploading method and device |
| CN109857672A (en) * | 2019-02-22 | 2019-06-07 | 杭州迪普科技股份有限公司 | A kind of formation gathering method, device, equipment and storage medium |
-
2019
- 2019-10-11 CN CN201910963719.8A patent/CN110795342A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080109547A1 (en) * | 2006-11-02 | 2008-05-08 | International Business Machines Corporation | Method, system and program product for determining a number of concurrent users accessing a system |
| CN102479113A (en) * | 2010-11-30 | 2012-05-30 | 中国移动通信集团黑龙江有限公司 | Abnormal self-adapting processing method and system |
| CN106557398A (en) * | 2015-09-29 | 2017-04-05 | 腾讯科技（深圳）有限公司 | Information uploading method and device |
| CN109857672A (en) * | 2019-02-22 | 2019-06-07 | 杭州迪普科技股份有限公司 | A kind of formation gathering method, device, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112035341A (en) * | 2020-08-11 | 2020-12-04 | 北京三快在线科技有限公司 | Automatic testing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20120079460A1 (en) | Instrumentation apparatus and method | |
| CN112579327B (en) | Fault detection method, device and equipment | |
| CN107678972B (en) | Test case evaluation method and related device | |
| CN112035314B (en) | Memory leakage monitoring method and device and electronic equipment | |
| CN108845927B (en) | Test case screening method and device | |
| US20140337673A1 (en) | Creating test templates based on steps in existing tests | |
| CN116340072B (en) | Fault detection method and device for multi-core chip | |
| CN110795342A (en) | Error detection method and device | |
| CN114860487A (en) | Memory fault identification method and memory fault isolation method | |
| CN112256462B (en) | Service life prediction method, device and medium of NAND Flash memory | |
| CN107102938B (en) | Test script updating method and device | |
| CN113708959B (en) | Rule base updating method, device and equipment | |
| CN111382052A (en) | Code quality evaluation method and device and electronic equipment | |
| CN112235312B (en) | Method and device for determining credibility of security event and electronic equipment | |
| CN109003643A (en) | A kind of data processing method and device | |
| CN110752962A (en) | Monitoring method and device of advertisement interface | |
| CN113076451B (en) | Abnormal behavior identification and risk model library establishment method and device and electronic equipment | |
| CN112882854B (en) | Method and device for processing request exception | |
| CN114385764A (en) | Reverse analysis method and device for relational database table structure | |
| CN110221971B (en) | Search engine testing method and device, electronic equipment and storage medium | |
| CN113177023B (en) | Log retrieval method and device and electronic equipment | |
| CN113744789B (en) | Method, system, equipment and medium for testing SSD stability in research and development stage | |
| CN110795297B (en) | Electronic equipment testing method and device | |
| CN110825648B (en) | Determination method and device for test script type, universal tester and storage medium | |
| CN117033215A (en) | Test data processing method and device for increment codes, electronic equipment and 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 |