KR101035097B1 - A test and history management system for mobile station applications using test libraries and the method thereof - Google Patents

Abstract

A mobile device application verification history management system and method for connecting to a mobile device having a wireless platform installed thereon to test an application executed on the wireless platform, and connected to a mobile device having a wireless platform installed thereon, the application executed on the wireless platform. A mobile device application verification history management system for testing the agent, the agent installation unit for loading and installing the agent module on the wireless platform of the mobile device; A script interpreter that converts a script for testing an application into test execution code that can be executed on the agent module; An execution code loading unit loading the test execution code on the mobile device and executing the test execution code on an agent module; The test execution code is provided with a configuration including an execution result receiving unit for receiving and storing the execution result data.

According to the system and method as described above, the test code can be managed and executed without depending on the wireless platform specification of the mobile device, so that the wireless platform installed in the mobile device varies from mobile carrier to carrier or the wireless platform specifications change from time to time. Even faster, mobile device applications can be tested.

Mobile Device, Application, Wireless Platform, Test, Script

Description

A test and history management system for mobile station applications using test libraries and the method

The present invention relates to a mobile device application verification history management system and method for testing an application of the mobile device implemented on the wireless platform by connecting to a mobile device installed wireless platform.

In addition, the present invention is installed on the mobile device a test library module running on the wireless platform of the mobile device and the test module used to execute the test execution code using the library, the mobile device by converting the test script prepared in advance to the test execution code The present invention relates to a mobile device application verification history management system and method for testing an application of a mobile device.

In general, when a mobile device such as a mobile phone of a new model is developed, a test of the application is performed to verify the stability and integrity of the application embedded in the mobile device. In particular, as the development cycle of new mobile devices and new product launch cycles become shorter, the work period for testing mobile device applications is shorter, while the test cases for verifying mobile device applications as the features of newly released mobile devices become high specifications It is getting bigger and more complicated.

In addition, the application development environment of the mobile device and the test environment further complicates the application test of the mobile device.

First, the application development environment of the mobile device will be described briefly. In general, the application of the mobile device is developed to be performed on the wireless platform of the mobile device. The wireless platform of a mobile device is a middleware that provides an API for developing a mobile device application. That is, the wireless platform provides a standardized function specification (or API) that runs on an operating system that directly controls the input / output or operation of the hardware of the mobile device. The application developer develops a desired application such as a game using only a standardized function specification (or API) provided. In a broader sense, a wireless platform provides a standard development environment for developing, deploying, and running applications in addition to standard APIs.

However, the problem is that the wireless platform is different depending on the mobile carrier or mobile communication method. Therefore, even if the application performs the same function, it should be made differently to be executed on the different wireless platform. Of course, due to the problems described above, efforts are being made to create a standardized platform standard of the same method in any communication company or any communication method. For example, a representative standard wireless platform in Korea is a standard that is required to provide an environment for executing applications downloaded through the wireless Internet on a mobile terminal by the Korea Wireless Internet Standardization Forum (KWISF). Is made by WIPI.

However, even if each mobile operator applies a standardized platform, the wireless platform is slightly different for each mobile operator while extending the standard platform in order to provide a special service function to each mobile operator.

In addition, each wireless platform itself is not a fixed standard, but the wireless platform specification itself changes as the demands of consumers expand as the technology develops.

That is, as the specifications of the wireless platform are different or changed, each application is developed for each wireless platform, and there is a problem that tests must be performed for each wireless platform.

Next, an application test environment of the mobile device will be described. In general, a test for an application installed on a mobile device is performed by connecting the mobile device to a mobile device verification terminal such as a PC, causing the verification terminal to perform a mobile device function according to a test scenario, and recording the result (or response of the mobile device). This is done in an analytic way.

The most commonly used test method is to use commands for communication between a mobile device and a PC. Most mobile device standard is a communication standard for controlling mobile devices through PC by connecting mobile devices to PC, and define commands that can be sent or received from PC to mobile devices and communicate with mobile devices with those commands. There is a specification. Some of the commands that can be defined are defined as commands for testing mobile device applications. That is, the command is defined as a command using the application in the mobile device, and the test is performed by transmitting the command to the mobile device from the PC and receiving the result. Usually a series of commands is passed to a mobile device to perform a test.

Therefore, the method using the command should create a command set used for the test, and make the test scenario by configuring the command in a series of commands.

Since the instruction sets for testing are instructions using an application running on a wireless platform, the task of creating a test instruction set has a similar problem to developing an application on the wireless platform described above. In other words, development and maintenance are difficult because they have to adapt to various wireless platforms and wireless platforms that are constantly changing (or evolving).

In addition, since the test scenario must be composed of instructions, there is a problem that a more complex test scenario cannot be written unless a command set composed of various instructions for a test is created.

A typical example of such a command standard is AT COMMAND, which communicates with a mobile device and a PC through an EIF (Extended InterFace) program used in WIPI. That is, the AT COMMAND is manually transferred from the PC to the mobile device to perform the test. However, as the specification for this EIF program evolves, functions need to be improved and versions have to be upgraded. Therefore, mobile device manufacturers are passive in developing AT COMMAND due to development period and cost problems. Therefore, at present, the program cannot be upgraded and only a part of the model that is different from the next model is modified in the previously applied model.

In order to solve this problem, an example of a technology for testing an application in a mobile device using a command standard for communicating with a mobile device is disclosed in [Korean Patent Registration No. 10-0794130 (published on Jan. 10, 2008), "Application and Addition of a Mobile Communication Terminal." Service automatic functional test apparatus "] (hereinafter, referred to as prior art 1). The prior art 1 is a script generator for creating instructions defined for one or more tests, and defining and writing a terminal environment applied to the test; At least one agent for receiving and applying the defined terminal environment to the terminal by the script generator, and transmitting and executing the command signal to the terminal by receiving a command signal according to the defined command; Initiating an automatic functional test device consisting of one or more verification to transmit the defined commands from the script writer to the agent for the terminal, and receives a result of the execution of the command signal from the agent for the terminal to prepare a result report have.

On the other hand, unlike the prior art 1 using the command specification to communicate with the mobile device, an example of a technology for downloading and testing a test program into the mobile device is described in [Domestic Patent Registration 10-0464006 (December 20, 2004), " Remote Diagnosis System and Method of Personal Portable Terminal "] (hereinafter, referred to as Prior Art 2). The prior art 2 is a remote diagnostic server for transmitting a self test program for error diagnosis of the terminal to the terminal at the request of the terminal, and after downloading and executing the self test program from the server to detect the cause of the error of the terminal itself; It consists of a personal portable terminal displayed on the display screen, the personal portable terminal stores a remote test code for checking the downloadability of the self-test program, and using this code to check the downloadability of the self-test program after the self Discusses the technique for downloading test programs.

In addition, another example of a technique for downloading and testing a test program into a mobile device is disclosed in Japanese Laid-Open Patent Publication No. 2003-22196, "Method for Automatically Executing a Test Program in a Mobile Terminal" (hereinafter, referred to as Prior Art 3). The prior art 3 relates to a method of automatically executing a plurality of test programs sequentially described by a test order in a program list, wherein the test program name is described by the execution order of a test for test programs stored in a server. Designating a list from the mobile terminal, sequentially notifying the mobile terminal of the name of the test program described in the designated program list, and whenever the name of the test program is notified, the mobile terminal checks the test program corresponding to the name. The present invention discloses a technique for configuring a program to be downloaded from a server, executed, and notified to the server of the result.

However, in the prior art 1, as described above, it is difficult to write and maintain a command for performing a test, and to perform a complex test. In addition, although the prior arts 2 and 3 have been improved to download the test program to be performed in the mobile device, as described above, the problem that occurs when the various and evolved of the wireless platform is still.

An object of the present invention is to solve the problems as described above, by connecting to a mobile device with a wireless platform, a mobile device application verification history management system and method for testing the application of the mobile device implemented on the wireless platform To provide.

In addition, an object of the present invention is to install a test library module to be executed on the mobile platform of the mobile device and an agent module for executing the test execution code using the library on the mobile device, the test script prepared in advance to the test execution code It is to provide a mobile device application verification history management system and method for converting the mobile device to be loaded and executed, to test the application of the mobile device.

In order to achieve the above object, the present invention relates to a mobile device application verification history management system for testing an application running on the wireless platform by connecting to a mobile device installed with a wireless platform, the agent module on the wireless platform of the mobile device Agent installation unit for loading and installing; A script interpreter that converts a script for testing an application into test execution code that can be executed on the agent module; An execution code loading unit loading the test execution code on the mobile device and executing the test execution code on an agent module; And an execution result receiver configured to receive and store the result data of the test execution code execution.

In addition, the present invention is a mobile device application verification history management system, wherein the script interpreter converts the test execution code to be executed by calling the test-only interface functions of the agent module, the test-only interface functions of the mobile device Characterized in that running on a wireless platform.

In another aspect, the present invention is a mobile device application verification history management system, the system further comprises a script writing unit for receiving a script for testing the application of the mobile device.

In another aspect, the present invention is a mobile device application verification history management system, wherein the agent module executes the test execution code on a wireless platform of the mobile device, and transmits the execution data of the test execution code to the execution result receiving unit. Characterized in that.

In addition, the present invention in the mobile device application verification history management system, the agent installation unit, by bringing the standard information of the mobile device or the standard information of the wireless platform installed in the mobile device, the test library and agent corresponding to the standard The module is loaded and installed on the wireless platform of the mobile device.

In addition, the present invention in the mobile device application verification history management system, the test-only interface function may be implemented differently according to the standard of the mobile device or the standard of the wireless platform installed in the mobile device, the call or The returned interface is the same.

The present invention further includes a script management means for storing and managing a script corresponding to a function of the mobile device and a set of test rules in a mobile device application verification history management system, wherein the script creation unit includes a function of the mobile device. Obtaining information, receiving a test rule set for the function of the mobile device, and receiving a script corresponding to the function of the mobile device and the test rule set from the script management means.

In addition, the present invention further comprises a test result management means for storing and managing the test results for the mobile device by dividing the test results for the mobile device according to the model and test case of the mobile device, the execution result receiving unit Bringing the model information of the mobile device, and transmitting the received execution result data and the model information of the mobile device to the test result management means.

In another aspect, the present invention is characterized in that in the mobile device application verification history management system, the test result management means is to create a report and output each test result for the application installed in the mobile device.

In another aspect, the present invention is characterized in that in the mobile device application verification history management system, the script is written using instructions defined by a document type definition (DTD) according to XML.

In addition, the present invention in the mobile device application verification history management system, wherein the script is written by a script writing rule including a variable declaration rule, a repetition / control statement writing rule, a function call rule, an operator use rule, commenting rule, The variable declaration rule includes an integer, a string, and a boolean as a type of a variable, the type of the variable being determined when the variable is defined, and the variable having a predetermined valid range. A rule including IF, ElseIF, Else, While, For, and a conditional statement executed only by a predetermined condition and a looping statement executed until a predetermined condition is satisfied. A rule that defines a set of scripts as a function and a function that can pass arguments to the function. In addition, the operator usage rule includes a logical operator, an arithmetic operator, a priority operator, and an assignment operator as available operators, and as a result of the logical operation, true is 1 and false is 0. And rules for handling operations, wherein the commenting rules are characterized by using XML commenting rules.

In another aspect of the present invention, in the mobile device application verification history management system, the script creation unit, using an XML parser to check whether the script conforms to the grammar for XML, and shows an error or a test result if there is no error A script checker for converting to a Document Object Model (DOM); A script parser that receives a DOM from the script checker and checks whether the DOM is written according to the script writing rule; And a script runner that virtually executes the DOM and shows an operation execution result.

In addition, the present invention is characterized in that in the mobile device application verification history management system, the script management means or the test result management means is built on a separate server connected to the network.

The present invention also relates to a mobile device application verification history management method for testing an application of the mobile device implemented on the wireless platform by connecting to a mobile device on which the wireless platform is installed, and (a) on the wireless platform of the mobile device. Loading and installing an agent module on the wireless platform of the mobile device, the agent module including a test library module configured with test only interface functions to be executed; (b) receiving a script for testing an application of the mobile device; (c) converting the test script into test execution code that can be executed on a wireless platform of the mobile device, wherein the test execution code calls the test-only interface functions; (d) loading and executing the test execution code on the wireless platform of the mobile device; (e) receiving and storing the result data executed by the test execution code, wherein the agent module executes the loaded test execution code on the wireless platform of the mobile device, and executes the test execution code. It is characterized by the transmission of the result data.

In addition, the present invention is a mobile device application verification history management method, the step (c) is the test execution code is converted to be executed by calling the test-only interface functions of the agent module, the test-only interface functions are the mobile It runs on the wireless platform of the device.

In addition, the present invention is a mobile device application verification history management method, characterized in that the method further comprises the step of (b) receiving a script for testing the application of the mobile device before step (c).

In another aspect, the present invention is a mobile device application verification history management method, wherein the agent module executes the test execution code on a wireless platform of the mobile device, and transmits the result data of the test execution code to the verification system. It is characterized by.

In addition, in the mobile device application verification history management method, the step (a), the standard library of the mobile device or the standard information of the wireless platform installed in the mobile device, the test library corresponding to the standard And installing and loading an agent module on the wireless platform of the mobile device.

In addition, the present invention in the mobile device application verification history management method, the test-only interface function may be implemented differently according to the standard of the mobile device or the standard of the wireless platform installed in the mobile device, the call or The returned interface is the same.

In addition, the present invention is connected to the network and the test server for storing and managing the program module and test script recording the mobile device application verification history management system, the mobile device application verification history management for testing the application of the mobile device implemented on the wireless platform A method comprising: (f) connecting to and authenticating a test server; (g) downloading the mobile device application verification history management system module from the test server; (h) connecting with a mobile device to obtain function information from the mobile device; (i) receiving a test rule set for the function of the mobile device; (j) downloading a script corresponding to the function and the rule set by transmitting the function and the test rule set to the test server; (k) if there is no script corresponding to the function and the rule set, directly receiving a script corresponding to the function and the rule set; (l) delivering the script to the mobile device application verification history management system module to execute a test for the mobile device application; (m) transmitting the executed test result data to the test server; (n) accessing the test server and requesting a test result for the mobile device, and transmitting and displaying the test result data.

In addition, the present invention is a mobile device application verification history management method, step (n), characterized in that the test results for the mobile device by showing the model and the test case of the mobile device by dividing or writing a report .

In addition, the present invention is a mobile device application verification history management method, wherein the script, characterized in that written using the instructions defined by DTD (Document Type Definition) according to the standard of XML.

The present invention also relates to a computer-readable recording medium recording the mobile device application verification history management method.

As described above, according to the mobile device application verification history management system and method according to the present invention, it is possible to manage and execute the test code without depending on the wireless platform standard of the mobile device, the wireless platform installed in the mobile device Even if the mobile carriers are different or the specifications of the wireless platform change from time to time, it is possible to test mobile device applications more quickly.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the drawings.

In addition, in describing this invention, the same code | symbol is attached | subjected and the repeated description is abbreviate | omitted.

First, an embodiment of the configuration of the entire system for implementing the present invention will be described with reference to FIG. 1 is a diagram illustrating the configuration of an entire system for implementing the present invention.

As shown in FIG. 1, as an example for implementing the present invention, the mobile device 10 is connected to the verification terminal 20 to perform a test. In addition, the verification terminal 20 is connected to the network 15 and the test server 21 for downloading a program module or test script for creating a test scenario for testing a mobile device application or sending a test result.

As described above, the mobile device 10 is provided with a wireless platform for driving an application. That is, as shown in FIG. 2, the mobile device 10 is composed of a wireless platform 11, an application 12, and an agent module 13. In addition, although the mobile device 10 is not shown, an operating system for directly controlling hardware and processing input / output is installed, and the wireless platform 11 is middleware implemented on the operating system.

On the other hand, the configuration of the mobile device 10 is a software configuration, it is also configured in hardware, such as a communication module, input and output devices, but this is a well-known technology, detailed description thereof will be omitted.

As described above, the wireless platform 11 is middleware that provides a standard API for writing an application of the mobile device 10.

In addition, the agent module 13 provides a test-only API for writing test execution code for testing an application of the mobile device 10, and receives the test execution code from the verification terminal 20 to wirelessly operate in the mobile device. It is a kind of middleware running on the platform 11.

However, since the test-only API mainly uses the API of the wireless platform 11, in order to distinguish it from the API of the wireless platform, it will be referred to as a test library below. That is, the test library may be viewed as a set of interface functions for testing. Of course, the test dedicated interface function may be called and used by an application of the mobile device in addition to the test.

The verification terminal 20 is a terminal connected to the mobile device 10 to test the mobile device 10. The verification terminal 20 may correspond to any terminal having a computing function such as a PC, a notebook, a PDA, and the like.

The verification terminal 20 sends the program for the agent module to the mobile device 10 to the mobile device 10, transmits the execution code for testing the application of the mobile device to the mobile device and receives the result.

On the other hand, the connection between the verification terminal 20 and the mobile device 10 may be a USB method, a method using a mobile device dedicated connector, a wireless method such as Bluetooth. In addition, the mobile device 10 can also be connected through a wireless communication network for transmitting and receiving calls and data. That is, since the present invention sends a test execution code to the mobile device 10 to execute the test execution code in the mobile device, the communication between the verification terminal 20 and the mobile device 10 becomes a certain communication method. If you can.

The test server 21 is installed in the verification terminal 20 to store and manage a mobile device application test module that tests the mobile device 10, that is, the mobile device application verification history management system 30. Therefore, when the verification terminal 20 does not have the test module (or verification system) when the mobile device 10 tries to test the verification terminal 20, the verification terminal 20 connects the application verification system 30 to the test server 21. request. At this time, the test server 21 to download and install the application verification system 30 to the verification terminal 20.

In addition, the test server 21 manages a script for creating a test scenario. That is, the test server 21 classifies and stores the created various scripts and sends appropriate scripts according to the request of the verification terminal 20. If a script corresponding to the requested verification environment does not exist, ask the administrator (or script manager) to write a script corresponding to the new environment.

On the other hand, the script is converted into test execution code that can be executed in the mobile device 10 by the verification terminal 20. That is, a test scenario is made into a script, the script is converted into executable code, and the converted executable code is loaded into the mobile device 10 and executed, so that a test is performed.

When the verification terminal 20 completes the test for the mobile device 10, the test terminal 20 transmits the test result data to the test server 21. The test server 21 receives and stores test result data executed in each mobile device 10. In particular, the test result data is classified and stored for each model and test case of the mobile device and stored in a database. And when the mobile device verification personnel accesses and requests the test server 21, the test server 21 retrieves and sends the corresponding test result data at any time. The mobile device verification person can analyze the application problems of the mobile device by searching the accumulated test result data.

In particular, the test server 21 accumulates and manages test result data tested in various environments, so that the test script corresponding to the test environment of another mobile device 10 may be searched for and provided with a test script corresponding thereto. have.

The network 15 is a network capable of bidirectional communication such as the Internet. If the network 15 is a public network such as the Internet, the mobile device 10 may be tested anywhere the network 15 is connected. In addition, if a place for intensive testing of a large number of mobile devices, such as a mobile device manufacturing plant or a mobile device A / S center, a closed network is not necessarily an open network.

Meanwhile, in the exemplary embodiment referring to FIG. 1, the verification terminal 20 and the test server 21 are separately configured, but another embodiment in which the mobile device 10 and the test server 21 directly connect without the verification terminal 20 is performed. An example is possible. The mobile device 10 is connected to the test server 21 through a wireless communication network for making calls and data transmission and reception. The test server 21 sends a test execution code to the mobile device 10 through a wireless communication network, and the mobile device 10 downloads and executes the test execution code. The mobile device 10 sends the test result data, which is the result of execution, directly to the test server 21.

Next, a mobile device application verification history management system according to an embodiment of the present invention will be described with reference to FIG. 3 is a block diagram of the configuration of the mobile device application verification history management system according to an embodiment of the present invention.

As shown in FIG. 3, the mobile device application verification history management system 30 includes an agent module installation unit 31, a script creation unit 32, a script analysis unit 33, an execution code loading unit 34, and an execution result. It consists of a receiver 35. In addition, the script management means 36 and the test result management means 37 may be further included.

The agent module installation unit 31 includes an agent module including a test library composed of test-only interface functions executed on the wireless platform 11 of the mobile device 10 on the wireless platform 11 of the mobile device 10. Load and install on.

The agent module is a module that is executed on the wireless platform of the mobile device, and executes the test execution code loaded from the execution code loading unit 31 on the wireless platform of the mobile device, and the result data of executing the test execution code. Is a program module for transmitting to the execution result receiving unit 35.

As shown below, the test execution code executes on the wireless platform 11 by calling functions of the test library of the agent module. Therefore, the test execution code can be seen as running on the agent module. That is, running on the agent module refers to executing on the wireless platform by calling the test-only interface functions of the agent module.

The test dedicated interface function may be implemented differently according to the standard of the mobile device or the standard of the wireless platform 11 installed in the mobile device 10. The interface for calling or returning the function is the same. Accordingly, the agent module installation unit 31 obtains specification information of the mobile device or specification information of a wireless platform installed in the mobile device, and wirelessly installs an agent module including a test library corresponding to the standard. Load and install on the platform.

That is, the present invention is a method of performing a test by directly loading and executing the test execution code on the mobile device (10). By the way, as seen in the prior art, the wireless platform 11 may have a variety of specifications. The functions included in the test library are implemented differently according to the specifications of the wireless platform 11, but the interface for calling or converting the functions is implemented in the same way.

Test execution code is a kind of mobile device application. Therefore, the test execution code is run on the wireless platform (11). Instead, it is implemented using the functions of the test library, unlike typical mobile device applications. The test execution code may directly use (or call) APIs of the wireless platform 11 which are commonly used in the wireless platform 11, but do not use other APIs related to the test or per wireless platform 11. Instead, the test execution code is made using the functions included in the test library.

Therefore, even if different mobile devices 10 have different wireless platforms 11, one execution code can be executed in all of the mobile devices 10. Instead, the test-only interface functions included in the test library are internally implemented differently if the wireless platform 11 is different.

The script writing unit 32 receives a script for testing an application of the mobile device.

The script is written using commands defined by a document type definition (DTD) according to the XML standard.

The script is prepared by a script writing rule including a variable declaration rule, a repetition / control statement writing rule, a function call rule, an operator use rule, and a commenting rule.

The variable declaration rule includes an integer, a string, and a boolean as a type of a variable, the type of the variable being determined when the variable is defined, and the variable having a predetermined range valid. Include rules. It also supports automatic variables.

The repetition / control statement creation rule includes a conditional word including IF, ElseIF, Else, While, For, and a condition for executing a conditional statement executed only by a predetermined condition, and a rule for generating a repeating statement executed until a predetermined condition is satisfied. That is, it is a loop statement such as a For or While statement that is used when the script is executed more than once, and the control statement is used when it is not executed or is executed by some condition.

In the function call rule, a series of scripts are defined as a function, and the function includes a rule that can pass arguments. When a unit of script is composed of several scripts instead of a single sentence, the unit can be viewed as a function. In this case, the script language rule used can be a function call. Functions can also pass arguments.

The operator usage rules include logical operators, arithmetic operators, precedence operators, and assignment operators as available operators, and the result of logical operations is assumed to be 1 for true and 0 for false. Contains rules for processing

In other words, when storing values through variables of scripting language, they must support the operation of these values. In this case, the following operators are used.

-Support operator

-Logical operators:! =, ==, ◀, ▶, ◀ =, ▶ =, AND, OR

Arithmetic operators: +,-, *, /

-Priority operator: (,)

Assignment operator: =

And if logical expression and expression coexist, we cannot guarantee correct operation. However, TRUE is 1 and FALSE is 0.

The annotation rule uses an annotation rule of XML. That is, it is used in the form of <<!-Comment-> ", which is the format of comments used in XML.

An example in which the above script writing rule is created by a document type definition (DTD) of XML is shown in FIG. 4. In addition, an example of a script created by the above-described writing rule is shown in FIG.

The script writing unit 32 checks whether the script conforms to the grammar for XML using an XML parser, and displays a check result error or, if there is no error, a script checker for converting the script into a Document Object Model (DOM); A script parser that receives a DOM from the script checker and checks whether the DOM is written according to the script writing rule; It includes a script runner that virtually executes the DOM and shows the result of performing the operation.

That is, the script writing unit 32 includes a script writing environment for converting the created script into test execution code or checking whether it works properly. The scripting environment includes a script checker, a script parser, and a script runner.

First, the Script Checker.

The script checker first reads an XML document through an I / O module. At this point, a basic check of the XML grammar is done using an XML parser (eg MSXML Parser). For example, the pair of opening and closing tags must match (well-formed check), and the XML document is written (validation check) according to the defined grammar (DTD). If there were no problems with this process, the XML document is converted to the Document Object Model (DOM) and the result is passed to the Script Parser.

As shown in FIG. 6A, if a problem occurs, the user is notified of the problem through the UI module and the execution process is stopped. At this time, the location and the details of the problem that occurred to the user should be displayed, as well as suggest a solution.

 On the other hand, the program used in parsing XML documents is MSXML 3.x provided by MS. The latest version is MSXML 7.x, which not only requires more stringent XML syntax, but also incorporates many new concepts (Scheme concepts are introduced). Therefore, there is a problem of backward compatibility with XML documents, and this problem needs to be considered.

The script checker inserts additional information about the script XML document. Main insert contents are line position and debug related information about XML tag. This information is later used to notify the user of errors or the progress of the script parser and script runner.

Next, a script parser will be described.

If the Script Checker is to determine and analyze errors in XML grammar, the Script Parser determines and analyzes errors in the actual programming language. That is, it checks whether an undeclared variable is not used, there are no math errors, and whether the function returns after it is called.

  In particular, the Script Parser constructs a symbol table to check for errors in variable names and function names. The symbol table is possible by searching the DOM received from the Script Checker in depth-first search. However, this method has a problem that it takes a long time if the XML document is complicated or very long.

Script Parser checks the type as well as the existence of the name of both variables and functions. Therefore, the symbol table stores not only the name of the variable but also the type.

If the script parser finds an error in the XML document, it informs the user through the UI module to induce modification.

And the script parser passes the DOM to the Script Runner if there are no errors in the XML document.

Next, as shown in Figure 6b, the script runner (Script Runner) performs an operation in accordance with the content of the script (Script) described. The operation execution process is displayed to the user in real time through the UI module, and when an error occurs during execution, the script runner stops the operation.

  If the operation is completed without error, the result report is displayed through the UI module. The contents of the result report may include the total execution time. Meanwhile, the script runner stops the operation that was performed when an error occurred.

Next, the screen of the UI (user interface) module in the scripting environment will be described with reference to FIG. 6C. The screen is roughly divided into a workspace window, an editor window, and an output window.

In the Workspace Window, you edit the environment values for your program. For example, set the environment such as test server IP and port. The Hierarchy displays a list of script files in the Workspace Window. Information about the list is read from the test server. Double click the script file displayed in the list to open it. Open script files are displayed in an editor window.

The Editor Window creates, modifies, and saves script files. The main tag in the script file is marked high-light. In addition, as described above, if an error occurs in the script checker, the script parser, or the script runner, an error occurred is displayed. When selecting the displayed error, move to the location where the error occurred. It also displays a log of its progress.

Such script development environment does not depend on the wireless platform (11). This is because the scripts are interpreted and converted into test execution codes, which all use test libraries that do not depend on the specific wireless platform 11.

On the other hand, the script management means 36 stores and manages the script corresponding to the function and test rule set of the mobile device. Accordingly, the script writing unit 32 receives the function information of the mobile device, receives a test rule set for the function of the mobile device, and outputs a script corresponding to the function of the mobile device and the test rule set. It receives from the script management means 36.

The script management means 36 may be means implemented in the test server 21. In other words, the UI (user interface) module is to import the script file from the test server 21, it may be received by receiving from the script management means 36 implemented in the test server 21.

The script interpreter 33 converts the test script into test execution code that can be executed on a wireless platform of the mobile device, and converts the test execution code to call the test-only interface functions.

The script creation unit 32 described above also includes a working environment such as writing and debugging a script, while the script interpreter 33 converts the test script completed by the script creation unit 32 into executable code. to be. Therefore, there may be program modules commonly used in the script generator 32 and the script interpreter 33.

The execution code loading unit 34 loads and executes the test execution code on the wireless platform 11 of the mobile device 10, and the execution result receiver 35 receives the result data executed by the test execution code. Save it.

On the other hand, the test result management means 37 stores the test results for the mobile device for each model and test case of the mobile device to store and manage. Accordingly, the execution result receiver 35 obtains model information of the mobile device and transmits the received execution result data and the model information of the mobile device to the test result management means 37.

The test result management unit 37 may generate and output a report of each test result for the application installed in the mobile device.

On the other hand, the script management means 36 or the test result management means 37 may be constructed as a means of a separate server connected to the network. That is, as the script management means 36 may be a means included in the test server 21, the test result management means 37 may also be implemented in the test server 21.

Next, a mobile device application verification history management method according to an embodiment of the present invention will be described with reference to FIG. 7 is a flowchart illustrating a mobile device application verification history management method according to an embodiment of the present invention.

As shown in Figure 7, the mobile device application verification history management method comprises the steps of (a) loading and installing the agent module on the wireless platform of the mobile device (S11); (B) receiving a script for testing the application of the mobile device (S12); (c) converting a script for testing an application into test execution code that can be executed on the agent module (S13); (d) loading the test execution code into the mobile device to execute on the agent module (S14); (e) receiving and storing the result data of executing the test execution code (S15).

The agent module is a program module that executes the loaded test execution code on a wireless platform of the mobile device and transmits the result data of executing the test execution code.

In particular, step (c) converts the test execution code to be executed by calling the test-only interface functions of the agent module, but the test-only interface functions are executed on the wireless platform of the mobile device.

In particular, in the step (a), the specification information of the mobile device or the specification information of the wireless platform installed in the mobile device is imported, and the test library and agent module corresponding to the standard are loaded on the wireless platform of the mobile device. Install it.

The test dedicated interface function may be implemented differently according to the standard of the mobile device or the standard of the wireless platform installed in the mobile device. The interface for calling or returning the function is the same.

Next, a mobile device application verification history management method according to another embodiment of the present invention will be described with reference to FIG. 8 is a flowchart illustrating a mobile device application verification history management method according to another embodiment of the present invention.

Mobile device application verification history management method according to another embodiment is implemented on a wireless platform on the premise that connecting to the network and the test server that stores and manages the program module and test script recording the mobile device application verification history management system described above Test the application of a mobile device.

As shown in FIG. 8, the mobile device application verification history management method includes (f) accessing the test server and authenticating (S21); (g) downloading the mobile device application verification history management system module from the test server (S22); (h) connecting with a mobile device to obtain function information from the mobile device (S23); (i) receiving a test rule set for the function of the mobile device (S24); (j) transmitting the function of the mobile device and the test rule set to the test server and downloading a script corresponding to the function and the rule set (S25); (k) if there is no script corresponding to the function and rule set, directly receiving a script corresponding to the function and rule set (S26); (l) delivering the script to the mobile device application verification history management system module to execute a test for the mobile device application (S27); (m) transmitting the executed test result data to the test server (S28); (n) accessing the test server and requesting a test result for the mobile device comprises sending and displaying the test result data (S29).

In particular, step (n) shows the test results for the mobile device by dividing the model and the test case of the mobile device or write a report. In addition, the script uses a test library, characterized in that the script is written using commands defined by a document type definition (DTD) according to the XML standard.

Insufficient portions of the description of the method for managing the mobile device application verification history refer to the description of the mobile device application verification history management system described above.

Next, the effects of the mobile device application verification history management system and method according to the present invention will be described with reference to FIGS. 9 and 10. 9 illustrates the relationship between each business entity in the case of the mobile device application verification history management in accordance with the present invention, Figure 10 is a mobile device application verification history management according to the conventional method and the method according to the present invention. This table shows the differences.

As shown in FIG. 9, in the related art, a mobile communication provider directly presents a command interface standard (EIF standard, etc.) to a manufacturer, and according to the standard, the manufacturer verifies the mobile device application and reports it to the service provider. Regardless of the operator's specification, it implements the indirect method of implementing only the minimum necessary functions and processing a large part through the test agent module (AQMP in the drawing).

Therefore, the present invention minimizes the communication and burden of the operator and manufacturer.

The method according to the present invention has an advantage as shown in FIG. 10A compared to the conventional method from the operator's point of view, and also as shown in FIG. 10B from the manufacturer's point of view.

As mentioned above, although the invention made by this inventor was demonstrated concretely according to the said Example, this invention is not limited to the said Example and can be variously changed in the range which does not deviate from the summary.

The present invention can be applied to the field of testing the application running on the mobile device installed wireless platform. In particular, a scenario for testing a mobile device application can be applied to the development of a mobile device application test system for writing a script using XML, converting the script into test execution code, and loading the test on a mobile device.

1 is a diagram illustrating the configuration of an entire system for implementing the present invention.

2 is a diagram illustrating an application installation configuration of a mobile device for implementing the present invention.

3 is a block diagram of the configuration of the mobile device application verification history management system according to an embodiment of the present invention.

4 illustrates an example of writing a script writing rule in a document type definition (DTD) of XML according to an embodiment of the present invention.

5 illustrates an example of a script created by a script writing rule according to an embodiment of the present invention.

6 illustrates a screen of an environment for creating a script according to an embodiment of the present invention.

7 is a flowchart illustrating a mobile device application verification history management method according to an embodiment of the present invention.

8 is a flowchart illustrating a mobile device application verification history management method according to another embodiment of the present invention.

Figure 9 illustrates the relationship between each business entity when the mobile device application verification history management in accordance with the conventional method and the method according to the present invention.

10 is a table illustrating a difference between the mobile device application verification history management according to the conventional method and the method according to the present invention.

Explanation of symbols on the main parts of the drawings

10: mobile device 11: wireless platform

12 application 13 agent module

15: network

20: verification terminal 21: test server

22: script management server 23: test result management server

30: application verification system 31: agent installation unit

32: script creation section 33: script interpretation section

34: execution code loading unit 35: execution result receiving unit

36: script management means 37: test result management means

Claims (10)

In the mobile device application verification history management system for connecting to a mobile device with a wireless platform installed, to test the application running on the wireless platform, Agent installation unit for loading and installing the agent module on the wireless platform of the mobile device; A script interpreter that converts a script for testing an application into test execution code that can be executed on the agent module; An execution code loading unit loading the test execution code on the mobile device and executing the test execution code on an agent module; And an execution result receiver configured to receive and store the result data of the test execution code execution, The script interpreter converts the test execution code to be executed by calling the test-only interface functions of the agent module, wherein the test-only interface functions are executed on a wireless platform of the mobile device. system. delete The method of claim 1, The system further comprises a script writing unit for receiving a script for testing the application of the mobile device application verification history management system. The method of claim 1, The agent installation unit obtains specification information of the mobile device or specification information of a wireless platform installed in the mobile device, and installs an agent module corresponding to the standard on the mobile device. . The method of claim 4, wherein the test-only interface function, According to the standard of the mobile device or the specification of the wireless platform installed in the mobile device can be implemented differently, the mobile device application verification history management system, characterized in that the interface to call or return a function. The method of claim 1, The system comprises: Script management means for storing and managing the script corresponding to the set of functions and test rules of the mobile device, and test result management means for storing and managing the test results for the mobile device by model and test case of the mobile device and, The script preparation unit obtains the function information of the mobile device, receives a test rule set for the function of the mobile device, and receives a script corresponding to the function of the mobile device and the test rule set from the script management means. , And the execution result receiving unit obtains model information of the mobile device and transmits the received execution result data and the model information of the mobile device to the test result management means. The method of claim 1, wherein the script is Mobile device application verification history management system characterized in that it is written using commands defined by DTD (Document Type Definition) according to the XML standard. In the mobile device application verification history management method of the verification system for testing the application running on the wireless platform by connecting to a mobile device installed wireless platform, (a) loading and installing the agent module on the wireless platform of the mobile device; (b) receiving a script for testing an application of the mobile device; (c) converting a script for testing an application into test executable code that can be executed on the agent module; (d) loading the test execution code into the mobile device to execute on the agent module; (e) receiving and storing the result data of executing the test execution code, In step (c), the test execution code is converted to be executed by calling the test-only interface functions of the agent module, wherein the test-only interface functions are executed on the mobile platform of the mobile device. History management method. delete The mobile device application verification history management method of testing a mobile device application implemented on a wireless platform by connecting to a network with a test server that stores and manages a program module and test script that records the mobile device application verification history management system of claim 1. In (f) accessing the test server and authenticating; (g) downloading the mobile device application verification history management system module from the test server; (h) connecting with a mobile device to obtain function information from the mobile device; (i) receiving a test rule set for the function of the mobile device; (j) downloading a script corresponding to the function and the rule set by transmitting the function of the mobile device and the test rule set to the test server; (k) if there is no script corresponding to the function and the rule set, directly receiving a script corresponding to the function and the rule set; (l) delivering the script to the mobile device application verification history management system module to execute a test for the mobile device application; (m) transmitting the executed test result data to the test server; and (n) accessing the test server and requesting a test result for the mobile device to send and display the test result data.

Images