JP2014053870A - Operation test program of mobile terminal device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an operation test program of a mobile terminal device which can be operated with an installed program only without using a monitoring terminal device and other equipment and in which an operation test is possible without selecting an operation test place.SOLUTION: In an operation test program which is installed in a recording area of a mobile terminal device and tests an operation of the mobile terminal device, the operation test program of the mobile terminal device has a recording mode and a reproduction mode. In the recording mode, an input signal that is an instruction transmitted to an operating system from an input device a user has operated is acquired to record the input signal to generate a scenario. In the recording mode, the input signal in which an operation is reproduced from the scenario is transmitted from the operation test program to the operating system.

Description

  The present invention is an operation test carried out in the development of a portable terminal, and can be operated only with an installed program without using a monitoring terminal and other equipment, and the operation test can be performed without selecting an operation test place. The present invention relates to an operation test program for portable terminals.

  In the development of mobile terminals, when conducting terminal evaluation, not only specific places, but places where mobile terminals are assumed to be used, for example, indoors such as offices and schools, in transportation, outdoors, underground, It is necessary to conduct operational tests in all fields such as at sea.

  However, in the conventional operation test environment, it is necessary to prepare equipment other than the terminal when evaluating the terminal. For example, in order to acquire and save the operation test result of the terminal, it is necessary to connect to a monitoring terminal.

JP2008-271129A

  Patent Document 1 discloses that an imaging device 4 includes an imaging device 4 that is a camera for imaging a display screen 2A of a test portable terminal 2, and an operation test method for a portable terminal and an operation test system for a portable terminal. In addition, an operation test program for a portable terminal is disclosed. Patent Document 1 captures a display image during an operation test of a mobile terminal with an imaging device 4, and displays a plurality of images corresponding to the display image (reference image) of the test mobile terminal 2 as a test result image indicating the test result. And create a difference image indicating the difference between the extracted test result image and a reference image corresponding to the test result image, and confirm the display image of the mobile terminal after the operation test of the mobile terminal A portable terminal operation test method and a portable terminal operation test system are disclosed.

  However, when the imaging device 4 and the test control device 6 are required and a plurality of terminals are tested at the same time or when a test other than a fixed place is performed, for example, when a test is performed in a train, the amount of equipment to be carried It was bulky and testing itself was a difficult task.

  In addition to Patent Document 1, there is a case in which large equipment such as a robot arm is used as an input device in order to perform an automatic test that repeats the same test or to operate a terminal in a GUI (GRAPHIC USER INTERFACE) environment. is there. In this operation mode, because the equipment used is large, it is not easy to increase the number of test systems. Moreover, regarding the test while moving, it was not realistic considering the scale of the test system and the preparation of the power source.

  In addition, event-driven programming that performs processing in response to an operation (input signal, event) executed by a user or another program is used in a program of a smartphone or a mobile terminal having a GUI.

  A normal mobile terminal operation test program (hereinafter referred to as a test program) is installed in an external monitoring terminal 120 connected to the mobile terminal 100 as shown in FIG. The OS 103 receives all the input signals generated by the input to the input device 110 of the user's portable terminal 100 and the input of communication, and the test program 115 acquires the event generated on the OS 103 at that time. It was. However, depending on the CPU load status of the mobile terminal 100 and the like, the OS 103 abandons the event generation of some input signals, so the test program 115 does not acquire events for all input signals. Therefore, when the test program 115 reproduces an event, the event cannot be reproduced for all input signals.

  Accordingly, the present invention provides an operation test program in a mobile terminal directly acquiring an input signal generated by an input to a user input device and an input such as communication in an operation test in a mobile terminal. In addition to preventing a decrease in the reproducibility of the input signal due to the abandonment of event generation on the OS side, equipment such as a monitoring terminal, a camera, a robot arm, and the like are not required during an operation test based on the reproduction of the input signal. It is an object to provide a test program that can perform an operation test only with a program installed in the system.

  An operation test program for a mobile terminal according to the present invention is an operation test program that is installed in a recording area of a mobile terminal and tests the operation of the mobile terminal, and the operation test program is operated by a user. A recording mode for acquiring all input signals that are commands transmitted from the input device to the operating system and recording the input signals, creating a scenario, and the input test signal reproducing the operation from the scenario, the operation test program And a reproduction mode for transmitting to the operating system.

  The acquisition of the input signal in the recording mode of the operation test program of the portable terminal according to the present invention is performed at a timing while the input signal reaches the operating system from the input device, and the reproduction of the input signal in the reproduction mode is performed. Transmits the input signal to the operation system at an arbitrary timing.

  The operating environment of the operation test program according to the present invention is such that the recording mode and the reproduction mode can be executed only by the portable terminal installed in the recording area, and no external monitoring terminal is required. It is characterized by.

  The operation test program according to the present invention relates to a display image displayed on the screen of the mobile terminal based on the input signal, the display image recorded in the recording mode, and the display image reproduced in the reproduction mode. It is possible to compare the display image and determine all or a part of the difference.

  The operation test program according to the present invention relates to the audio data and / or the communication data (packet data) issued by the portable terminal based on the input signal, the audio data recorded in the recording mode and / or the It is possible to compare communication data (packet data) with the audio data and / or the communication data (packet data) reproduced in the reproduction mode, and to determine all or some of the differences. Features.

  The reproduction mode of the operation test program according to the present invention can be executed by specifying the number of repetitions and reproduction range at the time of reproduction of the scenario, and is automatically executed from the start to the end of reproduction. To do.

  In the reproduction mode of the operation test program according to the present invention, when an operation test result error occurs during reproduction of the scenario, notification is performed by creating an error log file and operating the output device of the portable terminal. Features.

  In a method of acquiring an event from a conventional OS (Operating System), when the OS abandons event generation of an input signal generated by an input to the user's input device, the user's input operation is performed. Although it was impossible to reproduce completely, the test program of the present invention directly acquires the input signal generated by the user's input operation before reaching the OS, and generates a scenario from the acquired input signal. Therefore, when the scenario is reproduced, the user's input operation can be completely reproduced.

  Further, since all input signals can be acquired, communication-related input signals generated from input operations and screen transitions can also be acquired and reproduced.

  In addition, since the test program of the present invention is stored and executed in the recording area of the mobile terminal, the mobile terminal includes an external terminal for monitoring, a camera for screen acquisition, a microphone for audio acquisition, and the like. There is no need to connect. Since the operation test can be carried out with a single mobile terminal, the cost for equipment procurement is not necessary, and there are no restrictions on the location of the operation test. Can be tested.

  Further, the test program of the present invention can easily process a scenario generated from the acquired input signal, and can shorten the test pattern creation process. In addition, since the scenario can be copied and distributed and a reproduction operation test can be performed, the reproduction operation test can be performed simultaneously on a plurality of portable terminals.

It is a block diagram which shows the structure of the operation | movement test program and portable terminal of this invention. It is a conceptual diagram which shows the acquisition timing of the input signal of an operation test program. It is a flowchart which shows the flow of a process at the time of the recording mode of an operation test program. It is a figure which shows the screen of a portable terminal device at the time of the recording mode of an operation test program. It is a figure which shows the preservation | save method etc. of a scenario at the time of the recording mode of an operation test program. It is a flowchart which shows the flow of a process at the time of operation test implementation (at the time of reproduction mode) of an operation test program. It is a figure which shows the selection screen of a scenario at the time of operation test implementation (at the time of reproduction mode) of an operation test program. It is a figure which shows the operation test result screen of an operation test program. It is a figure which shows the change method of the comparison screen range at the time of the recording mode of an operation test program. It is a conceptual diagram which shows the acquisition timing of the event of the operation | movement test program of the conventional invention.

[First embodiment of the present invention]
Hereinafter, an operation test program according to the first embodiment of the present invention will be described in detail with reference to the drawings.
[System configuration]
FIG. 1 is a block diagram showing a configuration of an operation test program and a mobile terminal according to the present invention. As shown in FIG. 1, the mobile terminal 1 includes a control device 2, an input device 5, a recording device 10, a communication device 18, and an output device 20. The portable terminal 1 according to the present embodiment will be described using a device such as a smartphone having an operating system 3 (hereinafter referred to as OS 3) and a large display 22, but a normal portable terminal or PDA (Personal Digital). Any device equipped with the following OS, such as an assistant or a portable music player, may be used.

  The control device 2 executes the OS 3, and the OS 3 controls the hardware, software, and communication of the input device 5, the recording device 10, the communication device 18, and the output device 20. The OS 3 may be an operating system used for a portable terminal, for example, software such as Android (registered trademark) or iOS (trademark). The OS receives data input by the user from the input device 5 and transmits the data to the output device, the communication device, and the recording device, exchanges data with the communication device, and stores / uses data with the recording device. Control the output to the output device. The OS 3 is recorded in the internal storage 11 of the recording apparatus 10 and is not erased when the power is turned off, but starts when the power is turned on.

  The input device 5 is a device, a part, or the like that is installed in the mobile terminal 1 and can be input to the mobile terminal 1 by a user's input operation. The input device 5 includes a microphone 6, a hardware key 7, a software key 8, and a touch panel 9. Further, a camera, a motion sensor, a wireless communication device, or the like may be provided.

  The recording device 10 is a device for storing recording data such as an application and a telephone number temporarily or for a long term. The recording device 10 includes an internal storage 11 and an external storage 16, and the internal storage 11 includes recording devices such as an SSD (Solid State Drive) and an HDD (Hard Disk Drive), and includes an application 12 and a test program 15 inside. Record the program. The external storage 16 includes a removable recording device such as a memory card such as an SD card, a USB (Universal Serial Bus) memory, and an external HDD. It plays a role of supplementing program copy and installation to the internal storage 11 and insufficient capacity of the internal storage 11.

  The communication device 18 is a device in which the mobile terminal 1 communicates with a base station (not shown). The communication device 18 includes an antenna (not shown), a transmitter (not shown), a receiver (not shown), and the like.

  The output device 20 is a device for notifying the user of the result of the user's input operation and the processing result of the OS 3 and includes a speaker 21, a display 22, a lamp 23, a vibration device 24, and the like. If the display is a mobile terminal, a liquid crystal display (LCD) of 3.5 inches or more is suitable.

[Outline of test program]
An OS that uses a GUI for an input operation as shown in the present invention is an event-driven system. An event is a signal generated by the OS or the like when an action such as input / output from a user or the like, for example, clicking a mouse or inputting from a keyboard, occurs when a computer program is executed. Say. An operation method of a program that executes an actual process at the time when an event is generated is called event-driven (event-driven), and a program using this concept is called event-driven programming.

  Also, in a general operation test, an event for an operation is extracted and a scenario in which the range of continuous operations of a user is recorded is created, or a new scenario is created. By transmitting the operation test environment to the mobile terminal that performs the operation test, the operation is reproduced, and the operation test is performed based on whether or not the mobile terminal performs the operation according to the scenario.

  Here, the same operation can be repeated by repeating all the events for the user's operation. Therefore, when performing a repeated operation test, the same operation test can be easily repeated by recording these events and reproducing / transmitting the same event again. Further, by changing the order of the recorded events or directly changing the contents of the events, a new reproduction pattern can be generated without repeating the input operation.

  In the conventional operation test method for recording an event, as described above, as shown in FIG. 10, the input signal generated by the user operating the input device 110 and transmitted to the OS 103 is transmitted to the mobile terminal 100. The test program 115 installed in the connected external monitoring terminal 120 performs monitoring and recording. However, in this method, during recording, the OS 103 abandons the event generation of some of the input signals notified from the input device 110 depending on the CPU load or the like. The event for the input signal cannot be obtained. In addition, since the timing at which an event is generated on the OS 103 is recorded, not the timing at which the user actually touches, the event generation timing for all operations differs from the user's operation timing depending on the CPU load and the like. User operations cannot be recorded.

  Therefore, since the event is directly generated in the OS 103 at the time of reproduction, the OS 103 does not process the input signal from the input device 110, and the terminal load state at the time of performing the operation test is different from the actual user operation. Thus, it is difficult to say that the user operation can be reproduced. In addition, since an event is generated on the test program side, an event related to an input signal from an input device that is supposed to be abandoned by the OS due to the CPU load or the like when an operation is performed by a user in an operation test at a high load. Therefore, there is a problem that it is not appropriate as an operation test at high load.

  In addition, as an operation test environment, it is necessary to perform recording / reproduction after connecting to the monitoring terminal 120. In addition, the need for an external device such as a camera, the construction of an operation test environment with multiple units is expensive, and the operation test implementation environment is, for example, difficult to carry and has a certain amount of space when installed. Restrictions such as necessary, there are environments where the monitoring terminal 120 cannot be brought in, and the like occur.

  Therefore, in the present invention, as shown in FIG. 2, an input signal generated by the user operating the input device 5, generated in the application 12 and the communication device 18 in relation to the user operation, and transmitted to the OS 3. 1 and 2 at the position A shown in FIG. 1 and FIG. 2, the test program 15 acquires all the input signals issued by the input device 5 by the test program 15 before the OS 3 receives them. It was possible to do.

  By acquiring the input signal at the position A, it is possible to acquire an input signal that is not loaded into an event by the OS because the CPU is under load in the recording mode. Further, since the input signal from the input device 5 is monitored instead of the processing on the OS 3 side, it is possible to record all the user operations regardless of the delay related to the event generation on the OS 3 side.

  In the reproduction mode, when the test program 15 transmits the recorded input signal of the input device 5 from the position A to the OS, the OS 3 side is in the same state as when the input device 5 is actually operated. The input signal from the input device 5 is processed by the OS 3 in a pseudo manner, and then an event occurs, and the user operation can be reproduced in a natural manner. Further, since the input signal from the input device 5 is transmitted to the OS 3, it is possible to reproduce a situation in which no event is generated on the OS 3 side in a state where the processing capacity on the OS 3 side is insufficient due to a high load or the like.

  Also, since no monitoring terminal is required as an operation test environment, the cost for constructing an automatic operation test environment can be reduced, and an operation test can be performed anytime and anywhere as long as the terminal can be transported / loaded. For example, even when an operation test is performed on a communication state in an urban area, an operation test can be performed on a mobile terminal alone in a train or the like.

[Recording mode processing]
Hereinafter, the operation of the operation test program (test program) 15 in the recording mode will be described with reference to FIGS. FIG. 3 is a flowchart showing a flow of processing in the operation test program recording mode, FIG. 4 is a diagram showing a screen of the portable terminal in the operation test program recording mode, and FIG. 5 is a recording of the operation test program. It is a figure which shows the preservation | save method etc. of a scenario at the time of mode.

  First, the recording icon 35 is selected from the icons displayed on the display 22 of the portable terminal 1, and the test program 15 is activated (see step S1, FIG. 4A).

  When the test program 15 is activated, a record management screen 41 shown in FIG. 4B is displayed (step S2). The scenario is composed of three parts: “initialization operation”, “repetitive operation”, and “end operation”. The user selects contents to be recorded from any of the recording buttons 51a to 51c. In the present embodiment, the “initialization operation” of the recording button 51b records an operation for moving from the home screen to the repetitive operation start screen, and the “repetitive operation” of the recording button 51a includes an operation test to be actually performed. An operation according to the content is recorded, and an operation for returning from the repetitive operation end screen to the home screen is recorded in the “end operation” of the recording button 51c. Regardless of the present embodiment, other operations may be recorded.

  When the user selects the content to be recorded from any of the recording buttons 51a to 51c, the user transitions to the recording preparation state (step S3). The user is ready for the operation test by activating an application whose operation is to be recorded in the recording preparation state. Here, when a predetermined body key 32 is pressed, recording is started (Yes in step S4). If the predetermined main body key 32 is not pressed (No in step S4), the process waits until it is pressed. When the recording is started, the recording display icon 39 is discolored or turned on to indicate that the recording is in progress (see FIG. 4C).

  In the recording state, input signals for all operations of the user's portable terminal 1 are recorded in a temporary recording area (not shown) (step S5). Until the interrupt signal is detected (Yes in step S6), the recording of the input signal is continued.

  Next, when an interrupt signal is detected (Yes in step S6), it is determined whether or not the signal is a signal for creating a “screen checkpoint”. The “screen check point” is to designate whether or not to acquire by an operation of the user so as to acquire the image being displayed on the display 22. For example, when the user performs an arbitrary operation specified in advance (touching the screen, pressing a button, shaking the mobile terminal, etc.), it is determined as “create screen checkpoint” (Yes in step S7). ). The presence / absence of the “screen checkpoint” can be confirmed on the recording operation screen 40 after the operation is recorded.

  If it is determined that the signal is for creating a “screen checkpoint” (Yes in step S7), the screen information is acquired / temporarily stored as image data (step S9). Then, the recorded input signal information acquired / saved in the temporary recording area is saved in a file (step S10). Then, the process returns to step S5 and enters an input signal waiting state. In this manner, not only the user's operation but also screen information is acquired as image data, and a more accurate operation test can be performed by comparing with screen information being displayed in the reproduction mode.

  If it is determined that the signal is not a “screen checkpoint” creation signal (No in step S7), it is determined whether or not the interrupt signal is an end instruction signal (step S8). The end instruction is generated when the main body key 32 is pressed.

  If it is not an end instruction signal (No in step S8), input signals for all operations of the user's portable terminal 1 are continuously recorded in a temporary recording area (not shown) (step S5).

  If it is an end instruction signal (Yes in step S8), the recording of the input signal is ended. Here, the recorded input signal information acquired / saved in the temporary recording area is saved in a file (step S11), and the recording operation screen 40 is displayed (shown in FIG. 5A). Further, when the main body button 31 is pressed, the recorded result, the save button 53a and the delete button 53b are displayed (see FIG. 5B), and when the save button 53a is pressed, the data recorded in step S5 is changed. It is saved in the internal storage 11, and transitions to the record management screen 41.

  On the management record screen, since the record buttons 51a to 51c selected in step S2 are changed and the record is recorded and saved on any of the record buttons (saved) 52a to 52c, the user performs record management. The presence or absence of storage can be confirmed on the screen 41 (see FIG. 5C). Note that only one or two of “initialization operation”, “repetition operation”, and “end operation” can be saved and terminated.

  When the user further presses the save button, a dialog box for naming the scenario is displayed (see FIG. 5D). When the user inputs the scenario name and presses the save button, the scenario is saved in step S11. A scenario is generated from the recorded record (step S12), the generated scenario is stored in the internal storage 11, and the operation recording process is terminated (step S13).

  In the reproduction mode, an input signal of the contents of the generated scenario is sequentially transmitted to the position A and transmitted to the OS 3 to reproduce the acquired operation. In the scenario, the input signal generated by the operation of the input device 5, the communication-related input signal generated from the screen transition, and the like are recorded, so that the acquisition operation can be faithfully reproduced.

  Multiple scenarios can be created by changing the scenario name, and saved scenarios can be copied to other mobile terminals if they are of the same model and used in the reproduction mode on other mobile terminals. I can do it.

[Processing in reproduction mode]
Next, the operation of the operation test program (test program) 15 in the reproduction mode will be described with reference to FIGS. FIG. 6 is a flowchart showing a flow of processing when the operation test of the operation test program is performed (reproduction mode), and FIG. 7 is a scenario selection screen when the operation test of the operation test program is performed (reproduction mode). .

  First, the reproduction execution icon 36 is selected from the icons displayed on the display 22 of the portable terminal 1 shown in FIG. 4A, and the test program 15 is started (step S21). The scenario execution management screen 42 shown in FIG.

  When a desired scenario is selected (step S22), a scenario execution information editing screen shown in FIG. 7A is displayed. On the scenario execution information editing screen, the necessity of execution, the number of executions n times, and the execution range are set (step S23). For example, the necessity of execution (Enable) is selected. If the number of executions is set to “0”, the execution is repeated indefinitely. In addition, an execution range can be specified. The execution range can be selected to repeat with a set of “initialization operation”, “repetition operation” and “end operation”, or to repeat only “repetition operation”.

  When the input of the scenario execution information editing screen is completed, the scenario execution management screen 42 is displayed again. When the necessity of execution (Enable) is selected in step S23, the check box is checked on the scenario execution management screen 42 shown in FIG. On the scenario execution information editing screen, as shown in FIG. 7C, the scenario execution order can be changed by dragging with a finger. When the scenario execution button 54 shown in FIG. 7D is pressed, the reproduction process is started (step S24).

  At this time, the test program 15 generates an input signal from the selected scenario (step S25), sends the input signal to the position A in FIG. 1, and the OS 3 receives the sent input signal. In this way, it is possible to perform an operation test in a pseudo manner as if the user is actually operating the mobile terminal 1.

  First, when there is an “initialization operation” in the scenario, the “initialization operation” in the scenario is reproduced and executed (step S26).

  Next, the “repetitive operation” in the scenario is reproduced and executed (step S27). From the beginning of the scenario file, the input signals described in the scenario are sequentially reproduced and sent to the OS 3. During the sequential reproduction, the presence / absence of a screen checkpoint is determined (step S28). If there is a screen check point (Yes in step S28), the process proceeds to a result check (step S29).

  If there is no screen check point (No in step S28), there is no instruction to check the screen on the scenario, and therefore there is no target for determining the test result, so the scenario is advanced without performing the test result determination.

  If there is a screen check point (Yes in step S28), a result check is performed to check whether the actual operation of the mobile terminal 1 is consistent with the input signal sent from the scenario to the OS 3 (step S29). In the comparison of the operation coincidence, the screen information recorded in the recording mode is compared with the screen information displayed in the reproduction mode.

  If the result check is normal (OK) (Yes in step S29), it is checked whether the scenario being reproduced has been executed up to the end of the described content (step S30). If the scenario has not been executed until the end of the scenario (No in step S30), the process returns to step S28 and the scenario reproduction is continued. If the scenario has been executed up to the end (Yes in step S30), it is checked whether the number of executions of the scenario being reproduced has reached the number of executions n set in step S23 (step S31). If the number of executions has not reached n (No in step S31), the process returns to step S27 and the scenario is executed again.

  When the number of executions has reached n times (Yes in step S31), the “end operation” in the scenario is executed (step S32).

  Then, after finishing the “end operation”, it is checked whether or not a scenario to be executed next exists (step S33). If there is a scenario to be executed next (Yes in step S33), the process returns to step 25, and the next scenario is read. If there is no scenario to be executed next (No in step S33), the test program 15 is terminated (step S34).

  If the result check in step S29 is abnormal (NG) (No in step S29), processing is performed when the result is abnormal (step S35). The processing when the result is abnormal is to notify the user to that effect, such as a lamp display of the mobile terminal 1 when an abnormality is detected, a buzzer alarm, or a message indicating an error on the display 22. To do. Also, as a record, an error log file is acquired when an error occurs, and the contents of the error can be confirmed after the operation test is completed. It is preferable that the error log file can be edited, copied or converted into a scenario, and an operation test can be easily performed again.

  As described above, by selecting and executing a scenario, the operation test can be automatically digested, and the execution can be performed by specifying the number of repetitions and the execution range. Therefore, the labor and time of the user (operation tester) can be greatly reduced.

[Confirm result]
With reference to FIG. 8, the result confirmation of this operation test program (test program) 15 will be described. FIG. 8 is a diagram showing an operation test result screen of the operation test program.

  First, the record display icon 37 is selected from the icons displayed on the display 22 of the portable terminal 1 shown in FIG. 4A, and the result viewer screen 44 shown in FIG. 8A is displayed. The result viewer screen 44 displays a list of log files acquired when the scenario is executed. Here, when a result to be browsed is selected, an individual operation test result 44b shown in FIG. 8B is displayed. The display content includes, for example, a scenario name, start time, end time, total number of events, number of checks that are OK, and the like. At this time, the error log file may be browsed.

  In this way, the operation test result can be easily confirmed by acquiring the operation test log file and the error log file.

[Change screen comparison range]
Since the test program 15 can only enter “screen checkpoints” in the recording mode, the user manually adjusts the comparison range of the screen after the recording mode is finished in order to perform a more precise screen operation check. It is desirable to specify and create a scenario. When the comparison range is not set, at the screen checkpoint, only the image is acquired and the comparison is not performed. This is because, when all the screens are simply compared, if there is a display that changes state, such as a clock or a changing icon on the screen, there will always be a difference between the recording mode and the reproduction mode. This is to prevent a situation in which NG is always NG.

  The user selects the item “screen comparison” from the recording operation screen 40 shown in FIG. When selected, a screen comparison setting change dialog shown in FIG. 9A is displayed. Here, “change comparison range” is selected. Before the change, the entire range in which the image on the display 22 of the mobile terminal 1 is displayed is set. Here, the designated range 45 shown in FIG. 9B is selected. The selection can be made by touching the image displayed on the display 22. The end of the setting is confirmed by pressing “OK” since an input confirmation screen shown in FIG. 9C is displayed when an arbitrary place on the image displayed on the display 22 is touched. When the confirmation is made, the screen returns to the recording operation screen 40 in FIG. 9D, and it is understood that the position coordinate 46 is designated in the selected “screen comparison” item.

  When the scenario after “change of comparison range” is generated and executed in the reproduction mode, the display within the specified range 45 set in “change of comparison range” shows the scenario (in recording mode) and the reproduction mode. By performing the confirmation work of whether or not the screen display is the same, a confirmation test of a part of the image displayed on the display 22 can be performed more precisely.

  Also, in the recording mode, the voice or the like emitted from the speaker 21 is acquired and stored as audio data, or the content of communication data (packet data) transmitted / received from the communication device is stored as recording data. It may be reproduced. Further, an operation for imaging with a camera may be reproduced in a scenario. In this case, in the result check in the reproduction mode (step S29), the recording data of the contents of the audio data and the communication data (packet data) is compared with the audio data and the communication data (packet data) in the reproduction mode. You may do it.

[Manual and automatic specification of “screen checkpoint”]
For step S7 shown in FIG. 3 and step S28 shown in FIG. 6, instead of or in addition to specifying the presence / absence of “screen checkpoint” by the user's operation (manual specification), the operation test program 15 automatically To be specified (automatic specification).

  In the case of manual designation, the user inserts a screen check point (step S7 shown in FIG. 3). If the user does not insert a screen checkpoint, OK / NG determination (step S29 shown in FIG. 6) is not performed in the reproduction mode. In the case where the operation by the user takes a long time and the check by the screen checkpoint is not performed during that time, even if an unexpected error occurs during the execution of the reproduction mode, the scenario playback continues and the terminal operation continues. Therefore, there is a possibility that the situation at the time of error occurrence will change. This is not desirable from the viewpoint of error detection.

  In the case of automatic designation, the operation test program 15 automatically inserts a screen checkpoint (in response to a screen transition or a specific device signal) without the user's intention in the recording mode (step S7 shown in FIG. 3). . This function eliminates the need for the user to be aware of the creation of a large number of screen checkpoints (step S7 shown in FIG. 3) in a scene where the terminal operation in the recording mode takes a long time. It becomes possible to carry out creation. Further, in the reproduction mode, the screen checkpoints automatically inserted by this function can instantly catch the occurrence of an error at a location that is not assumed by the user (step S28 shown in FIG. 6). It becomes possible to cancel the operation of the portable terminal 1 after the occurrence of an error, which could not be realized by designation.

  For example, when performing an e-mail transmission test, the user starts an e-mail application and records a procedure of creating / sending an e-mail. At this time, in order to confirm the mail transmission result of the main purpose of the test, the operation in the reproduction mode when inserting “display of the mail transmission result screen” by manual designation as an image check point is considered.

  Here, after an e-mail application is started, if any error occurs when “display mail creation screen” is displayed, warning information such as a pop-up is displayed on the screen. However, since the screen checkpoint is not designated by manual designation, the input signal during mail creation is continuously transmitted to the mobile terminal in the reproduction mode. At this time, depending on the content of the input signal to be transmitted, the displayed warning information such as pop-up is deleted. After that, it progresses to “display of mail transmission result screen”, and it becomes NG determination for the first time, and the image of the mobile terminal is acquired. At this time, the pop-up etc. that should have been originally acquired when the error occurred Since display of warning information cannot be acquired, it is not preferable as a test result.

  When considering the same case with automatic designation, screen checkpoints automatically inserted by the operation test program 15 are, for example, “launch e-mail application”, “display mail creation screen”, “display mail transmission result screen”. Etc. are automatically inserted. In the case of the above error occurrence, warning information such as pop-up generated when “display mail creation screen” is displayed as an NG determination at the screen checkpoint of “display mail creation screen” by automatic insertion. Therefore, it is possible to detect NG at the moment when warning information such as a pop-up occurs, and it is possible to acquire information that is missed by OK / NG determination at an image checkpoint by manual designation without omission. Become.

  From these points, when performing simple application launch confirmation such as “launching email application” as described above, automatic designation is used, and points that can only be confirmed by manual designation (confirmation of text content entered on the mail creation screen) Etc.), it becomes easier for the user to study the screen checkpoints, so that the scenario creation becomes easier. Manual designation is performed at the location intended by the user in order to obtain advanced operation test results, and automatic designation facilitates scenario creation work and prompts abnormal termination of the operation test target in the reproduction mode as soon as possible. It becomes possible to detect. The accuracy of operation tests can be improved by using both manual specification and automatic specification.

  As described above, the test program of the present invention directly acquires an input signal generated by a user's input operation before reaching the OS, and generates a scenario from the acquired input signal. Sometimes, the user's input operation can be completely reproduced. In the conventional method of acquiring an event from the OS, the event cannot be acquired if the OS has abandoned the event generation from the input signal, but can be acquired in the present invention.

  Further, since all input signals can be acquired, communication-related input signals generated from input operations and screen transitions can also be acquired and reproduced.

  In addition, since the test program of the present invention is stored and executed in the recording area of the mobile terminal, the mobile terminal includes an external terminal for monitoring, a camera for screen acquisition, a microphone for audio acquisition, and the like. There is no need to connect. Since the operation test can be carried out with a single mobile terminal, the cost for equipment procurement is not necessary, and there are no restrictions on the location of the operation test. Can be tested.

  Further, the test program of the present invention can easily process a scenario generated from the acquired input signal, and can shorten the test pattern creation process. In addition, since the scenario can be copied and distributed and a reproduction operation test can be performed, the reproduction operation test can be performed simultaneously on a plurality of portable terminals.

  The present invention can be embodied in many forms without departing from its essential characteristics. Therefore, it is needless to say that the above-described embodiment is exclusively for description and does not limit the present invention.

DESCRIPTION OF SYMBOLS 1 Mobile terminal 2 Control apparatus 3 Operating system 5 Input apparatus 6 Microphone 7 Hardware key 8 Software key 9 Touch panel 10 Recording apparatus 11 Internal storage 12 Application 15 Operation test program (test program)
16 External storage 20 Output device 21 Speaker 22 Display 23 Lamp 24 Vibration device 31 Main body button 32 Main body key 35 Recording icon 36 Reproduction execution icon 37 Result display icon 39 Recording display icon 40 Recording operation screen 41 Recording management screen 42 Scenario execution management Screen 44 Result viewer screen 45 Specified range 51a, 51b, 51c Record button 52a, 52b, 52c Record button (saved)
53a Save button 53b Delete button 54 Scenario execution button 100 Mobile terminal 103 Operating system 105 Input device 115 Test program 120 Monitoring terminal

Claims (7)

An operation test program installed in a recording area of a mobile terminal and testing the operation of the mobile terminal,
The operation test program is a recording mode for acquiring all input signals that are commands transmitted from the input device operated by the user to the operating system, recording the input signals, and creating a scenario;
An operation test program for a portable terminal, comprising: a reproduction mode for transmitting the input signal that reproduces an operation from the scenario to the operating system from the operation test program. Acquisition of the input signal in the recording mode is performed at a timing during which the input signal reaches the operating system from the input device,
The mobile terminal operation test program of claim 1, wherein the reproduction of the input signal in the reproduction mode transmits the input signal to an operation system at an arbitrary timing. The operating environment of the operation test program is such that the recording mode and the reproduction mode can be executed only by the portable terminal installed in the recording area, and an external monitoring terminal is unnecessary. The operation test program for a portable terminal according to claim 1 or 2. For the display image displayed on the screen of the mobile terminal based on the input signal, the operation test program includes the display image recorded in the recording mode and the display image reproduced in the reproduction mode. The operation test program for a portable terminal according to any one of claims 1 to 3, wherein all or a part of the differences can be determined by comparison. The operation test program includes the voice data and / or communication data (packet data) recorded in the recording mode for voice data and / or communication data (packet data) issued by the portable terminal based on the input signal. Data) and the audio data and / or the communication data (packet data) reproduced in the reproduction mode, and it is possible to determine all or a part of differences. The operation test program for a portable terminal according to any one of claims 1 to 4. The reproduction mode specifies the number of repetitions and reproduction range when reproducing the scenario,
6. The operation test program for a portable terminal according to claim 1, wherein the operation test program is executable and is automatically executed from the start to the end of reproduction. 2. The reproduction mode according to claim 1, wherein when an operation test result error occurs during reproduction of the scenario, notification is made by creating an error log file and operating the output device of the portable terminal. 6. The mobile terminal operation test program according to any one of 6 above.

Images