WO2014137014A1

WO2014137014A1 - Auto-verification method of smart application using terminal automatic execution control

Info

Publication number: WO2014137014A1
Application number: PCT/KR2013/001914
Authority: WO
Inventors: 정호욱; 김미희
Original assignee: (주)인프라웨어테크놀러지
Priority date: 2013-03-08
Filing date: 2013-03-09
Publication date: 2014-09-12
Also published as: KR20140110520A

Abstract

The present invention relates to a smart application verification technique using a terminal automatic execution control, in order to solve the problem that it is costly and time consuming for a developer of an android application to precisely verify the integrity of an application for various models of android terminals. According to the present invention, a smart application developer uploads a developer's own android application and sets a test sequence in the situation where a plurality of android terminals for respective models are provided in a remote place, and then the developer is provided with the result in which the android application has been automatically executed in the plurality of android terminals. The present invention provides the effect of reducing the costs of purchasing terminals since each application developer does not need to buy terminals, and the effect of increasing efficiency since terminals are used all the time for tests without idle time. Moreover, the present invention provides the effect of reducing the time for verification since the verification is performed simultaneously at multiple test terminals, and the effect of reducing test labor since there is no need to test the multiple test terminals one by one.

Description

Automatic verification method of smart application using terminal automatic execution control

The present invention relates to a method for automatically verifying a smart application (eg, an Android application) using a terminal automatic execution control and a computer-readable recording medium recording an application verification program using the same.

More specifically, the present invention focuses on the fact that it is very difficult for a developer of an Android application to spend time and time intensively verifying the integrity of an application for various types of Android terminals. In the smart app developer's smart application verification technology using the terminal auto-run control that provides the developer with the result of automatically running on a number of Android devices according to the state of the smart application developers upload their Android application and set the test sequence accordingly It is about.

The Android platform is a software stack released by Google's Open Handset Alliance (OHA). The Android platform is a software package that includes the Linux kernel, virtual machine (VM), framework, and application (hereinafter referred to as "application"), and provides a software development kit (SDK) for developing Android applications. do.

Android has been proposed as a global standard platform, but over time, fragmentation has intensified with version updates and various handset releases. Therefore, in order to develop and test Android applications, terminal devices, Android versions, and carriers must be equipped with all terminal devices. You should also install the app on these terminals and test the same operation over and over. All of this is done by hand and the results are visually verified so that the tester can only verify during working hours.

Therefore, if you purchase all the terminals necessary to test a few applications, too much cost is consumed, and these purchased terminals are not used for 24 hours and are used only during the test period, which is inefficient. In order to reduce such costs, testing using the Android emulator not only reproduces the high speed of the terminal, but also multi-touch or hardware test is impossible, and the test reliability is low because it is not made in the actual terminal.

That is, according to the prior art, to test the Android application requires a lot of terminal devices and manpower because the work must be done by hand for each terminal device individually, and in particular, it is impossible to test 24 hours. In addition, since the test sequence may not be exactly the same for each terminal, it is difficult to compare the results for each terminal, and the results may not be distinguished because only the naked eye is confirmed.

This problem is not limited to Android and is common to many smart operating systems. Therefore, in the technical field, there is an urgent need for a technology development that can more efficiently, inexpensively, and with high reliability, perform an operation test on an actual terminal device for a smart application (an application running on a smart terminal operating system).

[관련기술문헌][Related Technical Documents]

1. Mobile communication terminal capable of inspecting the application and its inspection method (Korean Patent Application No. 10-2010-0126419)

2. Server system and online service for terminal management (Korean Patent Application No. 10-2011-0033879)

3. Behavior information dynamic analysis emulator of Android application and behavior information dynamic analysis system including the same (Korea Patent Application No. 10-2011-0094707)

An object of the present invention is to prepare a plurality of Android terminals in each remote location to solve the problem that the developer of the Android application is very difficult to spend a lot of money and time to thoroughly verify the integrity of the application for the Android terminal of various models. When the developer of the smart application uploads their Android application and sets the test sequence, the smart application verification technology using the terminal automatic execution control that provides the developer with the result of automatically executing the multiple Android terminals accordingly is provided. will be.

In order to achieve this problem, the method for automatically verifying a smart application using the terminal automatic execution control according to the present invention registers an application while the developer terminal 100 uploads an installation file of a verification target application to the application verification server 300. A first step of making; A second step of the developer terminal 100 setting the test sequence for the verification target application and providing the test sequence to the application verification server 300; A third step of the developer terminal 100 selecting one or more test target terminals 400 from a test terminal list provided by the application verification server 300; A fourth step in which the application verification server 300 specifies a test order corresponding to the test sequence and performs test work distribution for the selected test target terminal 400; By the cooperative operation of the application verification server 300 and the selected test target terminal 400, the application verification server 300 installs the verification target application on the test target terminal 400 and the test target terminal 400 is placed in the test sequence. A fifth step of automatically executing the verification target application and providing an automatic execution result log to the application verification server 300; The sixth step of the application verification server 300 collects the automatic execution result log to configure the entire test results and provide the entire test results to the developer terminal 100.

The second step in the present invention, the developer terminal 100 selects a specific test terminal 400 through the application verification server 300; Installing the verification target application on the selected test terminal 400 by the application verification server 300; A step A of the developer terminal 100 instructing a test of the individual items to the selected test terminal 400 through the application verification server 300; A step B of the selected test terminal 400 executing a test item commanded by the control of the application verification server 300 and providing the execution result to the application verification server 300; A step C of the application verification server 300 reflecting the execution result on the UI screen of the developer terminal 100 and generating a test script for the executed individual test item; Repeating steps A to C; The application verification server 300 collects the test script to generate a test sequence for the entire test item; may be configured to include.

In addition, the second step in the present invention, the portable test terminal 500, the step of downloading and installing the test sequence generation application and the verification target application; A step D of the portable test terminal 500 executing an individual test item in response to a user manipulation on the verification target application; Step E, in which the portable test terminal 500 reflects the execution result of the individual test item on the UI screen; A step F of the portable test terminal 500 generating a test script for the executed individual test item; Repeating steps D to F; Generating, by the portable test terminal 500, the test script by the test sequence generation application to generate a test sequence for the entire test item by collecting the test script; And providing the test sequence to the developer terminal 100 by the portable test terminal 500.

At this time, in the fifth step, the application verification server 300 tests the verification target application by the cooperative operation of the application installation deleting unit 352 of the application verification server 300 and the application executor 410 of the test target terminal 400. Installing in the target terminal 400; An application executor 410 of the test target terminal 400 automatically executing the verification target application while internally generating various change events corresponding to a user's operation with reference to the test sequence; By the cooperative operation of the application executor 410 of the test target terminal 400 and the execution log management means 353e of the application verification server 300, the test target terminal 400 collects the automatic execution result log and verifies the application verification server. Providing to 300; can be configured. In addition, the application to be verified in the present invention may be an Android application.

On the other hand, the computer-readable recording medium according to the present invention is to record the automatic application verification program for executing the automatic verification method of the smart application using the terminal automatic execution control as described above.

In addition, the computer-readable recording medium according to the present invention uploads an application installation file to be tested according to the connection of the developer terminal 100, and performs a test among a plurality of test terminals each having an Android-based application executor installed thereon. An administrative UI 310 for selecting a terminal to receive a test request and confirm a test result; When the developer terminal 100 is formed in plural and each user accesses at the same time, each user is divided into a plurality of steps in order to manage not to expose his or her application and tasks to other users, and limit the use according to the user's authority. Manager 320; When managing the application installation file uploaded by the developer terminal 100, each application is managed separately for each version and the application manager 330 for managing so that the path and package name of the installation file of each application do not overlap; A task manager 340 for instructing tasks while adjusting the order according to priorities while the user's test request is sequentially executed to assign tasks to each of the plurality of selected terminals among the plurality of test terminals; Among the plurality of test terminals to be tested, a plurality of selected terminals are managed by platform version, manufacturer, resolution, and performance, and the work progress is checked for each terminal, and the connected state or error of each terminal is checked. The terminal manager 350 is formed to record the smart application automatic verification program using the terminal automatic execution control made.

According to the present invention, the application developer does not need to purchase a terminal, the terminal purchase cost is reduced, and the terminal is always used for testing without idle time, thereby providing an effect of increasing efficiency. In addition, the verification is reduced at the same time in a plurality of test terminals to reduce the verification time, there is no need to test on a plurality of test terminals to provide the effect of reducing the test personnel.

1 is a diagram showing an entire system in which an automatic verification method of a smart application using a terminal automatic execution control according to the present invention is implemented.

2 is a view showing a detailed configuration for the interworking of the application verification server and the test terminal in the present invention.

3 is a view for explaining the detailed configuration of the terminal manager implemented in the application verification server in the present invention.

Figure 4 is a flow chart illustrating a method for automatic verification of smart applications using the terminal automatic execution control according to the present invention.

5 is a flowchart illustrating a first embodiment of a process of a developer setting up a test sequence in the present invention.

6 is a flow chart illustrating a second embodiment of a process for a developer setting up a test sequence in the present invention.

7 is a view showing an activity analysis and script generation process for the Android application in the present invention.

8 is a diagram illustrating tracking of an execution path using activity execution tree information in accordance with the present invention.

Hereinafter, with reference to the drawings will be described in detail the present invention. The technical idea of the present invention may be commonly applied to a smart operating system, but the present specification will be described based on more than one Android.

1 is a diagram illustrating an entire system 1000 in which an automatic verification method of a smart application using the terminal autorun control according to the present invention is implemented. Referring to FIG. 1, the entire system 1000 includes a developer terminal 100, a network 200, an application verification server 300, and a plurality of test terminals 400.

The developer terminal 100 is a device operated by a person who develops an Android application, and generally includes a personal computer or a laptop computer. The developer terminal 100 requests a verification test for the Android application represented by the APK file 120 to the smart application verification server 300 to verify the Android application. In the present invention, the developer UI 110 is implemented in the developer terminal 100. Preferably, the screen is formed on the application verification server 300 during the test operation.

The application verification server 300 receives a test request for the Android application from the developer terminal 100, and provides a test result for the corresponding Android application to the plurality of test terminals 400. The test terminal 400 is preferably provided in various models for each model in consideration of the background of the present invention.

Meanwhile, although the test terminal 400 is illustrated as being directly connected to the app verification server 300 in FIG. 1, the test terminal 400 and the app verification server 300 may be connected through the network 200. .

2 is a diagram illustrating a detailed configuration for interworking the application verification server 300 and the test terminal 400 for the present invention. App verification server 300 is configured to include a management UI 310, a user manager 320, an application manager 330, a task manager 340, a terminal manager 350. In addition, the test terminal 400 includes an application executor 410 for performing a specific Android application according to a specific test sequence under the control of the application verification server 300.

First, the management UI 310 includes an application registration means 311, a test sequence setting means 312, a log viewer means (313). The user of the developer terminal 100 accesses the application verification server 300 through the network 200, uploads the installation file (APK file) 120 of the Android application to be tested, and requests a test from among the plurality of test terminals 400. Select the terminal you want to. Next, the test sequence is set by specifying the item (test scenario) to be tested for the Android application, and finally, the test result is checked. The application is executed and verified in a plurality of test terminals 400 according to a test environment (application, terminal device specific) and a test method (test sequence) input by the user of the developer terminal 100.

To this end, the application registration means 311 of the management UI 310 registers the application installation file 120 and specifies the test terminal 400. The test sequence setting unit 312 determines a scenario in which the application is executed and verified in the plurality of test terminals 400 according to a test environment, a test method, and an expected result input by the user. The log viewer means 313 performs a function of providing the test result to the user of the developer terminal 100 through the developer UI 110.

The test terminal 400 is provided with an app executor 410 to implement an Android app test. The app executor 410 includes an app installation means 411, an app driving means 412, an app deleting means 413, It comprises an event generating means 414, log collecting means 415. The app executor 410 is a module for executing a specific operation on the test terminal 400 according to a command transmitted from the app verification server 300, and the app executor 410 is also preferably implemented as an Android application.

The application executor 410 mainly performs the following functions.

As a first function, the application installation means 411 receives and installs the application installation file 120 from the application verification server 300, the application driving means 412 drives the installed Android application for testing, the application The deleting means 413 deletes the tested Android application.

As a second function, the event generating means 414 collects the system operating environment of the test terminal 400 and responds to various change events (language setting, screen rotation, multi-touch, network setting, memory operation, Internet connection, etc.) correspondingly. ) In the actual terminal operating environment, various events occur as the user manipulates the terminal. In the present invention, since an application test is automatically executed without the user's intervention, the event generating means 414 refers to the test sequence to the user's operation. Internally generate various change events.

As a third function, the log collecting means 415 performs execution log collection. After the test terminal 400 executes various operations according to the test sequence, the log collecting unit 415 collects execution logs in order to check the operation result. This execution log is processed into a test result in the application verification server 300 is provided to the developer terminal 100 is displayed on the developer UI (110).

When the user manager 320 receives a request for using the application verification server 300 from a plurality of developer terminals 100, the user manager 320 appropriately manages Android applications and test tasks provided therefrom so as not to be exposed to other users. As a module, to do this, you manage users in several steps and limit their use according to their permissions.

Therefore, the user manager 320 includes sub-units, such as user management means 321 for managing users in stages and access rights management means 322 for granting access rights of the user.

The application manager 330 manages the application installation file 120 uploaded through the application registration unit 311 while requesting a test from the user of the developer terminal 100. A plurality of applications are uploaded from a plurality of developer terminals 100, the application manager 330 manages these applications separately for each version, so that the path and package name of the installation file does not overlap so as not to occupy storage capacity unnecessarily. do. To this end, the application manager 330 is provided with a sub configuration of the file management means 331 for managing so that the path and package name of the installation file of the application does not overlap, and the version management means 332 for managing the application separately for each version.

The task manager 340 is a module that assigns a test task to each of the plurality of test terminals 400. To this end, the verification order management means 341 installed in the job manager 340 sets the job schedule such that the order is adjusted according to the priority while the user's test request is executed sequentially. That is, the task manager 340 assigns the test terminal 400 to each test when one test terminal 400 has a large number of user's test requests.

Verification order management means 341 may be a basic consideration of the order and priority of the test request, in addition to determining the order of the associated request, the expected time required for the test, or whether the test is conducted during the day / night, etc. This may be a consideration. Since the test task is input in advance by the task manager 340, the user does not need to wait until the test is completed.

The terminal manager 350 is a module connected to the test terminal 400 to perform the control and the result check in order to actually perform the test of the Android application. For this purpose, the test environment setting means 350a and the terminal management means 350b are used. Include. The test environment setting means 350a manages a plurality of test terminals 400 to be tested by classifying them into platform versions, manufacturers, resolutions, and performances. The terminal management unit 350b is configured to check the progress status of the plurality of test terminals 400 for each terminal or to check the connected state or the error of each terminal. At the end of each task, initialize the test environment, such as deleting programs or files, so that the next task is not affected.

Through this detailed configuration, the app verification server 300 provides a system in which a plurality of users (developers) can verify their own applications using the plurality of test terminals 400 in a shared manner. The application verification system arbitrates between the developer terminal 100 and the test terminal 400. In particular, since only one application can be driven at a time in the test terminal 400, the user's request is sequentially stored in order to efficiently do this. Manage tasks to run.

Meanwhile, the applicant has already applied for the technology of analyzing and automatically executing a specific Android application using a script in the test terminal 400 as Korean Patent Application No. 10-2012-0101385 issued on September 13, 2012. In the specification, the overlapping parts thereof will be omitted by referring to the above patent applications. In the present invention, the description is mainly provided in relation to a technology for managing a plurality of test terminals 400 and distributing tasks.

3 is a view for explaining the detailed configuration of the terminal manager 350 implemented in the application verification server 300 in the present invention. The terminal manager 350 is a module for installing an Android application on a specific test terminal 400 and executing a test according to a test sequence set by an application developer. For this purpose, the test environment manager 351 and the application installation deleting unit ( 352, test management software 353, and terminal management hardware 354.

The test environment manager 351 performs a function of managing an environment for testing an Android application. First, a plurality of test terminals 400 are confirmed in advance so that the app developer can select a test target terminal as described above with reference to the application registration means 311. When the application is tested on a specific test terminal 400 according to the request of the developer, the operation state of the test terminal 400 is checked again, and the software and hardware states are stored and changed to meet the user's test request. .

The application installation deleting unit 352 is provided with the application installation file 120 for the current Android application to be tested, and installs the Android application, and after the test is terminated, the following application test is performed by deleting the Android application. Maintain a basic environment for doing so.

The environment managed by the terminal manager 350 for the plurality of test terminals 400 may be divided into a hardware state and a software environment. If you test the application several times while changing these two environments, you can check whether the application works in various states.

The test management software 353 includes a broadcast receiver managing means 353a, an activity managing means 353b, a content provider managing means 353c, a permission managing means 353d, and an execution log managing means 353e. . That is, the software state of the test terminal 400 managed by the terminal manager 350 is a broadcast receiver list, an activity list, a content provider list, a permission list, and the like.

This is described in detail in Korean Patent Application No. 10-2012-0101385 of the applicant, which is referred to simply herein.

The broadcast receiver managing unit 353a extracts intent information, which is information required for driving the Android application, by analyzing a broadcast receiver from the software code of the Android application.

Since the activity management unit 353b is composed of a number of activities, the Android application operates as the transition between activities occurs, and the activity's name, size, and additional information are analyzed when the transition is made. do.

Meanwhile, a process of generating a script and analyzing an activity for automatic execution of an Android application is as shown in FIG. 7, and a process of tracking a path for automatically executing an Android application using this activity is shown in FIG. 8. 7 and 8 are for automatically running the Android application, the test management software 353 of the application verification server 300 may be configured to perform or the application executor 410 of the test terminal 400 is performed It can also be configured to. For details of these processes, see the applicant's Korean Patent Application No. 10-2012-0101385.

7 is a diagram illustrating a process of generating a script and analyzing an activity for automatic execution of an Android application. The application management module installs the Android application in the dynamic behavior analysis unit, and the screen analysis module analyzes the screen structure and the screen components by receiving the screen information about the corresponding Android application. Based on the screen configuration information for each activity provided by the screen analysis module, the event generation module generates various input events and provides these input events to the dynamic behavior analysis unit. On the other hand, input events generated by the event generation module is delivered to the script generation module to generate a script that can be used later.

In addition, the screen analysis module may generate and store each activity execution tree information on the basis of the screen component and the input event types that require these input events, and the control unit tracks the execution path based on the activity execution tree information. You can try 8 may be an embodiment illustrating tracking of an execution path using activity execution tree information. In other words, the screen analysis module provides a function to track the execution path of the corresponding Android application through the activity tree information stored through the screen analysis.

The execution log management unit 353e receives and cleans up the log data provided from the one or more test terminals 400 as a result of the application verification test. Comparing and arranging the log data and the test sequence may determine what results are derived from the individual test terminals 400 for each test operation.

In addition, the terminal management hardware 354 includes a connection state module 354a, a test state module 354b, a load management module 354c, a network state module 354d, and a call state module 354e. That is, the hardware state of the test terminal 400 to be managed by the terminal manager 350 is about a system connection state, a test progress state, a hardware (CPU, memory, storage) load state, a network state, and a phone call state.

4 is a flowchart illustrating an automatic verification method of a smart application using the terminal automatic execution control according to the present invention. 1 to 4, first, the developer terminal 100 receives the display screen by accessing the application verification server 300 and implements it in the developer UI 110 (S11). In addition, the application verification server 300 sets up a data transmission and reception line and a plurality of test terminals 400 for the application verification (S12).

After step S12, the developer terminal 100 performs application registration with the application verification server 300 through the developer UI 110 to verify a specific Android application (S13). That is, the user accesses the system through the developer UI 110 provided by the application verification server 300 and uploads the installation file 120 of the Android application to be tested.

On the other hand, the plurality of test terminals 400 provide their status to the application verification server 300 (S14), the application verification server 300 has these terminal status information while the developer terminal 100 is connected Then, the developer UI 110 provides information so that a list of these test terminals 400 can be inquired (S15). That is, the plurality of test terminals 400 provided for the purpose of application verification update their device state to the application verification server 300 through the application executor 410 installed in advance, and such information is provided as it is the developer terminal 100. ) Is used to select a test terminal.

After step S15, the developer terminal 100 sets a test requirement to the application verification server 300 (S16). These test requirements can be considered which of the plurality of test terminals (400) to perform the application verification, and according to which scenario to run the operation test (test sequence). Preferably, after inquiring the status information of the terminals belonging to the test terminal group 400 from the application verification server 300, the terminal to be tested is selected dually, and information such as a test sequence and a test environment is input. A preferred embodiment of setting test requirements in the present invention is described below with reference to FIGS. 5 and 6.

Then, the application verification server 300 specifies the test order according to the test requirements (S17), and selectively performs the application verification test for one or more test terminals 400 selected from the test requirements (S18). .

After step S18, the application verification server 300 receives and collects the result (log data) of the application verification test from these test terminals 400 in sequence (S19), and tests based on the collected information. Providing the verification test execution result according to the requirements to the developer terminal 100 (S20).

Hereinafter, a process of performing an application verification test (S18) will be described.

First, the application verification server 300 distributes the work for performing the application verification test for one or more test terminals 400 selected from the test requirements set by the developer terminal 100 (S181). That is, the application verification server 300 designates a test order through a task manager 340, a plurality of test requirements input at a similar time by a plurality of users, to the plurality of test terminals 400 by the determined order Perform sequential task allocation for

After step S181, the application verification server 300 executes an application verification test on the test terminal 400 according to the distributed work order, and performs a verification test on a specific application on the specific test terminal 400. To first install the verification target application and set the test environment (S182).

Then, the automatic test according to the test sequence is performed (S183). The test sequence is preferably script-based, and the app executor 410 installed in the test terminal 400 executes the app according to the test sequence and generates an event therein as necessary in this process to perform an operation. For details on the process of the app executor 410 automatically executing the app according to the test sequence, refer to Korean Patent Application No. 10-2012-0101385 of the applicant.

After step S183, the test terminal 400 transmits a test result to the app verification server 300 (S184), and the app verification server 300 restores the state of the test terminal 400 to its original state (S185). ). In this case, the test terminal 400 may perform the state recovery process by itself after transmitting the test result.

FIG. 5 is a flowchart illustrating a first embodiment of a process in which a developer sets a test sequence in the present invention, and corresponds to a process of setting a test sequence in step S16. In the implementation example of FIG. 5, when the developer terminal 100 selects a specific test terminal 400 through the application verification server 300, installs a verification target application, directly executes a series of tests, and ends the script, the history is scripted. The test sequence is created by saving it as.

First, the developer terminal 100 selects one test terminal 400 from the UI screen 110 provided by the application verification server 300 (S31), and the application verification server 300 corresponds to the corresponding test terminal ( Notify the facts about the selection 400 and install the Android application to be verified (S32).

Subsequently, the developer orders a test for various individual items to the selected test terminal 400 while looking at the UI screen 110 (S33). Such individual items may be a touch event for a specific button implemented on a screen of an application under test, a zoom in / out event, a menu setting event provided in the app, and various events for manipulating a specific character operating in the app.

The application verification server 300 executes these individual test items for the selected test terminal 400 by the cooperative operation of the terminal manager 350 and the app executor 410 (S34, S35), and the app executor 410 By the cooperative operation of the log collecting means 415 and the execution log management means (353e) of the terminal manager 350 may collect the test results for the individual test items (S36, 37).

When performing a test on an individual item, the application verification server 300 generates a test script for the individual test item that was just performed (S38), and the UI screen 110 of the developer terminal 100 reflects the test result. The screen is configured (S39).

The developer continuously performs the test as desired for the application to be verified (S40), and each time the individual item is tested, the application verification server 300 generates a test script (S38).

When the developer completes all the tests, the application verification server 300 generates a test sequence by collecting the test scripts generated in this way (S41). The test sequence generated through this process is composed of a series of test histories executed by the developer while viewing the screen.

6 is a flowchart illustrating a second embodiment of a process of a developer setting test sequences in the present invention. In the implementation example of FIG. 6, when a developer performs a test while directly manipulating the portable test terminal 500 owned by the developer, a test sequence is generated by storing the history as a script.

First, the developer terminal 100 installs a test sequence generation application and a verification target application for the portable test terminal 500 (S51 and 52). In this embodiment, the portable test terminal 500 monitors various events occurring in the application to be verified, and generates a test sequence by collecting the monitored results, thereby installing a test sequence generation application.

The installation of the test sequence generation application and the verification target application may also be performed by connecting the portable test terminal 500 to the developer terminal 100 and directly transmitting and installing the installation file 120. In addition, the developer terminal 100 may upload the installation file 120 to a server device (not shown), and the portable test terminal 500 may download and install these installation files 120 through, for example, a wireless LAN. In addition, it is also possible to integrate the test sequence generation application into the verification target application and configure it as one.

Subsequently, the developer looks at the UI of the portable test terminal 500 to test various individual items (for example, touch events for various buttons implemented on the application screen, zoom in / zoom out events, menu setting events provided in the application, and operate in the application. To directly operate the portable test terminal 500 (S53), and the test result is confirmed by the developer from the UI of the portable test terminal 500 (S54).

The test sequence generation application installed in the portable test terminal 500 generates a test sequence for these individual test items (S55).

When the developer completes all the tests, the test sequence generation application collects the generated test scripts to generate a test sequence (S57), and provides the test sequence to the developer terminal 100.

The invention can also be embodied in the form of computer readable codes on a computer readable recording medium. At this time, the computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored.

Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, which may be implemented in the form of a carrier wave (eg, transmission over the Internet). . The computer readable recording medium can also store and execute computer readable code in a distributed manner over networked computer systems. And functional programs, codes, and code segments for implementing the present invention can be easily inferred by programmers in the technical field to which the present invention belongs.

In particular, in the present specification, the technical spirit of the present invention has been described with reference to the Android platform, but the present invention may be applied to other platforms that can be applied to a smart terminal, such as iOS or Tizen. It is understood that the scope of the present invention is not limited to a specific platform.

Claims

A first step of the developer terminal 100 registering the app while uploading the installation file of the app to be verified to the app verification server 300;

A second step of setting, by the developer terminal 100, a test sequence for the verification target application to the application verification server 300;

A third step of the developer terminal 100 selecting one or more test target terminals 400 from a test terminal list provided by the application verification server 300;

A fourth step of the application verification server 300 specifying a test order in response to the test sequence and performing test work distribution for the selected test target terminal 400;

By the cooperative operation of the application verification server 300 and the selected test target terminal 400, the app verification server 300 installs the verification target application on the test target terminal 400 and the test target terminal 400. A fifth step of automatically executing the application to be verified according to the test sequence and providing the automatic execution result log to the application verification server 300;

A sixth step in which the application verification server 300 collects the automatic execution result log to form a total test result and provides the full test result to the developer terminal 100;

Smart verification method of the smart application using the terminal automatic execution control configured to include.
The method according to claim 1,

The second step,

Selecting, by the developer terminal (100), a specific test terminal (400) through the application verification server (300);

Installing, by the app verification server (300), the app to be verified on the selected test terminal (400);

A step A of the developer terminal 100 instructing a test of the individual item to the selected test terminal 400 through the application verification server 300;

A step B of the selected test terminal 400 executing the commanded test item under the control of the app verification server 300 and providing the execution result to the app verification server 300;

A step C of the application verification server 300 reflecting the execution result on the UI screen of the developer terminal 100 and generating a test script for the executed individual test item;

Repeating steps A to C;

Generating, by the application verification server (300), a test sequence for all test items by collecting the test scripts;

Smart verification method of the smart application using the terminal automatic execution control, characterized in that configured to include.
The method according to claim 1,

The second step,

Downloading and installing a test sequence generation application and the verification target application by the portable test terminal 500;

A step D of the portable test terminal 500 executing an individual test item in response to a user manipulation on the verification target application;

Step E, in which the portable test terminal 500 reflects an execution result of the individual test item on a UI screen;

Step F, wherein the portable test terminal 500 generates a test script for the executed individual test item;

Repeating steps D to F;

Generating, by the portable test terminal 500, the test script by the test sequence generation application to generate a test sequence for all test items by collecting the test script;

Providing, by the portable test terminal (500), the test sequence to the developer terminal (100);

Smart verification method of the smart application using the terminal automatic execution control, characterized in that configured to include.
The method according to any one of claims 1 to 3,

The fifth step,

By the cooperative operation of the application installation deleting unit 352 of the app verification server 300 and the app executor 410 of the test target terminal 400, the app verification server 300 the test target application to the test target Installing in the terminal 400;

An application executor 410 of the test target terminal 400 automatically executing the verification target application while internally generating various change events corresponding to a user's manipulation with reference to the test sequence;

The test target terminal 400 collects the automatic execution result log by the cooperative operation of the application executor 410 of the test target terminal 400 and the execution log management means 353e of the app verification server 300. Providing to the application verification server 300;

Smart verification method of the smart application using the terminal automatic execution control, characterized in that configured to include.
The method according to any one of claims 1 to 3,

The verification target application is an automatic verification method of a smart application using the terminal automatic execution control, characterized in that the Android application.
A computer-readable recording medium recording an application automatic verification program for executing an automatic verification method of a smart application using the terminal automatic execution control according to any one of claims 1 to 3.
Upload the application installation file to be tested in accordance with the connection of the developer terminal 100, select a plurality of terminals to perform the test from each of the plurality of test terminals each of the Android-based application executor receives the test request and check the test results A management UI 310 to enable;

When the developer terminal 100 is formed in plural and each user accesses at the same time, each user is divided into a plurality of steps in order to manage each application and task not to be exposed to other users, and the use is restricted according to user rights. User manager 320; An application manager 330 for managing each application separately for each version when managing the application installation file uploaded by the developer terminal 100 and not allowing the path and package name of the installation file of each application to overlap;

A task manager 340 for instructing tasks while adjusting the order according to priority while executing a test request of a user sequentially to assign a task to each of a plurality of selected terminals among the plurality of test terminals;

Among the plurality of test terminals to be tested, each of a plurality of selected terminals is managed by platform version, manufacturer, resolution, and performance. Terminal manager 350 is formed for;

A computer-readable recording medium recording a smart application automatic verification program using the terminal automatic execution control provided.