CN108241571A - A kind of program testing method and device - Google Patents
A kind of program testing method and device Download PDFInfo
- Publication number
- CN108241571A CN108241571A CN201611207512.0A CN201611207512A CN108241571A CN 108241571 A CN108241571 A CN 108241571A CN 201611207512 A CN201611207512 A CN 201611207512A CN 108241571 A CN108241571 A CN 108241571A
- Authority
- CN
- China
- Prior art keywords
- test
- program
- state
- target
- tested
- 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
- 238000012360 testing method Methods 0.000 claims abstract description 219
- 206010048669 Terminal state Diseases 0.000 claims abstract description 22
- 238000000034 method Methods 0.000 claims description 20
- 230000007613 environmental effect Effects 0.000 claims description 2
- 238000010295 mobile communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 238000006467 substitution reaction 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—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
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 embodiment of the invention discloses a kind of program testing method and devices.The program testing method includes：S1. the SOT state of termination that terminal is presently in is obtained, using the SOT state of termination as dbjective state；S2. target program set is determined from program to be tested according to the dbjective state, the target program set includes at least one matcher, and state is identical with the first terminal state before the corresponding execution of the matcher；S3. simultaneously performance objective program is determined from least one matcher；S4. when the target program is finished, judgement tests whether to terminate；S5. if test does not terminate, state after the corresponding execution of the target program is obtained, and using state after the execution as the dbjective state, return and perform step S2, until discriminating test terminates.Program testing method and device provided by the invention by state are connected between each program, program are made to be traversed in state logic at random, improve test accuracy and covering scene range.
Description
Technical Field
The embodiment of the invention relates to the technical field of mobile communication testing, in particular to a program testing method and device.
Background
Currently, the software testing approach is mainly software stress testing, i.e. the maximum level of service that a system can provide is obtained by determining a bottleneck or unacceptable performance point of the system. The stress test in the wireless mobile communication test generally adopts two ways of increasing iteration times and running time.
In the prior art, when a wireless mobile communication system is tested, the test is completed based on the application environment and the realized service of the system, and the test is performed according to a preset flow, so that the test coverage range is narrow.
Disclosure of Invention
The invention provides a program testing method and a program testing device, which are used for testing a wireless mobile communication system and improving the testing accuracy and the coverage range of a scene.
In a first aspect, an embodiment of the present invention provides a program testing method, where the program testing method includes:
s1, acquiring a current terminal state of a terminal, and taking the terminal state as a target state;
s2, determining a target program set from programs to be tested according to the target state, wherein the target program set comprises at least one matching program, and the state before execution corresponding to the matching program is the same as the target state;
s3, determining and executing a target program from the at least one matching program;
s4, judging whether to finish the test or not when the target program is executed;
s5, if the test is not finished, acquiring the state after the execution corresponding to the target program, taking the state after the execution as the target state, and returning to the step of executing S2 until the test is judged to be finished.
Further, the determining whether to end the test includes:
acquiring the test coverage rate of the program to be tested;
and if the test coverage rate is greater than a preset coverage rate threshold value, judging to finish the test.
Further, the obtaining of the test coverage of the program to be tested includes:
recording the number of tested target programs and the total number of the programs to be tested;
and determining the test coverage rate according to the number of the target programs and the total amount of the programs to be tested.
Further, the determining whether to end the test includes:
if the total testing time length reaches a preset testing time length threshold value, judging to finish the test; or,
and acquiring the total testing times of the target program, and judging to finish the test if the total testing times reaches a preset testing time threshold value.
Further, before acquiring the current terminal state of the terminal at S1, the method further includes:
and acquiring a pre-execution state and a post-execution state corresponding to each program to be tested.
Further, the terminal is configured with the environmental parameters of the program to be tested.
In a second aspect, an embodiment of the present invention further provides a program testing apparatus, where the program testing apparatus includes:
the target state acquisition module is used for acquiring the current terminal state of the terminal and taking the terminal state as a target state;
the target program set determining module is used for determining a target program set from programs to be tested according to the target state, the target program set comprises at least one matching program, and the state before execution corresponding to the matching program is the same as the target state;
the target program determining module is used for determining and executing a target program from the at least one matching program;
the test ending judgment module is used for judging whether to end the test or not when the target program is executed;
and the after-execution state acquisition module is used for acquiring the after-execution state corresponding to the target program and taking the after-execution state as the target state if the test is not finished.
Further, the test termination judging module includes:
the test coverage rate obtaining submodule is used for obtaining the test coverage rate of the program to be tested;
and the test ending submodule is used for judging that the test is ended if the test coverage rate is greater than a preset coverage rate threshold value.
Further, the test coverage obtaining sub-module is configured to:
recording the number of tested target programs and the total number of the programs to be tested;
and determining the test coverage rate according to the number of the target programs and the total amount of the programs to be tested.
Further, the test termination judging module is configured to:
if the total testing time length reaches a preset testing time length threshold value, judging to finish the test; or,
and acquiring the total testing times of the target program, and judging to finish the test if the total testing times reaches a preset testing time threshold value.
According to the method and the device for testing the terminal, the current terminal state of the terminal is obtained, the terminal state is used as the target state, then the target program set is determined from the programs to be tested according to the target state, the target program set comprises at least one matching program, the state before execution corresponding to the matching program is the same as the target state, then the target program is determined and executed from the at least one matching program, when the target program is executed, whether the test is finished or not is judged, if the test is not finished, the state after execution corresponding to the target program is obtained, and the state after execution is used as the target state until the test is judged to be finished. In the prior art, when a wireless mobile communication system is tested, the test is completed based on the application environment and the realized service of the system, and the test is performed according to a preset flow, so that the test coverage range is narrow. In the application, all programs are linked randomly through states, so that the programs are traversed on state logic, a traditional preset scene or service is not provided, and the test accuracy and the scene coverage are improved.
Drawings
FIG. 1 is a flowchart of a program testing method according to one embodiment of the present invention;
FIG. 2 is a flowchart of a program testing method according to a second embodiment of the present invention;
FIG. 3 is a flowchart of a program testing method according to a third embodiment of the present invention;
FIG. 4 is a flowchart of a program testing method according to a third embodiment of the present invention;
FIG. 5 is a flowchart of a program testing method according to a fourth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a program testing apparatus according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a program testing method according to an embodiment of the present invention, where the method is applicable to a scenario of testing a mobile communication network subsystem in a virtual network environment, and the method may be executed by a terminal, where the terminal may be a desktop or a notebook computer. As shown in fig. 1, the program testing method specifically includes the following steps:
step 1, acquiring the current terminal state of the terminal, and taking the terminal state as a target state.
The terminal state may be a state set composed of a resident state of the terminal, a protocol state, a network environment, and the like. The stay state may include a normal state, an emergency state, etc.; the protocol states may include a Dedicated Channel (DCH) state, a Forward Access Channel (FACH) state, a Paging Channel (PCH) state, a Random Access Channel (RACH) state, and the like. Illustratively, the state set may be one set of state elements consisting of resident GSM cell1, idle state, CS registration success, PS registration success, and PDP inactivity, or another set of state elements consisting of resident TD cell1, idle, CS registration success, PS registration success, and PDP activity.
Under the application scene, after the test is started, the test script sends an AT command to control the mobile communication protocol stack to be started up by simulating the mobile communication network environment, so that the terminal enters a certain state, and the state of the terminal AT the moment is taken as a target state.
And 2, determining a target program set from the programs to be tested according to the target state, wherein the target program set comprises at least one matching program, and the state before execution corresponding to the matching program is the same as the target state.
The program to be tested may be all test cases or processes to be tested contained in the script to be tested, the number of the program to be tested is at least 1, and the program to be tested may have two attributes: a pre-execution state and a post-execution state. The target program set can be composed of the programs to be tested with the same state as the target state before execution, and the number of elements of the target program set can be 1 or more.
In the application scenario, the method for determining the target program set from the programs to be tested according to the target state may be to search matching programs with the same state as the target state before execution from all the programs to be tested, and combine the searched matching programs into the target program set.
And 3, determining and executing the target program from the at least one matching program.
Under the application scene, when only one matching program is included in the target program set, determining the matching program as a target program, and executing the target program; when the target program set comprises a plurality of matching programs, one of the matching programs is randomly selected to be determined as a target program, and the target program is executed.
And 4, judging whether to finish the test or not when the target program is completely executed.
In the application scenario, the method for judging whether to end the test may be to judge whether to end the test according to the test coverage of the program to be tested, and if the test coverage is greater than a preset coverage threshold, to judge to end the test; judging whether the test is finished or not according to the total test duration, and if the total test duration reaches a preset duration threshold, judging that the test is finished; or judging whether to finish the test according to the total test times of the target program, and if the total test times reaches a preset test time threshold, judging to finish the test. Optionally, the method for determining whether to end the test may be to end the test when an exception occurs during execution of the target program, where the exception may be that the target program is trapped in a loop during execution or that the target program cannot be executed due to a bug occurring in the target program.
And 5, if the test is not finished, acquiring the state after the execution corresponding to the target program, taking the state after the execution as the target state, and returning to the step 2 until the test is judged to be finished.
Under the application scene, when the target function is successfully executed and the condition of ending the test is not met, the executed state of the target program is taken as a new target state, the new target state is utilized to continuously search the target program set, and the test is carried out in a circulating mode until the test is judged to be ended.
Preferably, before step 1, the method comprises the following steps: and acquiring a pre-execution state and a post-execution state corresponding to each program to be tested.
Under the application scene, each program to be tested has two attributes of a pre-execution state and a post-execution state, and the pre-execution state and the post-execution state corresponding to each program to be tested are obtained, so that the target program set can be determined according to the target state, and the testing efficiency can be improved.
According to the technical scheme provided by the embodiment, the terminal state is taken as the target state by acquiring the current terminal state of the terminal, then the target program set is determined from the programs to be tested according to the target state, the target program set comprises at least one matching program, the state before execution corresponding to the matching program is the same as the target state, then the target program is determined and executed from the at least one matching program, when the target program is executed, whether the test is finished is judged, if the test is not finished, the state after execution corresponding to the target program is acquired, and the state after execution is taken as the target state until the test is judged to be finished. In the prior art, when a wireless mobile communication system is tested, the test is completed based on the application environment and the realized service of the system, and the test is performed according to a preset flow, so that the test coverage range is narrow. In the application, all programs are linked randomly through states, so that the programs are traversed on state logic, a traditional preset scene or service is not provided, and the test accuracy and the scene coverage are improved.
Example two
Fig. 2 is a flowchart of a program testing method according to a second embodiment of the present invention, based on the above-mentioned embodiment, as shown in fig. 2, step 4 includes:
step 401, obtaining the test coverage rate of the program to be tested.
Preferably, step 401 comprises: recording the number of tested target programs and the total number of the to-be-tested programs, and determining the test coverage rate according to the number of the target programs and the total number of the to-be-tested programs.
The test coverage may be a ratio of the number of executed target programs to the total number of all programs to be tested, and for example, assuming that the total number of programs to be tested is 90 and the number of executed target programs is 50, the test coverage is 55.5% obtained by dividing 90 by 50.
And step 402, if the test coverage rate is greater than a preset coverage rate threshold, ending the test.
The preset coverage threshold may be determined according to the actual test accuracy, and may be any percentage between 80% and 100%, for example. For example, assuming that the preset coverage threshold is set to 90%, after the terminal executes an object program, the terminal calculates the test coverage in the process from the start of the test to the completion of the execution of the object program, if the coverage is 90.2%, the test is ended, and if the coverage is 80%, the test is continued.
According to the technical scheme provided by the embodiment, the test coverage rate of the program to be tested is obtained, and if the test coverage rate is greater than the preset coverage rate threshold value, the test is judged to be finished. The test coverage rate is used as a test finishing condition, so that resources are saved on the basis that the test meets the precision.
EXAMPLE III
Fig. 3 is a flowchart of a program testing method according to a third embodiment of the present invention, based on the above-mentioned embodiment, as shown in fig. 3, step 4 includes:
step 403, the total duration is tested.
And step 404, if the total testing time length reaches a preset testing time length threshold value, judging that the test is ended.
The total test duration may be a total time taken from the start of the test to the last time an object program is executed, and the preset test duration threshold may be determined according to a test experience value, and may be any time length, such as 3 hours, 5 hours, and the like.
Fig. 4 is a flowchart of a program testing method according to a third embodiment of the present invention, and as shown in fig. 4, step 4 further includes:
step 405, acquiring the total test times of the target program.
Step 406, if the total number of tests reaches the preset test number threshold, determining to end the test.
The total number of tests may be the number of times of executing all target programs, and for example, from the start of the test to the current time, the total number of times of executing the program a is 3 times, the program B is 2 times, the program C is 5 times, the program D is 1 time, and the program H is 4 times, so that the total number of times of testing the target program is 15. The preset number of tests threshold may be determined according to the actual test scale, and may be set to 1 ten thousand times, for example.
According to the technical scheme provided by the embodiment, if the total testing time reaches the preset testing time threshold, the test is judged to be finished, or the total testing times of the target program are obtained, and if the total testing times reaches the preset testing time threshold, the test is judged to be finished. The total testing time is used as the testing finishing condition, so that the time is saved on the basis that the testing meets the precision, the total testing times is used as the testing finishing condition, the scale required by the testing can be met, and the testing precision can be improved.
Preferably, the environment parameters of the program to be tested are configured in the terminal, and the method can be applied to the program testing methods provided in the first, second and third embodiments.
Under the application scene, when the environment of the network side needs to be simulated, the environment parameters of the terminal are configured into the same environment variable as the environment variable of the network side, and then the test scene is selected in a self-adaptive mode. Illustratively, if a communication scenario of a router in a network node needs to be tested, the environment parameter of a terminal is configured into the same environment parameter as the router and then the router is tested, so that the environment test of the router can be realized without a real router for completing the test.
According to the technical scheme of the embodiment, the test scene can be selected in a self-adaptive manner under the environment of a simulation network side, the process is random, and the complexity of the test depth and the diversity of the test range are realized.
Example four
Fig. 5 is a flowchart of a program testing method according to a fourth embodiment of the present invention, based on the foregoing embodiment, as shown in fig. 5, the program testing method includes:
and step 410, acquiring the current terminal state of the terminal, and taking the terminal state as a target state.
Step 420, determining a target program set from the programs to be tested according to the target state, wherein the target program set comprises at least one matching program, and the state before execution corresponding to the matching program is the same as the target state.
And step 430, determining and executing the target program from the at least one matching program.
Step 440, determine whether the test is completed normally.
Step 450, if the test is completed normally, determining whether the test coverage is greater than a preset coverage threshold.
Step 460, if the test coverage is less than or equal to the preset coverage threshold, determining whether the total test duration reaches the preset test duration threshold.
Step 470, if the total testing duration does not reach the preset testing duration threshold, determining whether the total testing times reaches the preset testing times threshold.
And step 480, when the test is abnormal or the test coverage rate is greater than the preset coverage rate threshold value or the total test time length reaches the preset test time length threshold value or the total test times reaches the preset test time number threshold value, ending the test.
EXAMPLE five
Fig. 6 is a schematic structural diagram of a program testing apparatus according to a fifth embodiment of the present invention, as shown in fig. 6, the program testing apparatus includes: a target state obtaining module 510, a target program set determining module 520, a target program determining module 530, an end test judging module 540, an after-execution state obtaining module 550, a test coverage obtaining sub-module 541, and an end test sub-module 542.
A target state obtaining module 510, configured to obtain a terminal state where the terminal is currently located, and use the terminal state as a target state;
a target program set determining module 520, configured to determine a target program set from the programs to be tested according to the target state, where the target program set includes at least one matching program, and a state before execution corresponding to the matching program is the same as the target state;
a target program determining module 530 for determining and executing a target program from the at least one matching program;
a test ending judgment module 540, configured to judge whether to end the test when the target program is executed;
the post-execution state obtaining module 550 is configured to, if the test is not finished, obtain a post-execution state corresponding to the target program, and use the post-execution state as the target state.
Preferably, the test ending judging module 540 includes:
a test coverage obtaining submodule 541 configured to obtain a test coverage of a program to be tested;
and an end test submodule 542, configured to determine to end the test if the test coverage is greater than a preset coverage threshold.
Preferably, the test coverage obtaining sub-module 541 is configured to:
recording the number of tested target programs and the total amount of the programs to be tested;
and determining the test coverage rate according to the number of the target programs and the total amount of the programs to be tested.
Preferably, the end test determining module 540 is configured to:
if the total testing time length reaches a preset testing time length threshold value, judging to finish the test; or,
and acquiring the total test times of the target program, and judging to finish the test if the total test times reaches a preset test time threshold value.
The device can execute the methods provided by all the embodiments of the invention, and has corresponding functional modules and beneficial effects for executing the methods. For details not described in detail in this embodiment, reference may be made to the methods provided in all the foregoing embodiments of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A program testing method, comprising:
s1, acquiring a current terminal state of a terminal, and taking the terminal state as a target state;
s2, determining a target program set from programs to be tested according to the target state, wherein the target program set comprises at least one matching program, and the state before execution corresponding to the matching program is the same as the target state;
s3, determining and executing a target program from the at least one matching program;
s4, judging whether to finish the test or not when the target program is executed;
s5, if the test is not finished, acquiring the state after the execution corresponding to the target program, taking the state after the execution as the target state, and returning to the step of executing S2 until the test is judged to be finished.
2. The method of claim 1, wherein the determining whether to end the test comprises:
acquiring the test coverage rate of the program to be tested;
and if the test coverage rate is greater than a preset coverage rate threshold value, judging that the test is finished.
3. The method of claim 2, wherein said obtaining test coverage of said program under test comprises:
recording the number of tested target programs and the total number of the programs to be tested;
and determining the test coverage rate according to the number of the target programs and the total amount of the programs to be tested.
4. The method of claim 1, wherein the determining whether to end the test comprises:
if the total testing time length reaches a preset testing time length threshold value, judging to finish the test; or,
and acquiring the total testing times of the target program, and judging to finish the test if the total testing times reaches a preset testing time threshold value.
5. The method according to claim 1, before obtaining the terminal state currently located by the terminal at S1, further comprising:
and acquiring a pre-execution state and a post-execution state corresponding to each program to be tested.
6. Method according to any of claims 1-4, characterized in that the environmental parameters of the program to be tested are configured in the terminal.
7. A program test apparatus, comprising:
the target state acquisition module is used for acquiring the current terminal state of the terminal and taking the terminal state as a target state;
the target program set determining module is used for determining a target program set from programs to be tested according to the target state, the target program set comprises at least one matching program, and the state before execution corresponding to the matching program is the same as the target state;
the target program determining module is used for determining and executing a target program from the at least one matching program;
the test ending judgment module is used for judging whether to end the test or not when the target program is executed;
and the after-execution state acquisition module is used for acquiring the after-execution state corresponding to the target program and taking the after-execution state as the target state if the test is not finished.
8. The apparatus of claim 7, wherein the end-of-test determining module comprises:
the test coverage rate obtaining submodule is used for obtaining the test coverage rate of the program to be tested;
and the test ending submodule is used for judging that the test is ended if the test coverage rate is greater than a preset coverage rate threshold value.
9. The apparatus of claim 8, wherein the test coverage acquisition sub-module is configured to:
recording the number of tested target programs and the total number of the programs to be tested;
and determining the test coverage rate according to the number of the target programs and the total amount of the programs to be tested.
10. The apparatus of claim 7, wherein the end-of-test determining module is configured to:
if the total testing time length reaches a preset testing time length threshold value, judging to finish the test; or,
and acquiring the total testing times of the target program, and judging to finish the test if the total testing times reaches a preset testing time threshold value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611207512.0A CN108241571A (en) | 2016-12-23 | 2016-12-23 | A kind of program testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611207512.0A CN108241571A (en) | 2016-12-23 | 2016-12-23 | A kind of program testing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108241571A true CN108241571A (en) | 2018-07-03 |
Family
ID=62704180
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611207512.0A Pending CN108241571A (en) | 2016-12-23 | 2016-12-23 | A kind of program testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108241571A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109471663A (en) * | 2018-10-30 | 2019-03-15 | 珠海格力智能装备有限公司 | Method and device for executing single chip microcomputer program |
| CN110209593A (en) * | 2019-06-14 | 2019-09-06 | 南京大学 | A kind of Android application testing method towards preference setting |
| CN111326205A (en) * | 2018-12-14 | 2020-06-23 | 长鑫存储技术有限公司 | Test system, test method and test device for memory |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1431598A (en) * | 2002-01-11 | 2003-07-23 | 互慧科技股份有限公司 | Program test system and method |
| US7137103B2 (en) * | 2001-03-08 | 2006-11-14 | International Business Machines Corporation | Coverage analysis of message flows |
| CN101464829A (en) * | 2007-12-18 | 2009-06-24 | 珠海金山软件股份有限公司 | Method and test device for confirming code coverage rate |
| CN102087631A (en) * | 2011-03-09 | 2011-06-08 | 中国人民解放军国发科学技术大学 | Method for realizing fuzzing of software on the basis of state protocol |
| US20150293837A1 (en) * | 2014-04-14 | 2015-10-15 | International Business Machines Corporation | Risk-based test coverage and prioritization |
| CN105930271A (en) * | 2016-04-21 | 2016-09-07 | 惠州Tcl移动通信有限公司 | Java program running code coverage rate test method and system |
-
2016
- 2016-12-23 CN CN201611207512.0A patent/CN108241571A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7137103B2 (en) * | 2001-03-08 | 2006-11-14 | International Business Machines Corporation | Coverage analysis of message flows |
| CN1431598A (en) * | 2002-01-11 | 2003-07-23 | 互慧科技股份有限公司 | Program test system and method |
| CN101464829A (en) * | 2007-12-18 | 2009-06-24 | 珠海金山软件股份有限公司 | Method and test device for confirming code coverage rate |
| CN102087631A (en) * | 2011-03-09 | 2011-06-08 | 中国人民解放军国发科学技术大学 | Method for realizing fuzzing of software on the basis of state protocol |
| US20150293837A1 (en) * | 2014-04-14 | 2015-10-15 | International Business Machines Corporation | Risk-based test coverage and prioritization |
| CN105930271A (en) * | 2016-04-21 | 2016-09-07 | 惠州Tcl移动通信有限公司 | Java program running code coverage rate test method and system |
Non-Patent Citations (1)
| Title |
|---|
| 吴恒山等: "基于界面状态有效性的GUI自动测试模型", 《华中科技大学学报(自然科学版)》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109471663A (en) * | 2018-10-30 | 2019-03-15 | 珠海格力智能装备有限公司 | Method and device for executing single chip microcomputer program |
| CN109471663B (en) * | 2018-10-30 | 2022-04-05 | 珠海格力智能装备有限公司 | Method and device for executing single chip microcomputer program |
| CN111326205A (en) * | 2018-12-14 | 2020-06-23 | 长鑫存储技术有限公司 | Test system, test method and test device for memory |
| CN111326205B (en) * | 2018-12-14 | 2022-03-22 | 长鑫存储技术有限公司 | Test system, test method and test device for memory |
| CN110209593A (en) * | 2019-06-14 | 2019-09-06 | 南京大学 | A kind of Android application testing method towards preference setting |
| CN110209593B (en) * | 2019-06-14 | 2021-05-28 | 南京大学 | A preference-oriented Android application testing method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107562610B (en) | Method, device, terminal and medium for acquiring page loading time | |
| CN109885499B (en) | Robot automatic test system and test method | |
| CN106888060B (en) | Anti-interference test method and system for wireless communication module | |
| CN107391373B (en) | AutoIT-based automatic performance testing method | |
| CN108241571A (en) | A kind of program testing method and device | |
| CN110688319B (en) | Application keep-alive capability test method and related device | |
| CN112100085B (en) | Android application stability testing method, apparatus and device | |
| CN107621963B (en) | Software deployment method, software deployment system and electronic equipment | |
| CN109218136B (en) | WIFI connection performance test method and device, computer equipment and storage medium | |
| CN109491360B (en) | Simulation test method, device and system of vehicle control unit and electronic equipment | |
| CN114816956A (en) | Interface performance test method and device | |
| CN113836032B (en) | Android interface concurrent testing method, device, equipment and storage medium | |
| CN108572892B (en) | PowerPC multi-core processor-based offline test method and device | |
| CN111488278A (en) | Test method and device | |
| CN110750453A (en) | HTML 5-based intelligent mobile terminal testing method, system, server and storage medium | |
| CN109726124A (en) | Test macro, test method, managing device, test device and calculating equipment | |
| CN103902903A (en) | Malicious code analyzing method and system based on dynamic sandbox environment | |
| CN111949548A (en) | Automatic unauthorized penetration testing method and storage device | |
| CN116069504B (en) | Scheduling method and device for multi-core processor in automatic driving simulation | |
| CN106648895A (en) | Data processing method and device, and terminal | |
| CN117742999A (en) | Method and device for testing system | |
| US9264923B1 (en) | Signal segmentation, event recognition, extraction and classification for emulating wireless network | |
| CN115327953B (en) | Simulation test method and device for intelligent driving algorithm, electronic equipment and medium | |
| CN109788518A (en) | The method for tracing and device of mobile terminal | |
| CN113885052B (en) | Beidou positioning terminal electromagnetic compatibility test method, system, 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180703 |