CN105138450A - Software stability testing method and device - Google Patents
Software stability testing method and device Download PDFInfo
- Publication number
- CN105138450A CN105138450A CN201510462960.4A CN201510462960A CN105138450A CN 105138450 A CN105138450 A CN 105138450A CN 201510462960 A CN201510462960 A CN 201510462960A CN 105138450 A CN105138450 A CN 105138450A
- Authority
- CN
- China
- Prior art keywords
- case
- target detection
- test
- detection use
- software
- 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
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a software stability testing method and device. The software stability testing method comprises the following steps: judging whether the test starting time of the current test period is reached; when the test starting time reaching the current test period is judged, at least one random identification is obtained, a test case with a case identification identical to the obtained random identification in a pre-constructed test case set is determined to be a target test case to be tested in the current test period, the determined target test case is executed aiming at software to be tested, and an execution result corresponding to the target test case is determined, wherein the test case set comprises a plurality of test cases related to the software to be tested, and each test case uniquely corresponds to one case identification; and when the preset test ending condition is detected to be met, determining the stability of the software to be tested according to the execution result of each executed target test case. The efficiency of software stability test can be improved through the scheme.
Description
Technical field
The present invention relates to software testing technology field, particularly relate to software stability method of testing and device.
Background technology
Before software metric tools, usually can carry out software test, wherein, software stability test is wherein a kind of comparatively general test.
In prior art, software stability method of testing comprises pure random testing method and robotization use-case order manner of execution.Wherein, so-called pure random testing method is: send out keyboard various and mouse information and no matter whether software is to these message responses to the software as tested object randomly, keyboard and the mouse information of this test overwhelming majority have all been automatically ignored, and the efficient of stability test is extremely low; And so-called robotization use-case order manner of execution is: test case is performed for more than times by proper sequence, this situation software can respond the automation mechanized operation of the overwhelming majority, but the execution due to test case is fixing, so the problem that can expose also is very limited.
Summary of the invention
The object of the embodiment of the present invention is to provide software stability method of testing and device, to improve the efficient of software stability test.Concrete technical scheme is as follows:
First aspect, embodiments provides a kind of software stability method of testing, comprising:
Judge whether the test starting moment reaching current test period;
When judging the test starting moment reaching current test period, obtain at least one random identification, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, the target detection use-case determined is performed for software to be tested, and determine the execution result corresponding to described target detection use-case, wherein, described test case set comprises the multiple test cases relevant to described software to be tested, the unique corresponding use-case mark of each test case,
When detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determine the stability of described software to be tested.
Optionally, describedly perform the target detection use-case determined for software to be tested, comprising:
Successively using each target detection use-case as current pending target detection use-case;
After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, perform the current pending scheduled operation corresponding to target detection use-case, and after described scheduled operation is finished, perform current pending target detection use-case for described software to be tested;
Wherein, the current pending scheduled operation corresponding to target detection use-case for: by being performed the operation making the executive condition corresponding to current pending target detection use-case be satisfied.
Optionally, describedly perform the target detection use-case determined for software to be tested, comprising:
Successively using each target detection use-case as current pending target detection use-case;
After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, the execution of described current pending target detection use-case is skipped.
Optionally, at least one random identification of described acquisition, comprising:
Utilize pre-determined random to identify generating function, generate at least one random identification.
Optionally, at least one random identification of described acquisition, comprising:
From the digital collection built in advance, at least one random identification of Stochastic choice.
Optionally, described presumptive test termination condition comprises:
The test period preset all terminates, or the number of times of performance objective test case reaches pre-determined number threshold value.
Optionally, described presumptive test termination condition comprises:
Receive the test END instruction that user sends.
Second aspect, the embodiment of the present invention additionally provides a kind of software stability proving installation, comprising:
Judge module, stability test module and stability determination module, wherein, described stability test module comprises: random identification obtains submodule, use-case determination submodule, use-case implementation sub-module and execution result determination submodule;
Wherein, described judge module, for judging whether the test starting moment reaching current test period;
Described random identification obtains submodule, for when judging the test starting moment reaching current test period, obtains at least one random identification;
Described use-case determination submodule, for the test case that use-case mark in the test case set that will build in advance is identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, wherein, described test case set comprises the multiple test cases relevant to software to be tested, the unique corresponding use-case mark of each test case;
Described use-case implementation sub-module, for performing for described software to be tested the target detection use-case determined;
Described execution result determination submodule, for determining the execution result corresponding to described target detection use-case;
Described stability determination module, for when detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determines the stability of described software to be tested.
Optionally, described use-case implementation sub-module comprises:
First use-case performance element, for successively using each target detection use-case as current pending target detection use-case; After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, perform the current pending scheduled operation corresponding to target detection use-case, and after described scheduled operation is finished, perform current pending target detection use-case for described software to be tested;
Wherein, the current pending scheduled operation corresponding to target detection use-case for: by being performed the operation making the executive condition corresponding to current pending target detection use-case be satisfied.
Optionally, described use-case implementation sub-module comprises:
Second use-case performance element, for successively using each target detection use-case as current pending target detection use-case; After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, the execution of described current pending target detection use-case is skipped.
Optionally, described random identification acquisition submodule comprises:
First random identification obtains unit, for when judging to reach the trigger instants about the presumptive test period of software, utilizing pre-determined random to identify generating function, generating at least one random identification.
Optionally, described random identification acquisition submodule comprises:
Second random identification obtains unit, for when judging to reach the trigger instants about the presumptive test period of software, from the digital collection built in advance, and at least one random identification of Stochastic choice.
Optionally, the presumptive test termination condition that described stability determination module detects comprises:
The test period preset all terminates, or the number of times of performance objective test case reaches pre-determined number threshold value.
Optionally, the presumptive test termination condition that described stability determination module detects comprises:
Receive the test END instruction that user sends.
In the software stability method of testing that the embodiment of the present invention provides, when judging the test starting moment reaching current test period, obtain at least one random identification, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, perform the target detection use-case determined for software to be tested, and determine the execution result corresponding to target detection use-case; When detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determine the stability of this software.Compared with prior art, the test case of this programme periodically in random implementation of test cases set, merge pure random testing method and robotization use-case order manner of execution, the drawback that single method of testing can be avoided to bring, reaches the efficient object improving software stability test.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
The process flow diagram of the software stability method of testing that Fig. 1 provides for the embodiment of the present invention;
The structural representation of the software stability proving installation that Fig. 2 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
In order to solve prior art problem, embodiments provide software stability method of testing and device, to improve the efficient of software stability test.
First the software stability method of testing that the embodiment of the present invention provides is introduced below.
Wherein, the software stability method of testing that the embodiment of the present invention provides for software can be the software of any a existence and stability testing requirement, such as: instrumental software, audio-visual audiovisual software, chat and social software, office software etc.In addition, the executive agent of the software stability method of testing that the embodiment of the present invention provides can be software stability proving installation, in actual applications, this software stability proving installation can for carrying out the functional software of software stability test specially, also can for being built in the plug-in unit of software to be tested, this is all rational.
It should be noted that, before a certain software stability test starts, the test case set of this software to be tested can be built in advance, this test case set comprises the relevant multiple test cases of software to be tested to this, the unique corresponding use-case mark of each test case, wherein, the quantity of the test case in test case set can set according to actual conditions, such as: 20,30,50 etc., and this use-case mark can belong to letter type, as a, b, c, d etc., or, numeric type, as 1,2,3,4,5 etc., this is all rational.And, because the test case in test case set is relevant to software to be tested, therefore, for different software to be tested, corresponding test case set can be different, which test case of concrete employing is determined according to concrete software, and in addition, the dependence between the test case in test case set is usually less.Be understandable that, the set of the so-called test case of structure in advance refers to from codes implement writes the automatized script that simulation is directed to the operation of software to be tested, the corresponding test case of each operation in advance.
For example: for browser as software to be tested, test case can for a newly-built label, close a label, collection page, download a file, the QQ space (whether test is default browser) clicked on QQ panel; And for chat with social software as software to be tested, test case can for opening chat window, closing chat window, minimize panel, showing buddy list etc.
As shown in Figure 1, a kind of software stability method of testing, can comprise the steps:
S101, judges whether the test starting moment reaching current test period, if so, performs S102; Otherwise, do not deal with;
In the embodiment of the present invention, software steady testing is periodically test, therefore, can judge whether the test starting moment reaching current period within each cycle, and then performing different operations according to different judged results, the test of this periodicity at least can comprise two cycles.Concrete, when judging the test starting moment reaching current test period, can S102 be performed, and when judging the test starting moment not reaching current test period, can not deal with.
Wherein, for each test period, the test starting moment can be start time of test period, also can be the moment in test period except start time.
S102, obtain at least one random identification, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, perform the target detection use-case determined for software to be tested, and determine this execution result corresponding to target detection use-case;
Wherein, when judging the test starting moment reaching current test period, the test in current test period can be performed, concrete, can by specific mode, obtain at least one random identification, and then, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, the target detection use-case determined is performed for this software to be tested, and determine this execution result corresponding to target detection use-case, wherein, the execution result of target detection use-case can comprise and is effectively executed and cannot be performed.Wherein, at least one random identification obtained is the use-case mark of the test case in the test case set built in advance, and, the type belonging at least one random identification obtained is consistent with the type that use-case identifies, concrete, when use-case is designated numeric type, random identification is numeric type, and when use-case is designated letter type, random identification is letter type.
Concrete, in one implementation, at least one random identification of described acquisition, can comprise: utilize pre-determined random to identify generating function, generate at least one random identification; Or, from the digital collection built in advance, at least one random identification of Stochastic choice.Be understandable that, pre-determined random mark generating function can utilize prior art to generate, and does not limit at this.In addition, obtain at least one random identification concrete quantity can determine according to the quantity of the test case in test case set, such as, obtain at least one random identification concrete quantity be 1/4th, 1/3rd of the quantity of test case in test case set etc., this is all rational.
S103, when detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determines the stability of this software to be tested.
In software stability test process, when detecting that presumptive test termination condition is satisfied, can according to the execution result of each target detection use-case executed, determine the stability of this software to be tested, wherein, prior art can be adopted realize the stability determining software to be tested according to the execution result of each target detection use-case executed, for example: in the test case be performed, execution result be effectively executed account for more than 80%, then determine that this software to be tested is stable, otherwise, determine that this software to be tested is for unstable, etc.
Concrete, described presumptive test termination condition can comprise: the test period preset all terminates, or the number of times of performance objective test case reaches pre-determined number threshold value, or, receive the test END instruction that user sends.Wherein, the test period preset can be 10 cycles, 15 cycles, 20 cycles etc., and this pre-determined number threshold value can be 300 times, for 200 times etc.
In one embodiment, in order to improve the efficient of stability test further, can ensure that each test case goes when the executive condition of correspondence is satisfied to be performed, based on this demand, describedly perform the target detection use-case determined for software to be tested, can comprise:
Successively using each target detection use-case as current pending target detection use-case;
After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for this software to be tested; If not, perform the current pending scheduled operation corresponding to target detection use-case, and after this scheduled operation is finished, perform current pending target detection use-case for this software to be tested;
Wherein, the current pending scheduled operation corresponding to target detection use-case for: by being performed the operation making the executive condition corresponding to current pending target detection use-case be satisfied.
Be understandable that, without the need to prerequisite when some test case is performed, and some test case is performed the specific prerequisite of needs, based on this situation, before current pending target detection use-case is performed, can judge whether the current pending executive condition corresponding to target detection use-case is satisfied, wherein, for some test case without the need to prerequisite, corresponding executive condition can be empty; And, corresponding to different test cases can be different by being performed the scheduled operation that can meet executive condition, for example: if test case is closedown Shipping Options Page, then corresponding executive condition is show a Shipping Options Page in browser, and corresponding scheduled operation can be a newly-built Shipping Options Page; And if test case is click the QQ space on QQ panel, then corresponding executive condition be QQ panel in being transferred out state, corresponding scheduled operation can for recalling QQ panel.
The executive condition of current pending target detection use-case it should be noted that, if after scheduled operation is performed, still cannot be satisfied, then can ignore current pending target detection use-case.
In another kind of embodiment, in order to improve the efficient of stability test further, can ensure that the test case be performed is the test case meeting corresponding executive condition, based on this demand, describedly perform the target detection use-case determined for software to be tested, can comprise:
Successively using each target detection use-case as current pending target detection use-case;
After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for this software to be tested; If not, the execution of this current pending target detection use-case is skipped.
In the software stability method of testing that the embodiment of the present invention provides, when judging the test starting moment reaching current test period, obtain at least one random identification, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, perform the target detection use-case determined for software to be tested, and determine this execution result corresponding to target detection use-case; When detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determine the stability of this software to be tested.Compared with prior art, the test case of this programme periodically in random implementation of test cases set, merge pure random testing method and robotization use-case order manner of execution, the drawback that single method of testing can be avoided to bring, reaches the efficient object improving software stability test.
Below in conjunction with specific embodiment, the software stability method of testing that the embodiment of the present invention provides is introduced.
Suppose the test stability test of browser being comprised to 10 test periods, be built with test case set in advance, test case set comprises 5 test cases, the use-case of each test case mark by Digital ID, the use-case mark of 5 test cases and particular content as follows:
1, a page is opened
2, a file is downloaded
3, a newly-built label
4, a label is closed
5, the QQ space (test default browser) on QQ panel is clicked
Wherein, the use-case mark of 5 test cases is respectively 1,2,3,4,5.
In the stability test process of browser, if when judging the test starting moment reaching current test period, any one integer between a 1-5 is generated by random function, being assumed to be generated integer is 5, now, it is the target detection use-case that the test case in the QQ space clicked on QQ panel is defined as in current period by content, further, judge that QQ panel is not transferred out, after then calling QQ panel, perform for this browser the target detection use-case that content is the QQ space clicked on QQ panel, and determine execution result.
Periodically perform above-mentioned process, after detecting that 10 test periods all terminate, according to the execution result of each target detection use-case executed, determine the stability of browser.
Visible, the test case of this programme periodically in random implementation of test cases set, merge pure random testing method and robotization use-case order manner of execution, the drawback that single method of testing can be avoided to bring, reach raising software stability and test efficient object.
Corresponding to said method embodiment, the embodiment of the present invention additionally provides a kind of software stability proving installation, as shown in Figure 2, can comprise:
Judge module 210, stability test module 220 and stability determination module 230, wherein, described stability test module 220 comprises: random identification obtains submodule 221, use-case determination submodule 222, use-case implementation sub-module 223 and execution result determination submodule 224;
Wherein, described judge module 210, for judging whether the test starting moment reaching current test period;
Described random identification obtains submodule 221, for when judging the test starting moment reaching current test period, obtains at least one random identification;
Described use-case determination submodule 222, for the test case that use-case mark in the test case set that will build in advance is identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, wherein, described test case set comprises the multiple test cases relevant to software to be tested, the unique corresponding use-case mark of each test case;
Described use-case implementation sub-module 223, for performing for described software to be tested the target detection use-case determined;
Described execution result determination submodule 224, for determining the execution result corresponding to described target detection use-case;
Described stability determination module 230, for when detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determines the stability of described software to be tested.
In the software stability method of testing that the embodiment of the present invention provides, when judging the test starting moment reaching current test period, obtain at least one random identification, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, perform for this software to be tested the target detection use-case determined, and determine this execution result corresponding to target detection use-case; When detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determine the stability of this software to be tested.Compared with prior art, the test case of this programme periodically in random implementation of test cases set, merge pure random testing method and robotization use-case order manner of execution, the drawback that single method of testing can be avoided to bring, reaches the efficient object improving software stability test.
In one embodiment, efficient in order to improve test further, in one implementation, described use-case implementation sub-module 223 can comprise:
First use-case performance element, for successively using each target detection use-case as current pending target detection use-case; After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, perform the current pending scheduled operation corresponding to target detection use-case, and after described scheduled operation is finished, perform current pending target detection use-case for described software to be tested;
Wherein, the current pending scheduled operation corresponding to target detection use-case for: by being performed the operation making the executive condition corresponding to current pending target detection use-case be satisfied.
In another kind of embodiment, efficient in order to improve test further, in another kind of implementation, described use-case implementation sub-module 223 can comprise:
Second use-case performance element, for successively using each target detection use-case as current pending target detection use-case; After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, the execution of described current pending target detection use-case is skipped.
Concrete, described random identification obtains submodule 221 and can comprise:
First random identification obtains unit, for when judging to reach the trigger instants about the presumptive test period of software, utilizing pre-determined random to identify generating function, generating at least one random identification.
Concrete, described random identification obtains submodule 221 and can comprise:
Second random identification obtains unit, for when judging to reach the trigger instants about the presumptive test period of software, from the digital collection built in advance, and at least one random identification of Stochastic choice.
Concrete, the presumptive test termination condition that described stability determination module 230 detects comprises:
The test period preset all terminates, or the number of times of performance objective test case reaches pre-determined number threshold value.
Concrete, the presumptive test termination condition that described stability determination module 230 detects comprises:
Receive the test END instruction that user sends.
It should be noted that, in this article, the such as relational terms of first and second grades and so on is only used for an entity or operation to separate with another entity or operational zone, and not necessarily requires or imply the relation that there is any this reality between these entities or operation or sequentially.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thus make to comprise the process of a series of key element, method, article or equipment and not only comprise those key elements, but also comprise other key elements clearly do not listed, or also comprise by the intrinsic key element of this process, method, article or equipment.When not more restrictions, the key element limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment comprising described key element and also there is other identical element.
Each embodiment in this instructions all adopts relevant mode to describe, between each embodiment identical similar part mutually see, what each embodiment stressed is the difference with other embodiments.Especially, for system embodiment, because it is substantially similar to embodiment of the method, so description is fairly simple, relevant part illustrates see the part of embodiment of the method.
The foregoing is only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.All any amendments done within the spirit and principles in the present invention, equivalent replacement, improvement etc., be all included in protection scope of the present invention.
Claims (10)
1. a software stability method of testing, is characterized in that, comprising:
Judge whether the test starting moment reaching current test period;
When judging the test starting moment reaching current test period, obtain at least one random identification, use-case in the test case set built in advance is identified the test case identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, the target detection use-case determined is performed for software to be tested, and determine the execution result corresponding to described target detection use-case, wherein, described test case set comprises the multiple test cases relevant to described software to be tested, the unique corresponding use-case mark of each test case,
When detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determine the stability of described software to be tested.
2. method according to claim 1, is characterized in that, describedly performs the target detection use-case determined for software to be tested, comprising:
Successively using each target detection use-case as current pending target detection use-case;
After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, perform the current pending scheduled operation corresponding to target detection use-case, and after described scheduled operation is finished, perform current pending target detection use-case for described software to be tested;
Wherein, the current pending scheduled operation corresponding to target detection use-case for: by being performed the operation making the executive condition corresponding to current pending target detection use-case be satisfied.
3. method according to claim 1, is characterized in that, describedly performs the target detection use-case determined for software to be tested, comprising:
Successively using each target detection use-case as current pending target detection use-case;
After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, the execution of described current pending target detection use-case is skipped.
4. the method according to claim 1-3 any one, is characterized in that, at least one random identification of described acquisition, comprising:
Utilize pre-determined random to identify generating function, generate at least one random identification.
5. the method according to claim 1-3 any one, is characterized in that, described presumptive test termination condition comprises:
The test period preset all terminates, or the number of times of performance objective test case reaches pre-determined number threshold value.
6. a software stability proving installation, is characterized in that, comprising:
Judge module, stability test module and stability determination module, wherein, described stability test module comprises: random identification obtains submodule, use-case determination submodule, use-case implementation sub-module and execution result determination submodule;
Wherein, described judge module, for judging whether the test starting moment reaching current test period;
Described random identification obtains submodule, for when judging the test starting moment reaching current test period, obtains at least one random identification;
Described use-case determination submodule, for the test case that use-case mark in the test case set that will build in advance is identical with obtained random identification, be defined as the target detection use-case to be tested in current test period, wherein, described test case set comprises the multiple test cases relevant to software to be tested, the unique corresponding use-case mark of each test case;
Described use-case implementation sub-module, for performing for described software to be tested the target detection use-case determined;
Described execution result determination submodule, for determining the execution result corresponding to described target detection use-case;
Described stability determination module, for when detecting that presumptive test termination condition is satisfied, according to the execution result of each target detection use-case executed, determines the stability of described software to be tested.
7. device according to claim 6, is characterized in that, described use-case implementation sub-module comprises:
First use-case performance element, for successively using each target detection use-case as current pending target detection use-case; After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, perform the current pending scheduled operation corresponding to target detection use-case, and after described scheduled operation is finished, perform current pending target detection use-case for described software to be tested;
Wherein, the current pending scheduled operation corresponding to target detection use-case for: by being performed the operation making the executive condition corresponding to current pending target detection use-case be satisfied.
8. device according to claim 6, is characterized in that, described use-case implementation sub-module comprises:
Second use-case performance element, for successively using each target detection use-case as current pending target detection use-case; After determining each current pending target detection use-case, judge whether the current pending executive condition corresponding to target detection use-case is satisfied, if so, perform current pending target detection use-case for described software to be tested; If not, the execution of described current pending target detection use-case is skipped.
9. the device according to claim 6-8 any one, is characterized in that, described random identification obtains submodule and comprises:
First random identification obtains unit, for when judging to reach the trigger instants about the presumptive test period of software, utilizing pre-determined random to identify generating function, generating at least one random identification.
10. the device according to claim 6-8 any one, is characterized in that, the presumptive test termination condition that described stability determination module detects comprises:
The test period preset all terminates, or the number of times of performance objective test case reaches pre-determined number threshold value.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510462960.4A CN105138450A (en) | 2015-07-31 | 2015-07-31 | Software stability testing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510462960.4A CN105138450A (en) | 2015-07-31 | 2015-07-31 | Software stability testing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105138450A true CN105138450A (en) | 2015-12-09 |
Family
ID=54723804
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510462960.4A Pending CN105138450A (en) | 2015-07-31 | 2015-07-31 | Software stability testing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105138450A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109460366A (en) * | 2018-11-16 | 2019-03-12 | 郑州云海信息技术有限公司 | A kind of software stability test method, device, equipment and medium |
| CN110502422A (en) * | 2018-05-18 | 2019-11-26 | 海能达通信股份有限公司 | A kind of automatic test approach, test device and the device with store function |
| CN112131113A (en) * | 2020-09-23 | 2020-12-25 | 北京达佳互联信息技术有限公司 | Method for automatically testing special effect and electronic equipment |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1744056A (en) * | 2004-09-04 | 2006-03-08 | 华为技术有限公司 | Automatic test method of application |
| CN101620566A (en) * | 2009-07-23 | 2010-01-06 | 北京航空航天大学 | Dynamic random testing method |
| CN102521376A (en) * | 2011-12-20 | 2012-06-27 | 上海电机学院 | Method for simplifying software test case suite |
| CN103377104A (en) * | 2012-04-19 | 2013-10-30 | 腾讯科技（深圳）有限公司 | Test method and device |
| CN103473175A (en) * | 2013-09-11 | 2013-12-25 | 江苏中科梦兰电子科技有限公司 | Extraction method for software testing case set |
-
2015
- 2015-07-31 CN CN201510462960.4A patent/CN105138450A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1744056A (en) * | 2004-09-04 | 2006-03-08 | 华为技术有限公司 | Automatic test method of application |
| CN101620566A (en) * | 2009-07-23 | 2010-01-06 | 北京航空航天大学 | Dynamic random testing method |
| CN102521376A (en) * | 2011-12-20 | 2012-06-27 | 上海电机学院 | Method for simplifying software test case suite |
| CN103377104A (en) * | 2012-04-19 | 2013-10-30 | 腾讯科技（深圳）有限公司 | Test method and device |
| CN103473175A (en) * | 2013-09-11 | 2013-12-25 | 江苏中科梦兰电子科技有限公司 | Extraction method for software testing case set |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110502422A (en) * | 2018-05-18 | 2019-11-26 | 海能达通信股份有限公司 | A kind of automatic test approach, test device and the device with store function |
| CN109460366A (en) * | 2018-11-16 | 2019-03-12 | 郑州云海信息技术有限公司 | A kind of software stability test method, device, equipment and medium |
| CN112131113A (en) * | 2020-09-23 | 2020-12-25 | 北京达佳互联信息技术有限公司 | Method for automatically testing special effect and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109408102B (en) | Version comparison method and device, household electrical appliance and network equipment | |
| CN109521683B (en) | Control method, remote controller and control terminal of household electrical appliance in local area network | |
| CN103019936B (en) | Numerical control software testing system | |
| CN104980552B (en) | Realize the method and system of Android mobile terminal automatic test | |
| CN109117039B (en) | Display method and terminal equipment | |
| CN105138450A (en) | Software stability testing method and device | |
| CN103455403B (en) | Method of testing and device | |
| CN101482596B (en) | Fast fault recognition method for multifactor industrial system | |
| CN102222043A (en) | Testing method and testing device | |
| CN104461888A (en) | Application testing method and system | |
| CN105471935A (en) | Information prompting method and information prompting device | |
| CN104751053A (en) | Static behavior analysis method of mobile smart terminal software | |
| CN111934908A (en) | Internet of things simulation method, device and system and storage medium | |
| CN105025254A (en) | Multi-platform monitoring terminal system development method | |
| CN103809985A (en) | Method and system for generating software development program | |
| CN102622233A (en) | System and method for automatically generating user interface applicable to certain interactive terminal equipment | |
| CN104881350A (en) | Method and device for confirming user experience and method and device for assisting in user experience confirmation | |
| CN103955379B (en) | A kind of method and system for registering software | |
| CN106775268B (en) | Message display method and device | |
| CN112583617B (en) | Fault determination method, server, control terminal and storage medium | |
| CN104144076B (en) | A kind of flow process error control method, device and system | |
| CN104991781A (en) | Application software internal function recommendation method and device | |
| CN112306009B (en) | Control method and device of household appliance, electronic device and storage medium | |
| CN104142885A (en) | Method and device for carrying out abnormality test on tested program | |
| CN104639403A (en) | Method for calling IxChariot API (Application Program Interface) to test throughput |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into 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: 20151209 |