KR20160070410A - System for testing an application use for a smart device and method therefor - Google Patents

Abstract

The present invention relates to a system for testing an application for a smart device and a method thereof. More specifically, the present invention relates to a system for testing an application for a smart device and a method thereof, wherein the system for testing an application for a smart device comprises: a document object model extraction unit for extracting document object model information of an application executed on a user terminal connected through communication networks, collecting event information of the corresponding application based on the extracted document object model information, and storing the event information in a database; a scenario generation unit for displaying scene images when executing an event in a tree structure based on the collected event information; a test executing unit for generating a scenario for testing the application by selecting the scene images when executing an event in a tree structure, and executing a test for the application according to the generated scenario; a test management unit for executing a rule-based engine in which a preset test scenario is automatically provided for a user so that the user can select; and a result creation unit for creating a test result executed by the test executing unit and displayed the test result on the user terminal. Thereby, the system for testing an application for a smart device allows a user to write a test scenario and execute a test.

Description

[0001] The present invention relates to a test system for a smart device, and more particularly,

The present invention relates to a test system and method for an application program for a smart device, and more particularly, to a test system and method for an application program for a smart device, which extracts document object model information of an application executed in a user terminal connected via a communication network, A scenario generation unit for displaying scene images at the time of event execution in a tree structure based on the collected event information; A test system for a smart device application configured by selecting scene images at the time of event execution and generating a scenario for testing the application and testing the application in accordance with the generated scenario; And more particularly to a method of testing an application for a smart device.

Generally, a smart device such as a smart phone, a tablet PC, a personal digital assistant (PDA), or the like is an application program having a specific purpose and function Program, hereinafter abbreviated as "application" in the specification of the present invention) can be installed and executed in the device.

[0003] However, when developing an application and testing its performance, conventionally, performance of several tens of terminals per terminal or OS (Operating System) has been tested and many scenarios that the application can run have been tested one by one There is a problem in that it takes much time and cost to test the application.

In addition, it is not easy to develop a tool that can automatically test an application because it is difficult to write a script for testing, and for each test scenario, This is due to the constraints that must be written.

Also, there is a problem in that an individual script for testing does not reflect all possible types of exception processing, and that additional scripts must be written for a desired repetitive test.

Also, due to the nature of the application, it is not always easy to carry out the test while modifying the script, because it is continuously updated after the release.

In addition, because all exceptions are not reflected, if there is an unexpected error in the application, the test is interrupted. In this case, the test needs to be performed while the script is modified again.

Furthermore, because scripts must be written individually for all scenarios, the quality of the test tends to depend on the capabilities of the script developer, and other users besides the test developer are not easy to modify the script.

On the other hand, as a prior art for testing an application as described above, a method of automating the Android application JiUi test of Korean Patent Laid-Open Publication No. 2014-2815 and a test case generation method of automatically analyzing the user interface of Korean Patent Application No. 2012-40419 are known have.

In the present invention, a scene image of all events of an application is displayed in a tree structure using information of a document object model of an application, and a user can create scenarios for testing by selecting and editing scene images of tree-structured events, The present invention provides an application test system and method for enabling a user to easily create a test scenario and perform a test without writing a script for every possible scenario.

According to an aspect of the present invention, there is provided a test system for an application for a smart device, which extracts document object model information of an application executed in a user terminal connected to the system of the present invention, A document object model extracting unit for collecting event information of the application based on the information and storing the event information in a database, a scenario generating unit for displaying scene images at the time of event execution in a tree structure based on the collected event information, A test execution unit configured to receive a user input of scene images at the time of execution of an event indicated by the tree structure to generate a scenario for testing the application and to test the application according to the generated scenario, Of the test performed by Generate and to is characterized in that comprises a generator for displaying the results in a user terminal.

Preferably, the document object model extracting unit extracts the document object model from the script image when the new scene is added to the application, or when the image of each scene displayed at the time of execution of the application is changed to a new image, Lt; / RTI >

Preferably, the test execution unit receives a selection of a user by selecting a scene image by a drag and drop method when selecting scene images at the time of execution of an event displayed in the tree structure.

In addition, preferably, the test execution unit allows all testable scenarios between the start scene and the end scene selected by the user to be inquired when the user selects only the start scene and the end scene of the event.

In addition, when the user selects a start scene, an intermediate scene, and an end scene of the event, the test execution unit causes the front and back scenes of the event scene corresponding to the start scene to be blinked, Make connections intuitive

      The test management unit may further include a test management unit that operates a rule-based engine that automatically provides a predetermined test scenario to the user so that the user can select the role-based engine. The role- An event information extractor for generating an event information; A test scenario generator for providing a predetermined test scenario selectable by the application based on event information collected through the event information extractor; And a scene situation information provider for finding an event scene of an application suitable for the scenario when generating the test scenario based on the information of the event and providing the event scene to the test scenario generator.

In another aspect of the present invention, there is provided a method of testing an application executed in a user terminal (100) connected to an application test server through a communication network (200) Extracting model information (S 300); Collecting event information of the application according to the extracted document object model information and storing the event information in a database (S 301); (S 302) displaying scene images at the time of event execution in a tree structure based on the collected event information; Selecting a scene image at the time of execution of the event indicated by the tree structure to generate a test scenario for testing the application (S 303); Performing a test of the application in accordance with the generated test scenario (S 304); (S 305) displaying a test execution result of the application on the user terminal 100; And a control unit.

The application test system and method of the present invention having the above-described configuration exhibit the following effects.

First, scenarios and scripts can be automatically generated in advance by using the document object model extractor and the database of the present invention. Therefore, it is possible to dramatically shorten the script creation time, and since the developer is not required for the script creation, It is possible to reduce the cost of inputting the data.

Second, the developer must modify the script at every update of the conventional application. However, since the document object model extractor periodically collects the change information automatically to change the scenario, it is possible to re-test without changing the script. Maintenance costs can also be minimized.

Third, since various patterns and attributes that can be generated when an application is executed are stored in the database, it is possible to perform stable testing for a long time.

Fourth, since the script is not written by the developer, and the application can be tested immediately after the scenario is written by the user, it is a very advanced invention that enables the self-test to be performed remotely .

1 is a block diagram of an inventive application test system,
2 is a flow chart of control of the document object model extracting unit of the application test system of the present invention,
3 is a diagram showing an example of an execution screen of a test scenario generator of the application test system of the present invention,
4 is a configuration diagram of a test management unit of the application test system according to the present invention,
5 is a flow chart of control of the roll-based engine of the test management unit of the present invention,
6 is a flowchart of an application test method of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification. And a detailed description thereof will be omitted to omit descriptions of portions that can be readily understood by those skilled in the art.

Throughout the specification and claims, where a section includes a constituent, it does not exclude other elements unless specifically stated otherwise, but may include other elements.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an application test system and method according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of an inventive application test system.

Referring to the drawings, an application test system 1 of the present invention includes a document object model of an application executed in a user terminal 100 connected to the system 1 of the present invention via a communication network 200, A document object model extraction unit 10 for extracting DOM information, collecting event information of the application based on the extracted document object model information, and storing the collected event information in a database 50, A scenario generation unit 20 for displaying scene images of a city in a tree structure and a user for inputting scene images at the time of execution of an event indicated by the tree structure to generate a scenario for testing an application A test execution unit 30 for performing an application test according to the generated scenario, And a result generation unit 60 for generating a result of the test result and displaying the result on the user terminal 100.

In addition, the test management unit 40 may further include a rule-based engine 41 for automatically providing a predetermined test scenario to the user so that the rule-based engine 41 can be selected by the user.

Here, the user terminal 100 may be a smart device such as a smart phone, a tablet PC, a personal digital assistant (PDA) )to be.

Hereinafter, the configuration of the application test system of the present invention as described above will be described in more detail in a refinement manner.

1) a document object model (Document Object Model)

Extracts document object model (DOM) information of the application, collects event information from the extracted document object model information, and stores it in the database 50.

The document object model refers to a model in which all elements of a program are standardized so that they can be controlled by a language such as a Java script. When a document object model of an application is analyzed, all events and events Inter-connection information and inter-event flow information.

In this specification, the event information of the application refers to event-related information and event-to-event flow information such as event attribute information, event sequence information, and overall scenario information according to the order of events.

At this time, the document object model extraction unit 10 of the system of the present invention analyzes the syntax of the program to collect event information from the document object model information, and uses a parsing technique to separate each element.

As described above, the operation of extracting the information of the document object model of the application and collecting the event information is referred to as the crawling of the document object model in the present invention.

 The document object model extraction unit 10 extracts elements and their attributes for processing an event performed by the user as event information of the application by crawling the document object model, Each scene image constituting a scene displayed by execution is separately captured and included in event information as scene information, or stored in association with event information.

Accordingly, the event information of the application collected through the document object model extraction unit 10 is stored in the database 50 together with the images of each scene displayed when the corresponding application is executed.

[Table 1] is an example of attributes parsed by the document object model extracting unit 10, and the DOM of the mobile application includes various elements for processing an event performed by the user and their attributes, The crawling of the document object model of the model extracting unit 10 allows the document object model to have an element for processing each event as shown in Table 1 below and a form having a tree structure as its attributes .

The document object model extraction unit 10 sequentially crawls all the scenes starting from the initial scene of the application to the last scene and extracting event information such as event attributes and event connection information for the scene, And stores it in the database 50.

In addition, according to a preferred embodiment of the present invention, the scenes generated by the scenario generator 20 stored in association with the scene-specific event information stored in the database are stored in association with each other, When a new scene is added to an application or when an image of each scene displayed at the time of execution of an application is changed to a new image, the script is also automatically generated and changed according to the change, . In this case, the rule-based engine 41, which is provided by the rule-based engine 41, automatically provides the user with a predetermined test scenario so that the user can select the scenario or the prepared scenario, Will be described in detail.

In addition, when an error occurs in execution of the application, that is, when an application error and an error due to the mobile operating environment of the user terminal occur, the document object model extracting unit 10 extracts the document object model from the corresponding event Based on the information, the document object model information extracted and classified by the generated error scenes is stored separately in the database 50 and is cumulatively managed afterwards, for example, in a rule-based engine 41, Or the like to automatically select a test scenario and use it as basic information when providing it, so as to cope with an unexpected error situation in advance.

The process of collecting the event information of the application by the document object model extraction unit 10 of the present invention as described above is shown in FIG.

First, a registration request of an application desired to be tested is received from the user terminal 100 connected to the inventive system 1 through the communication network 200 (S 100).

In accordance with the registration request, the test management unit 40 determines whether the requested application is an application previously stored in the database 50 (S 101). If the application is stored in the database 50, (S 102). If the application is not stored in the database 50 and is required to be registered, it is determined whether the corresponding application is installed in the user terminal 100 (S 103).

If it is determined that the application is not installed, the user terminal 100 is requested to install the application (S 104).

If the application is installed in the user terminal 100, terminal information of the user terminal 100 requesting the application test is obtained (S 105). The fetched terminal information includes memory capacity of the terminal, power information, CPU information, version information of the OS, and brand information of the terminal.

Then, the user terminal 100 requests the user terminal 100 to activate the corresponding application and drives the corresponding application in the user terminal 100 (S 106).

Then, the document object model extraction unit 10 performs crawling of the document object model by the parsing method from the document object model information to obtain all the event information of the application (S 107).

At this time, when acquiring event information of the application, the document object model extracting unit 10 sequentially extracts event information such as event attributes, event connection information, and the like for all scenes starting from the initial scene of the application to the last scene And stores the extracted and extracted event information in the database 50. At this time, the captured scenes are captured and simultaneously captured scene images are included in the event information as scene information of an associated event, or are stored in the database 50 in association with the event information.

When extracting the event information, each of the events that are possible or impossible is classified and stored in the database 50 (S 108). The images of the respective event scenes are combined into a tree structure and stored in the database 50 (S 109). If the event scene is terminated or the extraction of the document object model based event information is completed (S 110), the acquisition of the event information by the document object model extraction unit 10 is terminated. If not completed, the event information of the next event of the application is acquired (S 111).

2) The scenario generating unit 20,

The event information collected by the document object model extracting unit 10 and stored in the database 50 is edited by a user in a graphical user interface (GUI) for all events of the application program so that a test scenario can be configured. The event information is displayed on the user terminal 100 through a graphical user interface (GUI) in a tree structure in association with scene information, that is, a scene image.

The display structure of the above event maps each scene-specific event and event flow information of the application existing in the document object model to the scene to which the corresponding event belongs, A tree structure for visually displaying connection relationships and flow information, that is, a GUI tree structure.

The events of the application in the user terminal 100 are displayed in a tree structure so that a scenario for drag and drop test of the user in the test execution unit 30 to be described later can be easily performed .

The scenario created by the scenario generation unit 20 is stored in the database 50. [

The important situation information can be displayed in the graphical user interface (GUI) of such a tree structure. As the important situation information, it is possible to display the relation between the scenes of each event of the application, Importance information, information of a scene requiring data input from the user terminal 100, and the like.

3) The test execution unit 30

The scenario generating unit 20 receives a user input of scene images at the time of execution of the event indicated by the tree structure, generates a scenario for testing the application, and tests the application according to the generated scenario.

At this time, since the event is displayed in a graphical user interface (GUI) at the time of creating the scenario in a tree structure in which the scene image and the connection relationship between them are displayed, a drag and drop method It is possible to create a scenario.

For example, in the case of N-drive application of Naver (naver), a portal site in South Korea, various scenarios such as selecting and uploading a photo upload scenario from a local terminal, . ≪ / RTI >

Thereafter, the event script is sequentially executed according to the flow of the generated test scenario, and the application is automatically tested.

3 is a graphical user interface (GUI) as an execution screen of the test execution unit 30 displayed on the user terminal 100 to generate the test scenario of the present invention.

As shown in the figure, it is composed of a GUI navigation area 31 at the top of the screen, a ruleset list area 32, a scenario editing area 33, a scenario storage button area 34, And a command input area for exposing the selected scenario to an excel file or the like in order to grasp the amount of power consumption, the amount of power consumption, and the like.

In the GUI navigation area 31 at the top of the screen, a scene corresponding to each event of the application and an event flow of the scene are displayed as arrows, and the user's input on the scene is received. The input is performed in a drag-and-drop manner by moving the scene image of the event selected in the ruleset list area 32 at the bottom of the screen.

In the rule set list area 32 at the bottom of the screen, rules sets (Scene set 1, Scene set 2 ....) are constituted by grouping scenes of each event moved from the GUI navigation area 31 at the top of the screen by the drag and drop method, The completed ruleset is moved to the scenario editing area 33 in a drag-and-drop manner and is combined with these in the scenario editing area 33, and the options such as the number of repetitions are input, and a test scenario can be easily created and completed .

The test scenario created in the scenario editing area 33 can be saved by clicking the 'Save scenario' button 34 at the bottom of the screen.

Here, the GUI navigation area 31 provides event information related to the app collected by the DOM crawler to the user in the form of a GUI tree in connection with the scene information. Through the GUI tree form, (2) the importance of a particular scene, (3) the connectivity with scenes in other nodes (NODE), (4) scenes with input nodes, etc. So that the user can visually check the scenes connected to each other and can easily configure the scenarios for the intended test of the user in an easy and intuitive way. Control and design, new grouping of scenes, segmentation of scene flow around scenes, and combinations of scenes.

In addition, when the predetermined event scene is set as the start scene, the GUI navigation area 31 causes the front and back scenes of the event scene corresponding to the start scene to be displayed in a blinking manner in the upper area 31 of the screen, In addition, when a scene is divided into several scenes and merged into a scene, even if one of the scenes is to be selected, the corresponding scenes are blinked, or the rulesets are combined When configuring the entire scenario, it may be configured to indicate whether or not each rule set is connectable to each other and, if not possible, indicate the location of the rulesets to indicate that the connection is broken.

The ruleset list area 32 may further specify the user to suit the test by adding scenes of each event in the navigation area 31 and adding options such as time, repetition, etc. to the scene selected at the time of forming the ruleset.

The scenario configuration area 33 is a part that constitutes the entire scenario based on contents that have been worked on in the navigation area 31 and the ruleset list area 32. [ The above-described options are added to move the specified ruleset in a drag-and-drop manner, and the moved rulesets are connected to the rulesets. Then, the user clicks the option button such as the iteration, connection and backward of the scenario configuration area 34 The scenario is completed when a plurality of rulesets that have been moved are tied and repeatedly executed or a connection relationship in which the rulesets go back for connection of the rulesets are defined. The scenario composition area 33 may also be used to check the total estimated time required for this completed scenario.

The process of storing a rule set using the GUI navigation area 31 of the graphical user interface (GUI) of the test execution unit 30 of FIG. 3 will be described as an example from the user's point of view. 1) In the case of selecting a scene, an intermediate scene, and an ending scene, when a scene is set as a starting point, the scene before and after the scene corresponding to the starting point flickers in the navigation area 31. This display allows the user to visually check the connection with other scenes. If you select an end point as a scene that is far from the starting point, the path from the start point to the end point is displayed on the screen. If a scene is split into several scenes in the middle of the path, the scenes are blinked and displayed even if one of the scenes is to be selected. Through this process, the user can create a rule set by collecting the desired scene image and setting the path.

In the case where the user selects only the start scene and the end scene of the event, in order to design the test scenario desired by the user after the user confirms the entire scene structure in the navigation area 31, the user first selects a scene to start the test , And clicks the scene to be terminated to confirm the attributes and information of the scenes to grasp the flow between scenes. The starting and ending points of the scenario are set by clicking on the menu of the scene corresponding to the start scene and the ending scene of the ending scene. Thus, in the rule set list area 32, all testable The scenario is retrieved. At this time, information such as an expected test time for each scenario is also inquired and selected by the user and stored as a test scenario as it is, or all or a part of the test scenario is moved to the scenario editing area 33 in a drag and drop manner, It is possible to combine them in the scenario editing area 33 and to input optional items such as the number of repetitions and to simply create and complete a test scenario.

  In this case, when a test management unit 40 is operated in which a rule-based engine 41 that automatically provides a user with a preset test scenario so that the user can select a test scenario, to be.

4) The test management unit 40

The test management unit 40 includes a rule-based engine 41 that automatically provides a predetermined test scenario to a user so that the user can select a test scenario when the test scenario is created by the test execution unit 30, . The provision of test scenarios is fundamentally implemented using a mechanical learning approach.

Providing automatic test scenarios with these rule-based engines can provide test scenarios in various situations, from test scenarios in normal situations to test scenarios based on exceptional circumstances.

In addition, it is possible to provide only the appropriate test scenarios to the user, thereby saving time for the test.

4 is a configuration diagram of the test management unit 40 of the application test system of the present invention.

The rule-based engine 41 of the test management unit 40 includes an event information extractor 42 for generating event information and scene information of the application as described above, A test scenario generator 43 for providing a predetermined test scenario that can be selected by the application based on the scene information, an event scene of an application suitable for the scenario at the time of generating the test scenario based on the event information and the scene, And a scene situation information provider 44 for providing the scene situation information to the user.

More specifically, the event information extractor 42 drives the application to perform crawling of the document object model (DOM), and transmits event information and event scene information generated as a result of the execution to the scene situation information provider 44).

In this case, the elements of each scene and the attribute information thereof are transmitted as scene information of the event information and the event, and the resource information of the smart device as the user terminal can be transmitted together. The resource information of the smart device is stored in the memory of the smart device, Version, battery remaining amount and consumption amount, IP of WiFi, and signal strength are transmitted together with event information and event scene information. In addition, event information and scene information of an exception scene through error induction may be separately transmitted.

The scene information provider 44 receiving the event information and the scene information of the event from the event information extractor 42 receives the scene information of the event information and the event and the scene information model previously stored in the database 50 Generates blueprint information for connecting forward and backward streams of respective scenes of the event through flow inference process of the scene, and determines a test scenario applicable as an application test case based on the blueprint information .

When the test case of the application to be recommended to the user is determined, the test scenario generator 43 fetches the information of the test scenario related to the test from the rule-based engine 41 and displays the information on the user terminal 100 of the user.

The control process of the roll-based engine 41 of the test management unit 40 having the above-described configuration will be described in detail with reference to FIG.

end. The application information collection step (S 200)

The event information of the application is collected by crawling the document object information (DOM) of the application, and the collected event information is loaded into the rule-based engine 41.

Also, scene information and scene life cycle information according to a scene flow at the time of event information collection are loaded together with the role-based engine 41. [

I. The scene condition information preprocessing step (S 201)

Acquiring scene information according to a scene flow of an event acquired in the application information collection step, converting the scene state information into a usable form in the role-based engine, and storing the scene state information in the database 50.

All. The scene situation information inference step (S 202)

Based on the scene-state information set in the role-based engine 41 based on the scene situation information of the event that is converted in the event scene situation information preprocessing and stored in the database 50, Inferring the context information of the user.

Also, it may be performed to infer an unintended scene or an uncertain scene through inference of scene context information.

The context information of the next scene of the event generated based on the speculation of the role-based engine 41 forms basic information for generating a preset test scenario to be provided to the user.

Here, the scene-specific information model preset in the rule-based engine 41 is a reasoning model based on a logical program using a regular pattern such as IF A Then B (A, B is performed) The scene flow is inferred by repeatedly applying regularity through scene inference and after scene inference.

la. The blueprint extraction step (S 203)

Based on the context information of the next scene inferred in the scene situation information inference step, a test case that can be provided based on the context information is loaded into the role-based engine 41, and a blueprint for creating a test scenario is tested based on the blueprint information This is a step of determining and providing an applicable test scenario as a case.

Therefore, only the appropriate test scenarios provided by the role-based engine 41 are loaded, as compared with providing all the scenes for all the events, thereby saving resources and time required for the test.

hemp. Providing and executing the test scenario (S 204)

And selecting the test scenario provided in the blueprint extraction step to test the application.

bar. Handling errors in applications

An application can cause unexpected errors (error conditions) at runtime.

Such an application error may cause an unexpected application error such as a communication failure, an unspecified push (PUSH) service from the server, a stoppage of a scene, or an unexpected application error during the moving from one scene of the event to the next, Errors may occur.

Since it is impossible to completely grasp the errors of these applications, the error scenes generated in such events are classified and stored in the database 50 and cumulatively managed by the rule-based engine 41 to cope with an unexpected error situation in advance I will.

The result generation unit 60 generates a result of the test performed by the test execution unit 30 and displays the result of the test on the user terminal 100. The result report unit 60 transmits the result report to the user terminal 100 via e-mail or SMS Short message service).

Next, a test method for an application for a smart device using the system of the present invention configured as described above will be described.

6 is a flowchart of an application test method of the present invention.

Referring to the drawings, an application testing method of the present invention is a testing method performed by an application testing server that performs testing of an application executed in a user terminal 100 connected via a communication network 200.

The test method of the present invention may include: extracting Document Object Model (DOM) information of an application executed by the application test server in the user terminal 100 (S 300); Collecting event information of the application according to the extracted document object model information and storing the event information in a database (S 301); (S 302) displaying scene images at the time of event execution in a tree structure based on the collected event information; A step (S303) of receiving a user input of a user for scene images at the time of execution of the event indicated by the tree structure and generating a test scenario for testing the application; Performing a test of the application in accordance with the generated test scenario (S 304); Displaying (S 305) a test execution result of the application on the user terminal (100); And a control unit.

In the process of collecting the event information of the application by the document object model extracting unit 10, the step of extracting the document object model information (S 300) (S100) receiving a registration request of an application desired to be tested from the user terminal (100); If the application requested by the test server according to the registration request is an application pre-stored in the database (S 101), if the application is stored in the database, the execution of the document object model extraction is interrupted (S 102) (S 103) whether the application is installed in the user terminal (100) if the application is not installed; If the application is installed in the user terminal 100, fetching terminal information of the user terminal 100 (S 105); A step (S 106) in which the corresponding application is executed in the user terminal (100); Performing a crawling of the document object model by the test server to obtain event information of the application (S 107); The test server classifies the events that are possible and impossible into the database (S 108), combines the images of the respective event scenes into a tree structure and stores them in the database (S 109) Determining whether the extraction of the event information based on the document object model is completed (S110), and terminating the acquisition of the event information when the event information is completed; .

As described above, the test server includes a test management unit 40 defined as a component of the test system. The test server 30 includes a test server 30, A rule-based engine 41, which automatically provides scenarios to the user, may be configured to operate, in which case the test server operates a rule-based engine 41 Based on the scene-state information of the event stored in the database 50, the inference based on the scene-based information model is performed by the role-based engine 41 to deduce the scene information of the next scene, Tree structure. Here, the error scenes generated when the application is executed are classified and stored in the database 50 and cumulatively managed by the rule-based engine 41. The model for each scene situation information is based on a logical program using a regular pattern And it is a model that infer scene flow by repeatedly applying regularity through previous scene inference and after scene inference. The inference of the scene is implemented by a mechanical learning method of the data accumulated in the database 50.

Based on the role-based engine 41, an application information collection step (S 200) of collecting event information of the application by crawling document object information (DOM) of the application and loading the collected event information into the rule-based engine 41, ; A scene situation information preprocessing step (S 201) of acquiring scene situation information according to a scene flow of an event acquired in the application information collection step, converting the acquired scene situation information into a usable form in a role based engine, and storing the scene state information in a database (50); Based on the scene-state information set in the role-based engine 41 based on the scene situation information of the event that is converted in the event scene situation information preprocessing and stored in the database 50, A scene situation information inferring step (S 202) of inferring the situation information of the scene information; Based on the context information of the next scene inferred in the scene context information inference step, a test case that can be provided based on the context information of the next scene is loaded into the role-based engine 41 to generate a blueprint for creation of a test scenario, A blueprint extraction step (S 203) for determining and providing a test scenario applicable as an application test case; Providing and executing a test scenario (S 204) for receiving a selection of a test scenario provided in the blueprint extraction step and testing the application; To provide a test scenario for testing an application by providing a blueprint for creating a test scenario as an example of a test scenario and selecting a test scenario suitable for the user.

Meanwhile, the method of testing an application of the present invention as described above can be performed in the form of a recording medium such as a compact disc containing the program.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it should be understood that various changes, substitutions, and alterations can be made hereto without departing from the spirit and scope of the invention. And should be construed as falling within the scope of protection of the present invention.

Description of the Related Art [0002]
One; The present invention system 10; The document object model extraction unit
20; A scenario generation unit 30; The test execution unit
40; A test management unit 50; Database
60; A result generating unit 100; User terminal

Claims (15)

1. A system for testing an application executed in a user terminal (100)
A document object model extracting unit 10 for extracting document object model information of an application executed in the user terminal 100, collecting event information of the application based on the extracted document object model information, and storing the collected information in the database 50;
A scenario generation unit (20) for displaying scene images at the time of event execution in a tree structure based on the collected event information;
A test execution unit (30) for receiving a user input of scene images at the time of execution of an event indicated by the tree structure to generate a scenario for testing an application and performing an application test according to the generated scenario; And
A result generating unit 60 for generating a result of the test performed by the test performing unit 30 and displaying the result of the test on the user terminal 100; And a control unit configured to control the operation of the application.
The method according to claim 1,
The document object model extraction unit 10 extracts,
And the event information of the collected application is stored in the database (50) together with the images of each scene displayed when the corresponding application is executed.
The document object model extracting unit (10) according to claim 1,
A script is automatically generated and changed according to the change when a new scene is added to an application or an image of each scene displayed when the application is executed is changed to a new image. Test system.
2. The apparatus of claim 1, wherein the test execution unit (30)
Wherein a scene image is selected by a drag and drop method when selecting scene images at the time of execution of an event indicated by the tree structure.
2. The apparatus of claim 1, wherein the test execution unit (30)
If the user selects only the start and end scenes of the event,
Wherein all testable scenarios between the start and end scenes selected by the user are displayed.
2. The apparatus of claim 1, wherein the test execution unit (30)
When the user selects a start scene, an intermediate scene, and an end scene of the event, the front and back scenes of the event scene corresponding to the start scene are displayed in a blinking manner so that the connection between the start scene and another scene can be intuitively confirmed The test system comprising:
The method according to claim 1,
Based test engine 40 that operates a rule-based engine 41 that automatically provides a predetermined test scenario to the user so that the user can select the test scenario, The engine 41,
An event information extractor 42 for generating event information of an application;
A test scenario generator 43 for providing a preset test scenario selectable by the application based on the event information collected through the event information extractor 42;
A scene situation information provider (44) for finding an event scene of an application suitable for a scenario when generating a test scenario based on the information of the event and providing the event scene to the test scenario generator (43); And a control unit configured to control the operation of the application.
8. The method of claim 7,
And the result generating unit (60) transmits the result report to the user terminal (100) by e-mail or SMS.
In a method of testing an application executed in a user terminal (100) connected to an application test server through a communication network (200)
Extracting document object model information of an application executed by the application test server in the user terminal 100 (S 300);
Collecting event information of the application according to the extracted document object model information and storing the event information in a database (S 301);
(S 302) displaying scene images at the time of event execution in a tree structure based on the collected event information;
Selecting a scene image at the time of execution of the event indicated by the tree structure to generate a test scenario for testing the application (S 303);
Performing a test of the application in accordance with the generated test scenario (S 304);
(S 305) displaying a test execution result of the application on the user terminal 100; The method comprising the steps of:
The method of claim 9, wherein extracting the document object model information (S 300)
Receiving (S100) a registration request of an application desired to be tested from the user terminal (100) through the communication network (200);
If the application requested by the test server according to the registration request is an application pre-stored in the database (S 101), if the application is stored in the database, the execution of the document object model extraction is interrupted (S 102) (S 103) whether the application is installed in the user terminal (100) if the application is not installed;
If the application is installed in the user terminal 100, fetching terminal information of the user terminal 100 (S 105);
A step (S 106) in which the corresponding application is executed in the user terminal (100);
Performing a crawling of the document object model by the test server to obtain event information of the application (S 107);
The test server classifies the events that are possible and impossible into the database (S 108), combines the images of the respective event scenes into a tree structure and stores them in the database (S 109) Determining whether the extraction of the event information based on the document object model is completed (S110), and terminating the acquisition of the event information when the event information is completed; The method comprising the steps < RTI ID = 0.0 > of: < / RTI >
10. The method of claim 9,
Based on scene context information of an event stored in the database 50, a reasoning based on a predetermined scene context information model is performed by the role based engine 41 to deduce scene information of the next scene, And displaying the data in a tree structure.
10. The method of claim 9,
And the error scenes generated when the application is executed are classified and stored in the database (50), and cumulatively managed by the rule-based engine (41).
12. The system of claim 11, wherein the roll-based engine (41)
An application information collection step (S 200) of collecting event information of the application by crawling document object information (DOM) of the application and loading the collected event information into the rule-based engine (41);
A scene situation information preprocessing step (S 201) of acquiring scene situation information according to a scene flow of an event acquired in the application information collection step, converting the acquired scene situation information into a usable form in a role based engine, and storing the scene state information in a database (50);
Based on the scene-state information set in the role-based engine 41 based on the scene situation information of the event that is converted in the event scene situation information preprocessing and stored in the database 50, A scene situation information inferring step (S 202) of inferring the situation information of the scene information;
Based on the context information of the next scene inferred in the scene context information inference step, a test case that can be provided based on the context information of the next scene is loaded into the role-based engine 41 to generate a blueprint for creating a test scenario, A blueprint extraction step (S 203) for determining and providing a test scenario applicable as an application test case; And providing and executing a test scenario (S 204) of receiving a selection of a test scenario provided in the blueprint extraction step and testing the application using the selected test scenario. Of the test method.
14. The system according to claim 13, wherein the scene-specific information model preset in the rule-based engine (41)
A method for testing an application, the method comprising the steps of: applying a regularity to a scene based on a logical program using a regular pattern;
A recording medium containing a program of a method of testing an application according to any one of claims 9 to 14.

Images