KR102303182B1 - Automated Test Network System and Automated Test Method - Google Patents

Abstract

A test automation network system and test automation method are provided. The test automation network system is an application server that receives scenario information and generates a finite state machine (FSM) scenario based on the scenario information, wherein the finite state machine scenario includes at least one state; An application server including a transition between the states, a job embedded in the state and set as an execution condition of the transition, a machine worker receiving and executing the finite state machine scenario, the scenario information and corresponding to the job A database for storing job information, providing the scenario information to the application server, and providing the job information to the machine worker, a job worker requesting execution of the job from the machine worker, and processing the job, and the job It receives and responds to a request for a job corresponding to the job from a worker, and includes an external network and an isolated internal network.

Description

Automated Test Network System and Automated Test Method

The present invention relates to a test automation network system and a test automation method. Specifically, it relates to a network system and method for automatically performing a test using a finite state machine (FSM).

The development of software that provides HTTP (HyperText Transfer Protocol) communication input/output has been accomplished through developer's step-by-step work and testing. In other words, software was developed in the form of modularizing the software to be developed step by step, testing each module and combining them.

In this development method, problems that are not discovered in testing of individual modules may occur depending on the combination of modules, so final testing and debugging of the finished software is essential, and accordingly, modifications of individual modules may occur frequently. Accordingly, there is an irrationality in that the cost and development period of software development increase, and unnecessary human resources are consumed. Accordingly, there is a need for a system in which a developer can easily produce software and automatically test and debug the software.

An object of the present invention is to provide a test automation network system that can easily test HTTP-based software.

Another problem to be solved by the present invention is to provide a test automation method that can easily test HTTP-based software.

The problems to be solved by the present invention are not limited to the above-mentioned problems, and other problems not mentioned will be clearly understood by those skilled in the art from the following description.

A test automation network system according to some embodiments of the present invention for solving the above problems is an application server that receives scenario information and generates a finite state machine (FSM) scenario based on the scenario information, wherein the A finite state machine scenario is an application server including at least one state, a transition between the states, and a job embedded in the state and set as a condition for performing the transition. a database for storing the executing machine worker, the scenario information and job information corresponding to the job, providing the scenario information to the application server, and providing the job information to the machine worker; It receives a request for execution, a job worker that processes the job, and receives and responds to a job corresponding to the job from the job worker, and includes an external network and an isolated internal network.

In addition, the job includes a first job requesting an API (Application Program Interface) and a second job including a web page uniform resource locator (URL), wherein the job worker includes a first job worker for processing the first job and the and a second job worker for processing the second job.

In addition, the internal network includes an internal API server and an internal web page, the first job worker requests the API to the internal API server in response to the first job, and the second job worker is the second job worker The web page URL is requested from the internal web page in response to the job.

In addition, the external network includes an external API server and an external web page, the first job worker requests the API to the external API server in response to the first job, and the second job worker requests the API from the second job worker. The web page URL is requested from the external web page in response to the job.

In addition, it further includes a proxy server for connecting the job worker and the external network.

In addition, the external network further includes a web server that connects the application server and the user.

The method further includes a log server that receives and stores a log from the machine worker and transmits the log to the user.

The apparatus further includes a deployment system including an execution schedule therein, and instructing the application server to generate the finite state machine scenario according to the execution schedule.

The method further includes a distribution system for causing the application server to generate the finite state machine scenario, and for receiving a scenario result from the application server and distributing a service corresponding to the finite state machine scenario.

In addition, the scenario information is edited into a diagram.

A test automation method according to some embodiments of the present invention for solving the above other problem corresponds to a finite state machine scenario in which a database includes a state, a transition between the states, and a job embedded in the state and set as an execution condition of the transition receiving and storing scenario information, and a machine worker executing a finite state machine scenario according to the scenario information, wherein the state includes a first state and a second state, and the job is embedded in the first state and executing the finite state machine scenario includes executing to the first state, executing the first job, and transitioning to the second state according to a result of the first job; , executing the first job includes: a job worker sending a request corresponding to the first job to an internal network isolated from an external network, and the internal network responding to the request corresponding to the first job .

In addition, receiving the scenario information includes editing the scenario information into a diagram, and editing the scenario information into a diagram includes storing arrangement information of at least one state diagram corresponding to the state, and Arrangement information of at least one transition diagram corresponding to the transition is stored between state diagrams, and setting information of job information corresponding to the job is stored in the state diagram, and any one of the transitions according to the result value of the job is stored. and storing specific information as to whether one is executed.

In addition, the database stores the job information and provides it according to a request.

Also, the first job is a job that requests an API, the internal network includes an internal API server, and the job worker includes a first job worker that requests the API from the internal API server.

The first job is a job that requests a webpage URL, the internal network includes an internal webpage, and the job worker includes a second job worker that requests the webpage URL from the internal webpage.

The test automation network system and test automation method according to some embodiments of the present invention can edit a finite state machine scenario through a diagram and test the entire scenario at once, greatly reducing the cost and development period required for testing in the software development process. can be reduced

Furthermore, the test automation network system and test automation method according to some embodiments of the present invention may facilitate debugging according to the test.

The specific effects of the present invention in addition to the above will be described together while describing specific details for carrying out the invention below.

1 is a block diagram illustrating a test automation network system according to some embodiments of the present invention.
FIG. 2 is a conceptual diagram for explaining in detail the structure of the test automation system of FIG. 1 .
FIG. 3 is a conceptual diagram for explaining in detail the structure of the network system of FIG. 1 .
4 and 5 are sequence diagrams for explaining a test automation method according to some embodiments of the present invention.
6 is a block diagram illustrating a test automation network system according to an embodiment of the present invention.
7 is a block diagram illustrating a test automation network system according to other embodiments of the present invention.
8 is a block diagram illustrating a test automation network system according to another embodiment of the present invention.
9 to 13 are diagrams for explaining editing of scenario information in a test automation method according to some embodiments of the present invention.
14 to 19 are diagrams for explaining debugging of scenario information of a test automation method according to some embodiments of the present invention.

The terms or words used in this specification and claims should not be construed as being limited to a general or dictionary meaning. In accordance with the principle that the inventor can define a term or concept of a word in order to best describe his invention, it should be interpreted as meaning and concept consistent with the technical idea of the present invention. In addition, the embodiments described in the present specification and the configurations shown in the drawings are only one embodiment in which the present invention is realized, and do not represent all the technical spirit of the present invention, so they can be substituted at the time of the present application. It should be understood that there may be various equivalents and modifications and applicable examples.

Terms such as first, second, A, B, etc. used in this specification and claims may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. The term 'and/or' includes a combination of a plurality of related listed items or any of a plurality of related listed items.

When a component is referred to as being “connected” or “connected” to another component, it is understood that the other component may be directly connected or connected to the other component, but other components may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that no other element is present in the middle.

The terms used in this specification and claims are used only to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. It should be understood that terms such as “comprise” or “have” in the present application do not preclude the possibility of addition or existence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification in advance. .

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.

Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

In addition, each configuration, process, process, or method included in each embodiment of the present invention may be shared within a range that does not technically contradict each other.

Hereinafter, a test automation system and method according to some embodiments of the present invention will be described with reference to FIGS. 1 to 5 .

1 is a block diagram for explaining a test automation network system according to some embodiments of the present invention, and FIG. 2 is a conceptual diagram for explaining the structure of the test automation system of FIG. 1 in detail. FIG. 3 is a conceptual diagram for explaining in detail the structure of the network system of FIG. 1 . 4 and 5 are exemplary sequence diagrams for explaining a test automation method according to some embodiments of the present invention. Fig. 5 is a lower sequence diagram connected to the sequence diagram of Fig. 4;

Referring to FIG. 1 , a test automation network system according to some embodiments of the present invention includes a test automation system 100 , an internal network 200 , an external network 300 , and a proxy server 400 .

The test automation system 100 may receive scenario information from the external network 300 . The scenario information may be information about a scenario based on a finite state machine (FSM). The scenario information may be scenario information about execution of software providing HTTP (HyperText Transfer Protocol) communication input/output.

The test automation system 100 may automatically perform a software test according to the scenario information. The test automation system 100 may perform a test by sending a request to the internal network 200 and receiving a response. In addition, the test automation system 100 may send a request to the external network 300 and perform a test by receiving a response. The test automation system 100 may be accessed through the proxy server 400 when accessing the external network 300 . However, the present embodiment is not limited thereto.

The internal network 200 may be a network isolated from the external network 300 . The internal network 200 may be connected to the test automation system 100 . The internal network 200 may receive a request from the test automation system 100 and provide a response to the request to the test automation system 100 .

The external network 300 may be a network including a general Internet network. The external network 300 may not be connected to the internal network 200 . The external network 300 may in principle be separated from the test automation system 100 as well. However, the present embodiment is not limited thereto.

The external network 300 may be connected to the test automation system 100 through the proxy server 400 . Alternatively, the external network 300 may be connected to the test automation system 100 in a limited manner.

The external network 300 may deliver the edited scenario information to the test automation system 100 . The test automation system 100 may store scenario information received from the external network 300 . Also, the test automation system 100 may generate and execute a finite state machine scenario corresponding to the scenario information. The test automation system 100 may send a request to the external network 300 and receive a response thereto according to the execution of the finite state machine scenario. In this case, the test automation system 100 may connect to the external network 300 through the proxy server 400 . However, the present embodiment is not limited thereto.

The proxy server 400 may be a server that indirectly connects between the test automation system 100 and the external network 300 . Through this, the test automation network system according to the present embodiments may promote network separation between the external network 300 and the test automation system 100 . However, the present embodiment is not limited thereto. That is, when network separation is not required, the proxy server 400 may be omitted and the test automation system 100 and the external network 300 may be directly connected to each other.

1 and 2 , the test automation system 100 includes an application server 110 , a machine worker 120 , a first job worker 130 , a second job worker 140 , a database 160 and a log. It may include a server 150 .

The application server 110 may receive scenario information from the external network 300 . The application server 110 may store the scenario information in the database 160 . The application server 110 may retrieve the scenario information from the database 160 again. The application server 110 may generate a finite state machine scenario corresponding to the scenario information. The application server 110 may transmit the finite state machine scenario to the machine worker 120 .

The finite state machine scenario may include a state, a transition, and a job. The state may mean a finite state, and the transition may mean movement between states. The job may be performed in the state to be a condition for performing the transition. This will be described in more detail later.

The machine worker 120 may receive the finite state machine scenario from the application server 110 . The machine worker 120 may execute the finite state machine scenario. The machine worker 120 may receive job information about the job from the database 160 . The machine worker 120 may request the first job worker 130 and the second job worker 140 to execute a job included in the finite state machine scenario. The machine worker 120 may transmit a log of the execution of the finite state machine scenario to the log server 150 .

The job may include a first job and a second job. The first job may be a job that requests an HTTP API (Application Program Interface). The second job may be a job that requests a web page Uniform Resource Locator (URL). The first job and the second job are only some examples of the job, and the job may include various jobs in addition to the first job and the second job.

The first job worker 130 may execute the first job. That is, the first job worker may request the API to the internal network 200 or the external network 300 . The first job worker 130 may receive a response to the requested API and transmit it to the machine worker. When the first job worker 130 transmits a request to the internal network 200 and receives a response, it may directly connect to the internal network 200 . However, when the first job worker 130 transmits a request to the external network 300 and receives a response, the first job worker 130 may indirectly connect to the external network 300 through the proxy server 400 . However, the present embodiment is not limited thereto. The first job worker 130 may be, for example, an HTTP API.

The second job worker 140 may execute the second job. That is, the second job worker may request the webpage URL from the internal network 200 or the external network 300 . The second job worker 140 may receive a response to the requested web page URL and transmit it to the machine worker. That is, the second job worker 140 may access the web page, perform a predefined user action (click, text input, form transmission, etc.), and return the result to the machine worker. When the second job worker 140 transmits a request to the internal network 200 and receives a response, it may directly connect to the internal network 200 . However, when the second job worker 140 transmits a request to the external network 300 and receives a response, the second job worker 140 may indirectly connect to the external network 300 through the proxy server 400 . However, the present embodiment is not limited thereto. The second job worker 140 may be, for example, a web client.

The log server 150 may store a log according to the execution of the finite state machine scenario performed by the machine worker 120 . The log server 150 may provide the log to the user. That is, the log server 150 may provide the log through the external network 300 . In this case, the log may be provided to the external network 300 through the machine worker 120 and the application server 110 , or may be provided to the external network 300 through the application server 110 . Alternatively, the log server 150 may be directly provided to the external network 300 .

The database 160 may receive scenario information from the application server 110 . The database 160 may store the received scenario information. The database 160 may provide the stored scenario information when the application server 110 requests it.

The database 160 may store the job information. The database 160 may provide the job information when the machine worker 120 requests it. The database 160 may store the job information in advance.

Referring to FIG. 3 , the internal network 200 may include an internal API server 210 and an internal web page 220 .

The internal API server 210 may receive an API request from the first job worker 130 . The internal API server 210 may respond to the API requested by the first job worker 130 . The internal web page 220 may receive a web page URL request from the second job worker 140 . The internal web page 220 may respond to the web page URL requested by the second job worker 140 .

The external network 300 may include an external web page 310 , an external API server 320 , a web server 330 , and a user device 340 .

The external API server 320 may receive an API request from the first job worker 130 . The external API server 320 may respond to the API requested by the first job worker 130 . The external web page 310 may receive a web page URL request from the second job worker 140 . The external web page 310 may respond to the web page URL requested by the second job worker 140 .

The first job worker 130 and the second job worker 140 may directly connect to the internal API server 210 and the internal web page 220, respectively, to perform the job. On the other hand, the first job worker 130 and the second job worker 140 are connected to the external API server 320 and the external web page 310 through the proxy server 400, respectively, when connecting to the external network 300 . You can connect and perform the above job.

The user device 340 may edit the scenario information. The user device 340 may be driven by a user to edit scenario information. Scenario information edited by the user device 340 may be transmitted to the test automation system 100 through the web server 330 . Specifically, the scenario information may be transmitted to the application server 110 through the web server 330 . The user device 340 is, for example, any one of various communication terminals such as a computer, a notebook computer, a netbook, a PDA, an MP4 player, or various smart devices such as a smart phone, a smart note, a tablet PC, a smart camera, and a smart TV. can However, the present embodiment is not limited thereto.

The web server 330 may receive the scenario information edited by the user device 340 and transmit it to the application server 110 of the test automation system 100 . The scenario information may be stored in the database 160 via the application server 110 .

Hereinafter, a test automation method according to some embodiments of the present invention will be described with reference to FIGS. 1 to 5 .

3 to 5 , the user device 340 requests the application server 110 to execute a scenario <1>. Accordingly, the application server 110 may select any one of various scenario information stored in the database 160 <2>. In this case, the scenario information stored in the database 160 may be scenario information previously edited and stored by the user device 340 . However, the present embodiment is not limited thereto. The selected scenario information may be loaded into the application server 110 .

Then, the application server 110 instructs the database 160 to execute the selected scenario information <3>. In this regard, the database 160 may provide a Run ID and reply to the application server 110 <4>.

Then, the application server 110 generates a finite state machine scenario corresponding to the scenario information <5>. In this case, the generated finite state machine scenario may include at least one state, a transition between the states, and a job embedded in the state.

The application server 110 may push the log of the execution start to the user device 340 <6>. At this time, the log of the start of execution may be generated by the application server 110 and directly pushed to the user device 340 , or stored in the log server 150 and then transferred to the user device 340 by the log server 150 . may be transmitted. Pushing the log of the execution start by the log server 150 may include pushing directly to the user device 340 through the web server 330 or pushing through a machine worker and/or an application server.

The application server 110 requests the machine worker 120 to execute a finite state machine scenario <7>. This request may be performed simultaneously with the log push <6>. In this case, the "simultaneous" may include similar time points in time and order. That is, operations <6> and <7> may be performed between operations <5> and <8>. However, the present embodiment is not limited thereto.

Then, the machine worker 120 executes the finite state machine scenario as the initial state <8>. In this case, the initial state may be preset to be executed when the finite state machine scenario is first started. Subsequently, a transition may be performed by performing a job embedded in the initial state. Accordingly, the log for the transition may be pushed to the user device 340 <9>.

According to the transition, the machine worker 120 may enter a new state of the finite state machine scenario <10>. Accordingly, a log for state entry may be pushed to the user device 340 <11>.

The machine worker 120 may request job information embedded in the state from the database 160 <12>. The database 160 may return job information in response to the request of the machine worker 120 <13>. Accordingly, a log indicating that job execution has started may be pushed to the user device 340 <14>. Simultaneously with the job <14>, the machine worker 120 may request the first job worker 130 to perform the job <15>. In this case, task <15> exemplifies the case in which the job embedded in the current state is the first job requesting the API, and the present embodiment is not limited thereto. That is, when the job embedded in the current state is not the first job that requests the API, the machine worker 120 may perform the job in a different way.

The first job worker 130 may request an HTTP API from the internal API server 210 <16>. In contrast, the internal API server 210 may return the HTTP API to the first job worker 130<17>. The first job worker 130 may transmit the received result to the machine worker 120 . The machine worker 120 may terminate the job through this. Accordingly, a log of job termination may be pushed to the user device 340 <19>. Then, the machine worker 120 may test the result of the job<20>. The machine worker 120 may determine which operation to perform according to the result of the job. In this case, the term “operation” may include transition and scenario termination. Accordingly, the log of the operation according to the job result may be pushed to the user device 340 <21>.

Then, the machine worker 120 may make a transition to the above operation <22>. Of course, this is only an example, and it is possible to end a scenario with the above operation. Accordingly, the log for the transition may be pushed to the user device 340 <23>.

According to the transition, the machine worker 120 may enter a new state of the finite state machine scenario <24>. Accordingly, a log for state entry may be pushed to the user device 340 <25>.

The machine worker 120 may request job information embedded in the state from the database 160 <26>. The database 160 may return job information in response to the request of the machine worker 120 <27>. Accordingly, a log indicating that job execution has started may be pushed to the user device 340 <28>. Simultaneously with the job <28>, the machine worker 120 may request the second job worker 140 to perform the job<29>. In this case, the job <29> exemplifies the case in which the job embedded in the current state is a second job requesting a web page URL, and the present embodiment is not limited thereto. That is, when the job embedded in the current state is not the second job requesting the web page URL, the machine worker 120 may perform the job in a different way.

The second job worker 140 may execute a headless browser <30>. The second job worker 140 accesses the web page URL through the headless browser, performs user actions (click, text input, form transfer, etc.) by a predefined script, and returns the result to the machine worker. have. A headless browser may be a browser without a graphical user interface. However, the present embodiment is not limited thereto. That is, the second job worker 140 may execute a general browser instead of the headless browser.

The second job worker 140 may load a URL into the internal web page 220 and execute a script <31>. In contrast, the internal web page 220 may return a response to the second job worker 140 <32>. In this case, the second job worker 140 may access a web page, perform a predefined user action (click, text input, form transmission, etc.) and return the result. The second job worker 140 may transmit the result to the machine worker 120 . The machine worker 120 may terminate the job through this. Accordingly, a log of job termination may be pushed to the user device 340 <34>. Accordingly, the finite state machine scenario may end.

Accordingly, the machine worker 120 may transmit the finished result to the application server 110 <35>. Accordingly, a log of the end of the finite state machine scenario may be pushed to the user device 340 <36>.

The test automation method and test automation network system according to the present embodiment can automatically test the overall performance of software at once, unlike the existing step-by-step software test. Accordingly, it is possible to significantly reduce the time required for software development and to easily perform debugging.

Furthermore, even if there is no problem in the existing step-by-step test, a situation in which a problem may occur in the overall test can be prevented in advance, thereby minimizing the cost and time invested in software development.

Hereinafter, a test automation network system according to some embodiments of the present invention will be described with reference to FIG. 6 .

6 is a block diagram illustrating a test automation network system according to an embodiment of the present invention.

Referring to FIG. 6 , the test automation system 100 of the test automation network system according to an embodiment of the present invention may further include a batch system 170 .

Batch system 170 may store schedules therein. The deployment system 170 may instruct the application server 110 to generate a finite state machine scenario according to a schedule stored therein. In this case, the finite state machine scenario may be stored with an ID identified in the database 160 . Accordingly, the deployment system 170 may store a schedule for executing the finite state machine scenario having a specific ID, and instruct the application server 110 to execute the finite state machine scenario according to the schedule.

For example, in the case of a finite state machine scenario that needs to be performed regularly, such as purchase and settlement of cards, the test may be performed according to a regular schedule, such as daily or once a week.

Accordingly, in the present embodiment, the software can be automatically tested even if the user who wants the test does not individually instruct the test according to the time point, so that the ease of testing can be greatly improved.

Hereinafter, a test automation network system according to some embodiments of the present invention will be described with reference to FIG. 7 .

7 is a block diagram illustrating a test automation network system according to other embodiments of the present invention.

Referring to FIG. 7 , the test automation network system according to other embodiments of the present invention may further include a distribution system 500 .

The distribution system 500 may be a system for distributing developed software to the actual external network 300 . The distribution system 500 may complete testing of the software through the test automation system 100 before distribution of the software and distribute the software.

Specifically, the distribution system 500 may be connected to the application server 110 of the test automation system 100 . The distribution system 500 may store in advance what the ID of the finite state machine scenario corresponding to the software to be distributed is. The distribution system 500 may transmit the ID of the finite state machine scenario corresponding to the software to be distributed to the application server 110 of the test automation system 100 and instruct the execution of the finite state machine scenario.

The application server 110 may generate a finite state machine scenario of the ID of the finite state machine scenario received from the distribution system 500 and cause the machine worker 120 to execute the finite state machine scenario.

The application server 110 may derive a result value of the executed finite state machine scenario and transmit it to the distribution system 500 . The distribution system 500 may check whether the software to be distributed operates normally through the result value of the finite state machine scenario. The distribution system 500 may perform distribution if it is determined that the software to be distributed operates normally, and may not perform distribution if it is determined that the software to be distributed operates abnormally.

According to the present embodiment, it is possible to automatically check whether the software before distribution is operating normally. Accordingly, it is possible to prevent problems of software after distribution and to ensure stable operation of the software.

Hereinafter, a test automation network system according to some embodiments of the present invention will be described with reference to FIG. 8 .

8 is a block diagram illustrating a test automation network system according to another embodiment of the present invention.

Referring to FIG. 8 , a test automation network system according to another embodiment of the present invention may further include a deployment system 170 and a distribution system 500 .

The deployment system 170 may instruct the application server 110 to generate a finite state machine scenario according to a schedule stored therein. In addition, the distribution system 500 may transmit the ID of the finite state machine scenario corresponding to the software to be distributed to the application server 110 of the test automation system 100 and instruct execution of the finite state machine scenario.

Accordingly, the application server 110 may automatically perform the test of the finite state machine scenario according to the timing indicated by the distribution system 500 and the deployment system 170 . Accordingly, the present embodiment can perform the test by automatically determining an appropriate execution time of the test.

Hereinafter, scenario information editing of a test automation method according to some embodiments of the present invention will be described with reference to FIGS. 3 to 5 and 9 to 19 .

9 to 13 are diagrams for explaining editing of scenario information of a test automation method according to some embodiments of the present invention, and FIGS. 14 to 19 are scenarios of a test automation method according to some embodiments of the present invention. These are drawings for explaining debugging of information.

The editing of the scenario information may be performed through the user device 340 . A user can easily edit the scenario information in a diagram through the user device 340 .

9 may show a screen for editing scenario information. The scenario information editing screen may include a graph area Rg and a state management area Rm.

The graph area Rg may be an area in which states and transitions are shown in a diagram. In FIG. 9 , a first state diagram S1 may be displayed by way of example. Since the relative relationship between states is important in scenario information, the first state diagram S1 can be easily edited by a user and freely arranged by a method such as drag and drop. However, the present embodiment is not limited thereto. Diagram information arranged in the graph area Rg may be stored in the user device 340 .

The state management area Rm may be an interface area in which the name, description, and action of whether to designate an initial state and the like of the state can be set. In this case, the action may mean an action to be performed when entering the state.

9 and 10 , scenario information may be displayed as at least one state and transition. For example, in FIG. 10 , the first state diagram S1 and the second state diagram S2 are connected by the first transition diagram T1, and the first state diagram S1 and the third state diagram S3 are connected. may be connected by the second transition diagram T2. The first transition diagram T1 and the second transition diagram T2 are indicated by arrows having a direction, so that a transition direction between states can be intuitively known. Although FIG. 10 illustrates two transition diagrams and three state diagrams by way of example, the scenario information of the present embodiment is not limited thereto. That is, the number and implementation form of the transition diagram and the state diagram may vary freely.

When the first state diagram S1 is selected, an action button AB capable of designating an action may be displayed in the state management area Rm. If “none” is selected as the action, the transition to the next state may be performed without any action in the state corresponding to the first state diagram S1 . During the action, the "Transition" button may show transition diagrams connected in the current first state diagram S1. That is, in FIG. 10 , the first transition diagram T1 and the second transition diagram T2 may be selectively displayed in the form of drop boxes. However, the present embodiment is not limited thereto and may be implemented as an interface of any other form.

10 and 11 , when the selection of the “Transition” button in the action button AB is completed, the job information may be embedded in the first state diagram S1 by using the “Job” button. When the "Job" button is selected from the action button AB, the job load button JLB may be displayed. The job load button JLB may be a button for embedding job information in a state.

3 and 12 , when the job load button JLB is selected, the job load window JLW may be generated on the screen. The job load window JLW may present a list of settable job information and select at least one of them. Through this, job information can be set in the state diagram. The user device 340 may store setting information of job information set in the state diagram. The job information may be stored in the database 160 of the test automation system 100 . According to the operation of the user device 340 , the database 160 may provide the job information to the user device 340 via the machine worker 120 , the application server 110 , and/or the web server 330 . . However, the present embodiment is not limited thereto.

3 and 13 , when job information is set, a job result handler JRH may be displayed. In the job result handler JRH, a transition corresponding to which transition diagram is to be performed may be described as a conditional expression under which condition for the job result value. The user device 340 may store designation information of the job result handler. At this time, the conditional expression includes the value of the HTTP response status code (statusCode) of the result value, the type of HTTP response headers, and the API response value composed of the HTML body or JSON, XML, etc. of the HTTP response body of the conditional expression. It can be used as a variable. However, the present embodiment is not limited thereto.

3 to 5 and 14 , when the user device 340 executes the edited scenario information, the application server 110 generates a finite state machine scenario corresponding to the scenario information and performs the test in the manner described above. carry out

In this case, the first log display window EL1 may be displayed on the screen of the user device 340 . In the first log display window EL1, the logs pushed from the log server 150 (operations <6>, <9>, <11>, <14>, <19>, <21>, < 23>, <25>, <28>, <34> and <38>) may be displayed.

Referring to FIG. 15 , the first log display window EL1 may be enlarged and displayed like the second log display window EL2 . The log displayed on the first log display window EL1 and the second log display window EL2 may include a date, a log type, a message, and additional information. The log type may be displayed in the form of, for example, [EnterState], [Transit], [Job], [JobResult], and [Error]. However, the present embodiment is not limited thereto.

14 to 16 , the first log display window EL1 and the second log display window EL2 may include an object information checker icon OII.

Referring to FIG. 17 , when the user selects the object information checker icon OII, the object information checker may be executed. When the object information inspector is executed, an object information inspection window (OIW) may be displayed on the screen. In the object information inspection window (OIW), more detailed confirmation may be possible. The object information inspection window (OIW) may provide various functions when detailed information uses an object format such as JavaScript Object Notation (JSON). For example, the object information inspection window (OIW) is structured so that the user can read it easily (JSON Prettify), and returns a specific value by entering the key name of detailed information (Console), and the part you want to know in the JSON area. If you click , you can provide functions such as tracking the key name that accesses the corresponding value and displaying it on the lower console (Key Finder). However, the present embodiment is not limited thereto.

3 and 18 , after the execution of the finite state machine scenario corresponding to the scenario information is finished, the user device 340 may generate the history window HW.

The user device 340 may inquire the result of the corresponding execution, log record, and log analysis in the history window HW.

Referring to FIG. 19 , the third log display window EL3 may be displayed in the history window HW as individual execution is selected. The third log display window EL3 may display the same information as the first log display window EL1 and the second log display window EL2 .

Although the embodiments of the present invention have been described above with reference to the accompanying drawings, those of ordinary skill in the art to which the present invention pertains can realize that the present invention can be embodied in other specific forms without changing its technical spirit or essential features. you will be able to understand Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive.

110: application server
120: machine worker
150: log server
160: database

Claims (15)

An application server that receives scenario information and generates a finite state machine (FSM) scenario based on the scenario information, wherein the finite state machine scenario includes at least one state and a transition between the states; an application server embedded in the state and including a job set as a condition for performing the transition;
a machine worker receiving and executing the finite state machine scenario;
a database storing the scenario information and job information corresponding to the job, providing the scenario information to the application server, and providing the job information to the machine worker;
a job worker receiving a request for execution of the job from the machine worker and processing the job; and
Including an internal network isolated from an external network and responding to a request for a job corresponding to the job from the job worker,
The job includes a first job requesting an API (Application Program Interface) and a second job including a web page uniform resource locator (URL),
The job worker includes a first job worker for processing the first job and a second job worker for processing the second job,
The internal network includes an internal API server and an internal web page,
The first job worker requests the API to the internal API server in response to the first job,
and the second job worker requests the web page URL to the internal web page in response to the second job, and performs a preset user operation according to a predefined script.
delete delete According to claim 1,
The external network includes an external API server and an external web page,
The first job worker requests the API to the external API server in response to the first job,
The second job worker is a test automation network system for requesting the web page URL to the external web page in response to the second job.

5. The method of claim 4,
The test automation network system further comprising a proxy server connecting the job worker and the external network.
According to claim 1,
The external network test automation network system further comprising a web server that connects the application server and the user.
7. The method of claim 6,
The test automation network system further comprising a log server for receiving and storing the log from the machine worker, and transmitting the log to the user.
According to claim 1,
A test automation network system, further comprising: a deployment system including an execution schedule therein, and instructing the application server to generate the finite state machine scenario according to the execution schedule.
According to claim 1,
and a distribution system for causing the application server to generate the finite state machine scenario, and for receiving a scenario result from the application server and distributing a service corresponding to the finite state machine scenario.
According to claim 1,
The scenario information is edited into a diagram of a test automation network system.
A database receives and stores scenario information corresponding to a finite state machine scenario including a state, a transition between the states, and a job embedded in the state and set as an execution condition of the transition,
a machine worker executing a finite state machine scenario according to the scenario information;
The state includes a first state and a second state,
The job includes any one of a first job and a second job embedded in the first state,
Executing the finite state machine scenario comprises:
run into the first state,
executing any one of the first job and the second job;
Transitioning to the second state according to a result of any one of the first job and the second job,
Executing any one of the first job and the second job comprises:
The job worker transmits a request corresponding to any one of the first job and the second job to the internal network isolated from the external network,
Comprising that the internal network responds to a request corresponding to any one of the first job and the second job,
The first job is a job that requests an API,
The internal network includes an internal API server,
The job worker includes a first job worker that requests the API to the internal API server,
The second job is a job that requests a web page URL,
The internal network includes an internal web page,
and the job worker requests the web page URL to the internal web page and includes a second job worker that performs a preset user action according to a predefined script.
12. The method of claim 11,
Receiving the scenario information includes:
Comprising that the scenario information is edited into a diagram,
When the scenario information is edited into a diagram,
arrangement information of at least one state diagram corresponding to the state is stored;
arrangement information of at least one transition diagram corresponding to the transition is stored between the state diagrams;
setting information of job information corresponding to the job is stored in the state diagram;
and storing designation information on which one of the transitions is executed according to a result value of the job.
13. The method of claim 12,
The database stores the job information and provides a test automation method according to a request.
delete delete

Images