CN103049371A - Testing method and testing device of Android application programs - Google Patents
Testing method and testing device of Android application programs Download PDFInfo
- Publication number
- CN103049371A CN103049371A CN2012104418756A CN201210441875A CN103049371A CN 103049371 A CN103049371 A CN 103049371A CN 2012104418756 A CN2012104418756 A CN 2012104418756A CN 201210441875 A CN201210441875 A CN 201210441875A CN 103049371 A CN103049371 A CN 103049371A
- Authority
- CN
- China
- Prior art keywords
- test
- operation steps
- configuration values
- test case
- time
- 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 title claims abstract description 293
- 238000000034 method Methods 0.000 claims abstract description 33
- 230000009471 action Effects 0.000 claims description 26
- 238000012544 monitoring process Methods 0.000 claims description 7
- 230000008569 process Effects 0.000 abstract description 21
- 238000009434 installation Methods 0.000 description 24
- 241000282693 Cercopithecidae Species 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000010998 test method Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000013100 final test Methods 0.000 description 1
- 239000000796 flavoring agent Substances 0.000 description 1
- 235000019634 flavors Nutrition 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000013112 stability test Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a testing method and a testing device of Android application programs. The method comprises steps of analyzing configuration values of key words of various operation processes from a testing example; sequentially executing tests of operation processes in accordance with analyzed configuration values of the serial number of operation processes; and executing the test for an operation process as follows: calling an element operation tool, wherein element operation tool conducts corresponding operation for corresponding user interface (UI) elements of tested Android application programs in accordance with operation types and configuration values of operation objects of the operation process. Therefore, a tester can configure testing examples based on key words conveniently, conducts the analyzing through key words of testing examples and calls relative tools to operate UI elements of tested application programs, and the testing process is completed automatically, and the testing is convenient.
Description
Technical field
The present invention relates to the program test field, relate in particular to a kind of Android applied program testing method and proving installation.
Background technology
Software test, always being very crucial in the application development also is a very loaded down with trivial details ring, concerning the Android(Android) especially true the test of application program.Day by day universal along with based on the smart machine of Android operating system, the Android number of applications is also more and more, and function becomes increasingly complex, for functional test, the stability test of the Android application program ever more important that also seems.
Because Android rises evening, the Android means of testing is relatively backward with respect to other software test, the test of at present a large amount of Android application programs all is to depend on manually to finish, and these test jobs not only repeatability are higher, and human input is larger; Therefore exigence Android automatization testing technique improves testing efficiency, and the manpower and materials of saving test drop into.
The Android automated test tool has Monkey(monkey instrument at present, a kind of robotization random test instrument that Google provides), MonkeyRunner(monkey running instrument, another kind of robotization random test instrument) etc., the tester need depend on the realization of programming when utilizing these instruments to write test script.And reality is, for the tester, its programming basis is often relatively weaker, be difficult to effectively utilize these instruments, the robotization use-case writes cost and maintenance cost is all larger, therefore needs a kind of more convenient tester Android automated test frame that use, that need not to programme to help the tester and finishes automatic test.
Publication number is the patent " based on automated testing method and the testing tool of android platform " that the patent " a kind of automatic test approach of Android program " of CN102521118, patent " a kind of software operation recording and replaying method towards Android and flavor thereof " that publication number is CN101957793 and publication number are CN102419732, all by record-mode of playback realizes the automatic test of Android application program, namely at first by the recording operation event and generate the android platform and can carry out the script of script and record step; Secondly receive the order of carrying out script at device object and carry out afterwards the described script execution in step of carrying out script.The automated testing method operation of this recording-playback formula is fairly simple comparatively speaking, need not programming, but size and the coordinate of serious dependence and screen, in case screen size changes or interface layout changes, then the tester need record script again; Therefore, the test mode of this recording-playback still can be cumbersome, and is convenient not.
In addition, publication number is that the patent " a kind of automated testing method based on Android " of CN102141960 generates the APK file with test case, calls the Monkey instruction and realizes robotization.The method operation interface is visual.But the method is when writing test case, owing to being by being packaged into APK(Android Application Package, Android application program installation kit) mode is had relatively high expectations to programming skill, needs the test case writer to be familiar with the Android application and development and just can write test case.
In sum, the method for testing of the Android application program of prior art is convenient not, needs a kind of more convenient tester Android automated testing method that use, that need not to programme.
Summary of the invention
Embodiments of the invention provide a kind of Android applied program testing method and proving installation, can realize the test to the Android application program more conveniently.
According to an aspect of the present invention, provide a kind of Android applied program testing method, having comprised:
From test case, parse the Configuration Values of the key word of each operation steps; Wherein, the key word of described operation steps comprises: sequence number, action type, operand; The Configuration Values of described operand is sign or the text message of UI element;
The Configuration Values of the sequence number of each operation steps that foundation parses is carried out the test of each operation steps successively; The test that one of them operation steps is carried out is: call the element operation tool, described element operation tool carries out corresponding operating according to the action type of this operation steps and the Configuration Values of operand to the corresponding UI element in the tested Android application program.
Further, the key word of described operation steps also comprises: proof test value, and the Configuration Values of described proof test value is sign or the text message of expectation UI element;
After the test of executable operations step, also comprise:
The Configuration Values of the proof test value of this operation steps and the execution result that described element operation tool returns are compared; If include the Configuration Values of the proof test value of this operation steps in the described execution result, the test result of then confirming this operation steps is successfully; Otherwise the test result of confirming this operation steps is unsuccessfully.
Further, the test result of described this operation steps of affirmation be unsuccessfully after, also comprise:
By described element operation tool tested Android application program is carried out the screenshotss operation, keep screen message.
Preferably, the key word of described operation steps also comprises: input value; And
The described test that one of them operation steps is carried out, also comprise: if the Configuration Values of the action type of this operation steps is input, then described element operation tool also according to the Configuration Values of the input value of this operation steps, carries out input operation to the corresponding UI element in the tested Android application program.
Preferably, described test case is based on extensible markup language XML; And
Before the described test of carrying out successively each operation steps, also comprise:
From described test case, parse the Configuration Values of following key word: time-out time, cycle index, step interval; And
When the test of described each operation steps of execution, also comprise:
The control and measuring spent time; If the time of monitoring surpasses the Configuration Values of time-out time warning information is proposed then;
According to the Configuration Values at the step interval that parses, the time interval between each operation steps is carried out in control;
According to the Configuration Values of the cycle index that parses, the cycle index of the test of each operation steps is carried out in control.
According to another aspect of the present invention, also provide a kind of Android Application testing device, having comprised:
The test case parsing module is for the Configuration Values that parses the key word of each operation steps from test case; Wherein, the key word of described operation steps comprises: sequence number, action type, operand; The Configuration Values of described operand is sign or the text message of UI element;
Testing execution module is used for the Configuration Values of the sequence number of each operation steps of parsing according to described test case parsing module, carries out successively the test of each operation steps; The test that one of them operation steps is carried out is: call the element operation tool, described element operation tool carries out corresponding operating according to the action type of this operation steps and the Configuration Values of operand to the corresponding UI element in the tested Android application program.
Further, described device also comprises:
The test case generation module is used for the Configuration Values according to the key word of each operation steps of tester's input, generates described test case;
The test case memory module is used for storing the test case that described test case generation module generates; And
Described test case parsing module also is used for obtaining described test case from described test case memory module.
Preferably, the key word of described operation steps also comprises: proof test value, and the Configuration Values of described proof test value is sign or the text message of expectation UI element; And
Testing execution module also is used at described element operation tool according to the action type of this operation steps and the Configuration Values of operand, after corresponding UI element in the tested Android application program carried out corresponding operating, obtain the execution result that described element operation tool returns; And
Described device also comprises:
The test result determination module is used for obtaining described execution result from described testing execution module, and Configuration Values and the described execution result of the proof test value of this operation steps are compared; If include the Configuration Values of the proof test value of this operation steps in the described execution result, the test result of then confirming this operation steps is successfully; Otherwise the test result of confirming this operation steps is unsuccessfully.
Further, described device also comprises:
The test result display module is used for obtaining the test result of each operation steps that described test result determination module confirms, and shows with the html page form.
Further, described test case generation module also is used for also generating described test case according to the Configuration Values of the following key word of tester's input: time-out time, cycle index, step interval; And
Described test case parsing module also is used for parsing from described test case the Configuration Values at described time-out time, cycle index, step interval; And
Described testing execution module also is used for obtaining the Configuration Values at time-out time that described test case parsing module parses, cycle index, step interval; And described when carrying out successively the test of each operation steps, the control and measuring spent time; If the time of monitoring surpasses the Configuration Values of described time-out time warning information is proposed then; According to the Configuration Values at described step interval, the time interval between each operation steps is carried out in control; According to the Configuration Values of described cycle index, the cycle index of the test of each operation steps is carried out in control.
In the technical scheme of the embodiment of the invention, because the tester can configure the test case based on key word easily; And by the key word in the test case is resolved, and call the element operation tool at bottom and realize operation to the UI element in the tested application program, thereby automatically finish test process.Like this, the tester only need carry out simple key word configuration, does not test with regard to generating test use case but do not need to carry out complicated programming; And even screen size changes or interface layout changes, the test case that has configured key word before still can using is tested, and need not regenerate test case, and large greatly tester provides the convenience of test.
Description of drawings
Fig. 1 is the message based method of testing process flow diagram of the support various protocols of the embodiment of the invention;
Fig. 2 is the message based test system structure schematic diagram of the support various protocols of the embodiment of the invention;
Fig. 3 is the Android applied program testing method process flow diagram of the embodiment of the invention;
Fig. 4 is the test driver module inner structure schematic diagram of the embodiment of the invention.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, referring to accompanying drawing and enumerate preferred embodiment, the present invention is described in more detail.Yet, need to prove, many details of listing in the instructions only are in order to make the reader to one or more aspects of the present invention a thorough understanding be arranged, even if there are not these specific details also can realize these aspects of the present invention.
The terms such as " module " used in this application, " system " are intended to comprise the entity relevant with computing machine, such as but not limited to hardware, firmware, combination thereof, software or executory software.For example, module can be, but be not limited in: the thread of the process of moving on the processor, processor, object, executable program, execution, program and/or computing machine.For instance, the application program of moving on the computing equipment and this computing equipment can be modules.One or more modules can be positioned at an executory process and/or thread, and module also can be on the computing machine and/or be distributed between two or more the computing machines.
The present inventor analyzes the test process of Android application program, discovery can be decomposed into a plurality of operation stepss to the test of Android application program, in each operation steps, operate for certain UI element respectively, for example, carrying out click(for certain UI element clicks) or the input(input) operation etc.Based on this analysis, in the test case based on key word provided by the invention, the tester comprises for the key word of each operation steps configuration: sequence number (index), action type (operation type), operand (target), input value (value) etc.And the tester is configured the key word in the test case, and the value of the key word in the test case namely is set, and just can finish the generation of test case.
The proving installation that the embodiment of the invention provides can be resolved test case automatically, calls the element operation tool according to the key word in the test case at bottom, such as MonkeyRunner, Monkey etc., carries out test and returns execution result, finishes test.Except calling the various interface of MonkeyRunner or Monkey instrument encapsulation, also can directly call Adb Shell instruction (order of ADB shell) as the element operation tool, finish the various operations to the UI element.ADB(Android Debug Bridge, Android debugging bridge) the shell order is the cover command-line tool that android provides.For ease of describing, herein can be at bottom to the UI(User Interface in the Android application program, user interface) instrument that operates of element is referred to as the element operation tool.Because the technician only need carry out simple key word configuration, do not test with regard to generating test use case but do not need to carry out complicated programming, so that the technician can carry out the test of Android application program more easily; And, with respect to recording-method of testing of playback, need not record script, even screen size changes or interface layout changes, still the test case that has configured key word before can using is tested, need not regenerate test case, large greatly tester provides the convenience of test.
Describe the technical scheme of the embodiment of the invention in detail below in conjunction with accompanying drawing.In the technical scheme of the embodiment of the invention, generate the method flow based on the test case of key word, as shown in Figure 1, comprise the steps:
S101: the key word of each operation steps in tester's configuration testing use-case.
In this step, the tester presses the order that each operation steps is carried out in the test process, configures successively the key word of each operation steps.The tester can generate the interface by the test case that software provides, and inputs the Configuration Values of the key word of each operation steps;
Particularly, the tester can generate the following configuration that the key word of each operation steps is carried out at the interface by test case:
Input integer numerical value is as the Configuration Values of the sequence number of operation steps, the order of the Configuration Values of the sequence number of operation steps in order to represent that operation steps is carried out; For example, the Configuration Values of the sequence number of each operation steps of input is respectively 1,2,3,4,5 successively
The title of input operation type or sign are such as click, input etc., as the Configuration Values of the action type of operation steps;
The sign (ID) of input UI element or text message are as the Configuration Values of the operand of operation steps;
If the value of action type of the operation steps of configuration is the input(input), then also need configure the input value of this operation steps, in order to when the UI element being carried out the input operation, as the input value of input operation.
S102: according to the key word generating test use case of tester's configuration.
The test case that generates according to the key word of each operation steps of configuration specifically can be based on XML(Extensive Makeup Language, extensible markup language) form, perhaps text formatting, perhaps script form.Preferably, the test case of XML-based is more convenient for resolving.
The test case of using the above-mentioned steps generation is carried out the system of Android Application testing, as shown in Figure 2, comprising: proving installation 101 and equipment under test 102.
Proving installation 101 is tested the Android application program in the equipment under test 102 according to the test case that above-mentioned steps generates; Concrete method of testing flow process comprises the steps: as shown in Figure 3
S301: after proving installation 101 connected with equipment under test 102, proving installation 101 sent instruction and starts tested Android application program in the equipment under test 102.
In this step, after proving installation 101 transmission adb connect instructions are connected to equipment under test 102, send am start instructions to equipment under test 102 again and start tested Android application program.
S302: proving installation 101 parses the Configuration Values of the key word of each operation steps in the test case.
In this step, for each operation steps, proving installation 101 parses the Configuration Values of the key word of this operation steps in the test case, namely parses sequence number, action type, the operand of this operation steps, the Configuration Values of input value.
S303: proving installation 101 is carried out the test of each operation steps successively according to the Configuration Values of the sequence number of the operation steps that parses.
Particularly, proving installation 101 is carried out the test to each operation steps successively according to the Configuration Values of the sequence number of each operation steps that parses.The detailed process of one of them operation steps being carried out test is: according to the action type of this operation steps that parses, the Configuration Values of operand, call the element operation tool, such as the MonkeyRunner instrument; The element operation tool is according to the action type of this operation steps and the Configuration Values of operand, to the corresponding UI(user interface in the tested Android application program, user interface) element carries out corresponding operating; For example, after calling the MonkeyRunner instrument, the MonkeyRunner instrument is according to sign or the text message of the UI element that configures for operand, and be action type title or the sign of action type configuration, corresponding UI element in the tested Android application program is carried out corresponding operating, for example certain corresponding UI element is clicked (click) operation, finish this operation steps in the test process.
Be the input(input for the Configuration Values of action type) operation steps, the detailed process of this operation steps being carried out test is: after calling the MonkeyRunner instrument, the MonkeyRunner instrument is according to the action type of this operation steps and the Configuration Values of operand, also according to the Configuration Values of the input value of this operation steps, to the corresponding UI element in the tested Android application program, carry out input operation according to the Configuration Values of input value.
S304: proving installation 101 obtains the test execution result, according to the test value (verify) of the operation steps in the test case, judges test result and record.
Further, for each operation steps, the key word of the operation steps in the test case also can comprise: test value (verify); The tester also can be configured the test value of operation steps in above-mentioned steps S101: the tester can generate the interface by test case, and the sign of input expectation UI element or text message are as the test value of operation steps.
According to the action type of the operation steps that parses, the Configuration Values of operand, after calling the element operation tool and having carried out the test of an operation steps, the element operation tool also can return the execution result of this operation steps at above-mentioned steps S303; For example, call the MonkeyRunner instrument after, the MonkeyRunner instrument returns a UI element set, and should the set in each UI attribute of an element information, as the execution result of this operation steps.
Proving installation 101 is compared Configuration Values and the execution result of the test value of this operation steps after obtaining the execution result that the element operation tool returns; If compare out the Configuration Values of the test value that includes this operation steps in the execution result, be sign or the text message that includes expectation UI element in the execution result, think that then execution result is the execution result of expectation, the test result of confirming this operation steps is successfully, the test result that can record this operation steps is Pass, and namely the test result of this operation steps is for passing through; Otherwise the test result of confirming this operation steps is unsuccessfully, and the test result that records this operation steps is failed Fail.
Preferably, the test result of confirming this operation steps be unsuccessfully after, proving installation 101 carries out screenshotss operations (screenshot) by the element operation tool to tested Android application program, keeps the screen message when makeing mistakes, and is convenient to analyze after test finishes.
S305: cleaning test scene.
After being completed of each operation steps in implementation of test cases successively, can not be affected for guaranteeing follow-up test case, then clear up the operation of test scene, specifically comprise: close current tested Android application program; If the interface of makeing mistakes is arranged, also to close the interface of makeing mistakes.
S306: show the test result of carrying out test according to test case.
Particularly, with the test result of above-mentioned each operation steps, show as the test result of carrying out test according to test case.
Preferably, can pass through HTML(Hypertext Markup Language, HTML (Hypertext Markup Language)) form of the page carries out the demonstration of test result: the test result that shows for each test case comprises a Global Result(test overall result) and the test result of a plurality of Step Results(operation stepss).Wherein Global Result represents the final test result of this test case (the Pass representative is carried out and passed through, and Fail represents unsuccessfully); Step Results then is the test result (the Pass representative is carried out and passed through, and Fail represents unsuccessfully) of each operation steps in the test case.In addition, also has the link of test result form on the html page of test result; By this link, can check the test result form, screen message in the test result form during integrated makeing mistakes of in test process, preserving, and proving installation 101 is by sending the Logcat daily record that the logcat instruction is obtained to equipment under test 102 in test process, and proving installation 101 is by sending the information such as CPU internal memory operating position that the dumpsys instruction is obtained to equipment under test 102 in test process.
The tester by preserve make mistakes the time the screen message observation test interface of makeing mistakes directly perceived, by Logcat daily record, CPU(Central Processing Unit, CPU (central processing unit)) information such as internal memory use is convenient to alignment error information.
More preferably, the key word in the test case also can comprise: time-out time, cycle index, step interval etc.;
The tester also can be to key word in above-mentioned steps S101: time-out time, cycle index, step interval are configured; Namely generate the interface by test case, the Configuration Values at input time-out time, cycle index, step interval.
Proving installation 101 also can parse the Configuration Values of time-out time, the Configuration Values of cycle index, the Configuration Values at step interval from test case in above-mentioned steps S302;
Proving installation 101 is carried out the test spent time of each operation steps successively according to the Configuration Values of the time-out time that parses among the monitoring above-mentioned steps S303; If the time of monitoring surpasses the Configuration Values of time-out time warning information is proposed then;
Proving installation 101 is according to the Configuration Values at the step interval that parses, and the time interval between each operation steps is carried out in control;
Proving installation 101 is according to the Configuration Values of the cycle index that parses, and the cycle index of the test of each operation steps is carried out in control.
Fig. 4 shows the inner structure block diagram in the above-mentioned proving installation 101, comprising: test case parsing module 401, testing execution module 402, test case generation module 403, test case memory module 404.
Test case generation module 403 is used for the Configuration Values according to the key word of each operation steps of the test case of tester's input, generates described test case; Further, test case generation module 403 also can receive the Configuration Values of following key word: time-out time, cycle index, step interval; And also generate described test case according to these key words.Particularly, test case parsing module 401 can provide test case to generate the interface, and the tester generates the Configuration Values that the key word of each operation steps is inputted at the interface by test case, and the Configuration Values of the key words such as time-out time, cycle index, step interval.
Test case memory module 404 is used for storing the test case that described test case generation module generates.
Test case parsing module 401 is used for parsing from test case the Configuration Values of the key word of each operation steps; Wherein, the key word of described operation steps comprises: sequence number, action type, operand; The Configuration Values of described operand is sign or the text message of UI element; Further, test case parsing module 401 also is used for parsing from described test case the Configuration Values at described time-out time, cycle index, step interval.
Further, testing execution module 402 also is used at described element operation tool according to the action type of this operation steps and the Configuration Values of operand, after corresponding UI element in the tested Android application program carried out corresponding operating, obtain the execution result that described element operation tool returns.
Further, also comprise in the proving installation 101: test result determination module 405, test result display module 406.
Test result determination module 405 is used for obtaining described execution result from testing execution module 402, and Configuration Values and the described execution result of the proof test value of this operation steps are compared; If include the Configuration Values of the proof test value of this operation steps in the described execution result, the test result of then confirming this operation steps is successfully; Otherwise the test result of confirming this operation steps is unsuccessfully.
Test result display module 406 is used for obtaining the test result of each operation steps that test result determination module 405 confirms, and shows with the html page form.
In the technical scheme of the embodiment of the invention, because test case consists of based on key word, the tester can configure the test case based on key word easily; By the key word in the test case is resolved, and call the element operation tool at bottom and realize operation to the UI element in the tested application program, can automatically finish test process.Like this, the tester only need carry out simple key word configuration, does not test with regard to generating test use case but do not need to carry out complicated programming; And even screen size changes or interface layout changes, the test case that has configured key word before still can using is tested, and need not regenerate test case, and large greatly tester provides the convenience of test.
One of ordinary skill in the art will appreciate that all or part of step that realizes in above-described embodiment method is to come the relevant hardware of instruction to finish by program, this program can be stored in the computer read/write memory medium, as: ROM/RAM, magnetic disc, CD etc.
The above only is preferred implementation of the present invention; should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; can also make some improvements and modifications, these improvements and modifications also should be considered as protection scope of the present invention.
Claims (10)
1. Android applied program testing method comprises:
From test case, parse the Configuration Values of the key word of each operation steps; Wherein, the key word of described operation steps comprises: sequence number, action type, operand; The Configuration Values of described operand is sign or the text message of UI element;
The Configuration Values of the sequence number of each operation steps that foundation parses is carried out the test of each operation steps successively; The test that one of them operation steps is carried out is: call the element operation tool, described element operation tool carries out corresponding operating according to the action type of this operation steps and the Configuration Values of operand to the corresponding UI element in the tested Android application program.
2. the method for claim 1 is characterized in that, the key word of described operation steps also comprises: proof test value, and the Configuration Values of described proof test value is sign or the text message of expectation UI element;
After the test of executable operations step, also comprise:
The Configuration Values of the proof test value of this operation steps and the execution result that described element operation tool returns are compared; If include the Configuration Values of the proof test value of this operation steps in the described execution result, the test result of then confirming this operation steps is successfully; Otherwise the test result of confirming this operation steps is unsuccessfully.
3. method as claimed in claim 2 is characterized in that, the test result of described this operation steps of affirmation be unsuccessfully after, also comprise:
By described element operation tool tested Android application program is carried out the screenshotss operation, keep screen message.
4. such as the arbitrary described method of claim 1-3, it is characterized in that, the key word of described operation steps also comprises: input value; And
The described test that one of them operation steps is carried out, also comprise: if the Configuration Values of the action type of this operation steps is input, then described element operation tool also according to the Configuration Values of the input value of this operation steps, carries out input operation to the corresponding UI element in the tested Android application program.
5. method as claimed in claim 4 is characterized in that, described test case is based on extensible markup language XML; And
Before the described test of carrying out successively each operation steps, also comprise:
From described test case, parse the Configuration Values of following key word: time-out time, cycle index, step interval; And
When the test of described each operation steps of execution, also comprise:
The control and measuring spent time; If the time of monitoring surpasses the Configuration Values of time-out time warning information is proposed then;
According to the Configuration Values at the step interval that parses, the time interval between each operation steps is carried out in control;
According to the Configuration Values of the cycle index that parses, the cycle index of the test of each operation steps is carried out in control.
6. Android Application testing device comprises:
The test case parsing module is for the Configuration Values that parses the key word of each operation steps from test case; Wherein, the key word of described operation steps comprises: sequence number, action type, operand; The Configuration Values of described operand is sign or the text message of UI element;
Testing execution module is used for the Configuration Values of the sequence number of each operation steps of parsing according to described test case parsing module, carries out successively the test of each operation steps; The test that one of them operation steps is carried out is: call the element operation tool, described element operation tool carries out corresponding operating according to the action type of this operation steps and the Configuration Values of operand to the corresponding UI element in the tested Android application program.
7. device as claimed in claim 6 is characterized in that, also comprises:
The test case generation module is used for the Configuration Values according to the key word of each operation steps of tester's input, generates described test case;
The test case memory module is used for storing the test case that described test case generation module generates; And
Described test case parsing module also is used for obtaining described test case from described test case memory module.
8. device as claimed in claim 7 is characterized in that, the key word of described operation steps also comprises: proof test value, and the Configuration Values of described proof test value is sign or the text message of expectation UI element; And
Testing execution module also is used at described element operation tool according to the action type of this operation steps and the Configuration Values of operand, after corresponding UI element in the tested Android application program carried out corresponding operating, obtain the execution result that described element operation tool returns; And
Described device also comprises:
The test result determination module is used for obtaining described execution result from described testing execution module, and Configuration Values and the described execution result of the proof test value of this operation steps are compared; If include the Configuration Values of the proof test value of this operation steps in the described execution result, the test result of then confirming this operation steps is successfully; Otherwise the test result of confirming this operation steps is unsuccessfully.
9. device as claimed in claim 8 is characterized in that, also comprises:
The test result display module is used for obtaining the test result of each operation steps that described test result determination module confirms, and shows with the html page form.
10. such as the arbitrary described device of claim 7-9, it is characterized in that,
Described test case generation module also is used for also generating described test case according to the Configuration Values of the following key word of tester's input: time-out time, cycle index, step interval; And
Described test case parsing module also is used for parsing from described test case the Configuration Values at described time-out time, cycle index, step interval; And
Described testing execution module also is used for obtaining the Configuration Values at time-out time that described test case parsing module parses, cycle index, step interval; And described when carrying out successively the test of each operation steps, the control and measuring spent time; If the time of monitoring surpasses the Configuration Values of described time-out time warning information is proposed then; According to the Configuration Values at described step interval, the time interval between each operation steps is carried out in control; According to the Configuration Values of described cycle index, the cycle index of the test of each operation steps is carried out in control.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012104418756A CN103049371A (en) | 2012-11-07 | 2012-11-07 | Testing method and testing device of Android application programs |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012104418756A CN103049371A (en) | 2012-11-07 | 2012-11-07 | Testing method and testing device of Android application programs |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103049371A true CN103049371A (en) | 2013-04-17 |
Family
ID=48062018
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012104418756A Pending CN103049371A (en) | 2012-11-07 | 2012-11-07 | Testing method and testing device of Android application programs |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103049371A (en) |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103259697A (en) * | 2013-04-19 | 2013-08-21 | 福州瑞芯微电子有限公司 | Method using UWB equipment to carry out ADB debugging on android platform |
| CN103309664A (en) * | 2013-05-31 | 2013-09-18 | 北京小米科技有限责任公司 | Screenshot method, device and equipment |
| CN103353858A (en) * | 2013-06-06 | 2013-10-16 | 百度在线网络技术（北京）有限公司 | Automatic testing method and device based on action touch simulation |
| CN103942146A (en) * | 2014-04-22 | 2014-07-23 | 上海斐讯数据通信技术有限公司 | Visual Monkey test method and device |
| CN104063324A (en) * | 2014-07-10 | 2014-09-24 | 上海斐讯数据通信技术有限公司 | Method and system for Monkey test |
| CN104199767A (en) * | 2014-08-19 | 2014-12-10 | 北京金山安全软件有限公司 | Test method and device |
| CN104331373A (en) * | 2014-11-28 | 2015-02-04 | 上海斐讯数据通信技术有限公司 | Monkey test system and method |
| CN104866384A (en) * | 2014-02-20 | 2015-08-26 | 纬创资通股份有限公司 | Method and system for rapidly testing and detecting mobile device |
| CN105100900A (en) * | 2015-08-19 | 2015-11-25 | Tcl海外电子（惠州）有限公司 | Compatibility test authentication method and device |
| CN105094783A (en) * | 2014-05-19 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and device for testing Android application stability |
| CN105608012A (en) * | 2016-03-10 | 2016-05-25 | 武汉斗鱼网络科技有限公司 | Automatic test method and automatic test system |
| CN105868100A (en) * | 2015-12-22 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Android system-based automatic test method and device |
| CN106341684A (en) * | 2016-09-05 | 2017-01-18 | Tcl集团股份有限公司 | Method and system for automatically generating Android TV test script |
| CN106951777A (en) * | 2017-03-06 | 2017-07-14 | 西安电子科技大学 | The estimating method of user interface during Android application operation |
| CN108170494A (en) * | 2017-12-28 | 2018-06-15 | 上海传英信息技术有限公司 | A kind of application program launching method and activation system for intelligent terminal |
| CN108304329A (en) * | 2018-02-13 | 2018-07-20 | 论客科技（广州）有限公司 | A kind of testing example design method, apparatus, terminal and readable storage medium storing program for executing |
| CN108733568A (en) * | 2018-05-25 | 2018-11-02 | 平安科技（深圳）有限公司 | Application testing method, device, equipment and readable storage medium |
| CN109189688A (en) * | 2018-09-11 | 2019-01-11 | 北京奇艺世纪科技有限公司 | A kind of generation method, generating means and the electronic equipment of test case script |
| CN109491919A (en) * | 2018-11-28 | 2019-03-19 | 中电科西北集团有限公司 | A kind of method for testing software and test platform |
| CN109918288A (en) * | 2019-01-16 | 2019-06-21 | 北京互金新融科技有限公司 | Use-case test method and device |
| WO2019136852A1 (en) * | 2018-01-10 | 2019-07-18 | 武汉斗鱼网络科技有限公司 | Method and system for saving starting log of application program, and storage medium and electronic device |
| CN110704709A (en) * | 2019-08-27 | 2020-01-17 | 北京金堤科技有限公司 | Application data capturing method and device, storage medium and electronic equipment |
| CN111190825A (en) * | 2019-12-28 | 2020-05-22 | 深圳市优必选科技股份有限公司 | Automatic test method, system and robot |
| CN111651359A (en) * | 2020-06-08 | 2020-09-11 | 北京首汽智行科技有限公司 | APP stability test method |
| CN114490330A (en) * | 2021-12-27 | 2022-05-13 | 北京鸿合爱学教育科技有限公司 | Method and apparatus for generating test cases |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030204784A1 (en) * | 2002-04-29 | 2003-10-30 | Jorapur Gopal P. | System and method for automatic test case generation |
| CN101339532A (en) * | 2007-07-06 | 2009-01-07 | 中国银联股份有限公司 | An automated testing method and device for a web application system |
| CN102541740A (en) * | 2012-01-04 | 2012-07-04 | 广东欧珀移动通信有限公司 | Android-based automatic test method for mobile phone notes |
-
2012
- 2012-11-07 CN CN2012104418756A patent/CN103049371A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030204784A1 (en) * | 2002-04-29 | 2003-10-30 | Jorapur Gopal P. | System and method for automatic test case generation |
| CN101339532A (en) * | 2007-07-06 | 2009-01-07 | 中国银联股份有限公司 | An automated testing method and device for a web application system |
| CN102541740A (en) * | 2012-01-04 | 2012-07-04 | 广东欧珀移动通信有限公司 | Android-based automatic test method for mobile phone notes |
Non-Patent Citations (1)
| Title |
|---|
| 侯菊敏: "基于Android的关键字驱动自动化测试框架研究", 《中国优秀硕士学位论文全文数据库》, 15 September 2012 (2012-09-15) * |
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103259697B (en) * | 2013-04-19 | 2016-03-02 | 福州瑞芯微电子股份有限公司 | Android platform utilize UWB equipment carry out the method for ADB debugging |
| CN103259697A (en) * | 2013-04-19 | 2013-08-21 | 福州瑞芯微电子有限公司 | Method using UWB equipment to carry out ADB debugging on android platform |
| CN103309664A (en) * | 2013-05-31 | 2013-09-18 | 北京小米科技有限责任公司 | Screenshot method, device and equipment |
| CN103309664B (en) * | 2013-05-31 | 2016-08-10 | 小米科技有限责任公司 | Screenshot method, device and equipment |
| CN103353858A (en) * | 2013-06-06 | 2013-10-16 | 百度在线网络技术（北京）有限公司 | Automatic testing method and device based on action touch simulation |
| CN103353858B (en) * | 2013-06-06 | 2016-03-16 | 百度在线网络技术（北京）有限公司 | A kind of automated testing method based on action touch simulation and device |
| CN104866384A (en) * | 2014-02-20 | 2015-08-26 | 纬创资通股份有限公司 | Method and system for rapidly testing and detecting mobile device |
| CN103942146A (en) * | 2014-04-22 | 2014-07-23 | 上海斐讯数据通信技术有限公司 | Visual Monkey test method and device |
| CN105094783A (en) * | 2014-05-19 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and device for testing Android application stability |
| CN105094783B (en) * | 2014-05-19 | 2019-12-13 | 腾讯科技（深圳）有限公司 | method and device for testing stability of android application |
| CN104063324A (en) * | 2014-07-10 | 2014-09-24 | 上海斐讯数据通信技术有限公司 | Method and system for Monkey test |
| CN104063324B (en) * | 2014-07-10 | 2017-11-24 | 上海斐讯数据通信技术有限公司 | A kind of Monkey method of testings and system |
| CN104199767B (en) * | 2014-08-19 | 2017-08-29 | 北京金山安全软件有限公司 | Test method and device |
| CN104199767A (en) * | 2014-08-19 | 2014-12-10 | 北京金山安全软件有限公司 | Test method and device |
| CN104331373A (en) * | 2014-11-28 | 2015-02-04 | 上海斐讯数据通信技术有限公司 | Monkey test system and method |
| CN105100900B (en) * | 2015-08-19 | 2019-05-14 | Tcl海外电子（惠州）有限公司 | The method and apparatus of compatibility test certification |
| CN105100900A (en) * | 2015-08-19 | 2015-11-25 | Tcl海外电子（惠州）有限公司 | Compatibility test authentication method and device |
| CN105868100A (en) * | 2015-12-22 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Android system-based automatic test method and device |
| CN105608012A (en) * | 2016-03-10 | 2016-05-25 | 武汉斗鱼网络科技有限公司 | Automatic test method and automatic test system |
| CN106341684A (en) * | 2016-09-05 | 2017-01-18 | Tcl集团股份有限公司 | Method and system for automatically generating Android TV test script |
| CN106951777A (en) * | 2017-03-06 | 2017-07-14 | 西安电子科技大学 | The estimating method of user interface during Android application operation |
| CN106951777B (en) * | 2017-03-06 | 2019-07-23 | 西安电子科技大学 | The estimating method of user interface when Android application operation |
| CN108170494A (en) * | 2017-12-28 | 2018-06-15 | 上海传英信息技术有限公司 | A kind of application program launching method and activation system for intelligent terminal |
| CN108170494B (en) * | 2017-12-28 | 2021-12-17 | 上海传英信息技术有限公司 | Application program starting method and starting system for intelligent terminal |
| WO2019136852A1 (en) * | 2018-01-10 | 2019-07-18 | 武汉斗鱼网络科技有限公司 | Method and system for saving starting log of application program, and storage medium and electronic device |
| CN108304329A (en) * | 2018-02-13 | 2018-07-20 | 论客科技（广州）有限公司 | A kind of testing example design method, apparatus, terminal and readable storage medium storing program for executing |
| CN108733568A (en) * | 2018-05-25 | 2018-11-02 | 平安科技（深圳）有限公司 | Application testing method, device, equipment and readable storage medium |
| CN109189688A (en) * | 2018-09-11 | 2019-01-11 | 北京奇艺世纪科技有限公司 | A kind of generation method, generating means and the electronic equipment of test case script |
| CN109491919A (en) * | 2018-11-28 | 2019-03-19 | 中电科西北集团有限公司 | A kind of method for testing software and test platform |
| CN109491919B (en) * | 2018-11-28 | 2021-10-26 | 中电科西北集团有限公司 | Software testing method and testing platform |
| CN109918288A (en) * | 2019-01-16 | 2019-06-21 | 北京互金新融科技有限公司 | Use-case test method and device |
| CN110704709A (en) * | 2019-08-27 | 2020-01-17 | 北京金堤科技有限公司 | Application data capturing method and device, storage medium and electronic equipment |
| CN111190825A (en) * | 2019-12-28 | 2020-05-22 | 深圳市优必选科技股份有限公司 | Automatic test method, system and robot |
| CN111651359A (en) * | 2020-06-08 | 2020-09-11 | 北京首汽智行科技有限公司 | APP stability test method |
| CN114490330A (en) * | 2021-12-27 | 2022-05-13 | 北京鸿合爱学教育科技有限公司 | Method and apparatus for generating test cases |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103049371A (en) | Testing method and testing device of Android application programs | |
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| US8924912B2 (en) | Method of recording and replaying call frames for a test bench | |
| US9465718B2 (en) | Filter generation for load testing managed environments | |
| CN104407980B (en) | Mobile solution automatic test device and method | |
| TWI566090B (en) | Debugging firmware / software to produce tracking systems and methods, recording media and computer program products | |
| CN103729294B (en) | Method and device for testing performance script of application software | |
| CN102495802B (en) | Method and device for testing software system, and computer system | |
| Roehm et al. | Monitoring user interactions for supporting failure reproduction | |
| US9792402B1 (en) | Method and system for debugging a system on chip under test | |
| CN113568825B (en) | Program flow debugging method, device, equipment and storage medium | |
| CN110908915A (en) | Test coverage rate display method and device and computer system | |
| CA2811617C (en) | Commit sensitive tests | |
| US8381185B2 (en) | Apparatus, system, and method for dynamic module flow analysis | |
| Ghosh et al. | A systematic review on program debugging techniques | |
| CN112685306A (en) | Test method, test device, user terminal and storage medium | |
| CN110633199A (en) | Test apparatus, method and medium for blockchain supporting smart contracts | |
| CN114490337A (en) | Commissioning method, commissioning platform, equipment and storage medium | |
| CN107885648B (en) | Method and device for generating test report | |
| CN118606211A (en) | Test script generation method, device, electronic equipment and vehicle | |
| CN117707982A (en) | Test method, apparatus, device, medium and program product | |
| CN112416807A (en) | System and method for analyzing and correlating test case results | |
| CN116756053A (en) | Front-end project test problem reporting distribution method and system based on screen recording playback | |
| JP4957521B2 (en) | Software partial test system, method and program used therefor | |
| US9244814B1 (en) | Enriched log viewer |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130417 |