KR102481254B1 - Apparatus and method for test automation service - Google Patents

Abstract

A test automation service apparatus and method are disclosed. A test automation service method according to an embodiment includes obtaining a test script corresponding to a test option selected by a user from a server where one or more test scripts are registered; Transmitting a test request including the acquired test script to a server connected to one or more terminals under test; obtaining a snapshot of a test performed in one or more terminals under test; and providing a user with a report including a snapshot of the test.

Description

Test automation service device and method {APPARATUS AND METHOD FOR TEST AUTOMATION SERVICE}

The disclosed embodiments relate to technology for providing test automation services.

Since most software, including online games, is distributed and used by a large number of users, it must be produced with excellent quality to meet the various needs of users.

To this end, before distributing the software or updating a new version after distributing the software, it is necessary to test the software in terms of various quality characteristics such as functionality, reliability, usability, efficiency, maintainability, and portability.

However, in the prior art, even if the software is tested, a log of test results is provided as it is or only data on whether the test is successful or not is simply provided, and thus it is difficult for a user to intuitively grasp detailed test results.

Republic of Korea Patent Registration No. 10-1196522 (registered on October 25, 2012)

The disclosed embodiments are intended to provide more intuitive software test results to users through snapshots.

A test automation service method according to an embodiment disclosed herein includes obtaining a test script corresponding to a test option selected by a user from a server where one or more test scripts are registered; Transmitting a test request including a test script to a server connected to one or more test target terminals; obtaining a snapshot of a test performed in one or more terminals under test; and providing a user with a report including a snapshot of the test.

The operation of acquiring a snapshot may acquire a snapshot of a game screen output from each of one or more test target terminals as the test is performed.

The operation of obtaining a snapshot may obtain a snapshot for each of one or more actions performed in each of one or more test target terminals according to a test script.

The operation of providing a report may provide a report in which the snapshots are arranged according to the order in which tests were performed for each of one or more terminals under test.

The operation of providing a report may provide a report in which snapshots are arranged in a table in which identification information for each of one or more terminals under test is set as a row or column, and an order in which tests are performed is set as other rows or columns.

The operation of providing a report includes identification information on one or more terminals under test, name of a server providing game service to each of the one or more terminals under test, and identification information on one or more actions performed in each of the one or more terminals under test. A report including at least one more may be provided.

A test automation service apparatus according to an embodiment disclosed herein includes one or more processors; and a memory for storing one or more programs configured to be executed by one or more processors, wherein the program acquires a test script corresponding to a test option selected by a user from a server where the one or more test scripts are registered. ; Transmitting a test request including a test script to a server connected to one or more test target terminals; obtaining a snapshot of a test performed in one or more terminals under test; and instructions for executing an operation of providing a user with a report containing a snapshot of the test.

The operation of acquiring a snapshot may acquire a snapshot of a game screen output from each of one or more test target terminals as the test is performed.

The operation of obtaining a snapshot may obtain a snapshot for each of one or more actions performed in each of one or more test target terminals according to a test script.

The operation of providing a report may provide a report in which the snapshots are arranged according to the order in which tests were performed for each of one or more terminals under test.

The operation of providing a report may provide a report in which snapshots are arranged in a table in which identification information for each of one or more terminals under test is set as a row or column, and an order in which tests are performed is set as other rows or columns.

The operation of providing a report includes identification information on one or more terminals under test, name of a server providing game service to each of the one or more terminals under test, and identification information on one or more actions performed in each of the one or more terminals under test. A report including at least one more may be provided.

According to the disclosed embodiments, a user can intuitively recognize a test result by providing a snapshot of an execution result of an action performed according to a test script.

In addition, according to the disclosed embodiments, snapshots are sorted based on test target device, performed action, etc. and provided in the form of a table, so that a user can quickly identify the test target device or action in which a problem occurred. can

1 is a block diagram for explaining a test automation service system according to an embodiment
Figure 2 is a block diagram for explaining a test automation service device according to an embodiment
3 is an exemplary view showing a test automation service screen according to an embodiment
4 is an exemplary view showing a screen on which a report is provided according to an embodiment;
5 is a flowchart for explaining a test automation service method according to an embodiment
6 is a block diagram for illustrating and describing a computing environment including a computing device according to an exemplary embodiment;

Hereinafter, specific embodiments will be described with reference to the drawings. The detailed descriptions that follow are provided to provide a comprehensive understanding of the methods, devices and/or systems described herein. However, this is only an example and disclosed embodiments are not limited thereto.

In describing the embodiments, if it is determined that a detailed description of related known technologies may unnecessarily obscure the gist of the disclosed embodiments, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the disclosed embodiments, which may vary according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout this specification. Terminology used in the detailed description is only for describing the embodiments and should in no way be limiting. Unless expressly used otherwise, singular forms of expression include plural forms. In this description, expressions such as "comprising" or "comprising" are intended to indicate any characteristic, number, step, operation, element, portion or combination thereof, one or more other than those described. It should not be construed to exclude the existence or possibility of any other feature, number, step, operation, element, part or combination thereof.

1 is a block diagram illustrating a test automation service system according to an exemplary embodiment.

As shown, the test automation service system according to an embodiment includes a first server 1, a second server 2, a third server 3, a test candidate terminal 4, and a test automation service device 100. includes

In the following embodiments, 'testing' means an act of inspecting software in a development stage, a mass production stage, or a stage after distribution so that the software can have a certain level of quality. In other words, 'testing' is a concept including Quality Assurance (QA) activities and Quality Control (QC) activities for software.

Specifically, 'testing' means finding defects remaining in the software, improving inefficiently configured parts, verifying that the software complies with the requirements of the software development specification, verifying that it meets the user's needs, or pre-set operating conditions. It can be performed for a variety of purposes, such as ensuring that it operates properly under the environment.

The first server 1 and the second server 2 are devices in which files necessary for performing software tests are registered, and the test automation service device receives a request for access to specific files from the test automation service device 100. Originals or copies of the requested files may be transmitted to (100).

Meanwhile, in FIG. 1, the first server 1 and the second server 2 are shown separately, and this is to functionally distinguish each server in that the types of files registered in each server are different. That is, the first server 1 and the second server 2 may actually be different computing devices, but are not necessarily limited thereto, and may be merely functionally divided identical computing devices.

The third server 3 is connected to the test candidate terminals 4 and transmits information for performing a software test to at least some test target terminals among the test candidate terminals 4 according to a request received from the test automation service device 100. It is a device that That is, in the following embodiments, a 'server connected to a terminal under test' is interpreted as referring to the third server 3 .

Specifically, the third server 3 is a server that provides the test candidate terminal 4 with the software that the user wants to test. For example, when the user wants to test a specific game A, the third server 3 ) denotes a server that serves the game A to the test candidate terminal 4.

In this case, 'game' refers to software that one or more gamers can enjoy using an input device mounted on or connected to a gaming device. In general, it proceeds in such a way as directly manipulating a player character or manipulating the movement of an object in a game, and genres such as role-playing, adventure, and arcade are sometimes divided.

In addition, a 'gaming device' is hardware that executes game software, performs calculations according to user input through an input device, and outputs results through an output device, such as a smart phone or tablet PC ( It may be in the form of a tablet PC), a smart watch, a smart band, or a personal computer. In addition, any device that satisfies the above definition is interpreted as belonging to a gaming device.

The test candidate terminal 4 is a terminal connected to the third server 3 and includes a test target terminal, and the test target terminal is automated according to a request transmitted from the test automation service device 100 to the third server 3. means the device on which the tested software tests are performed.

For an effective software test, a test target terminal must include as many types of terminals as possible to support the software to be tested. For example, if a mobile game called B is to be tested, a terminal under test should include as many types of mobile devices as possible supporting mobile game B.

In FIG. 1 exemplarily, the test candidate terminal 4 is shown as a set of N terminals 4-1, 4-2, ..., 4-N, but this indicates that one or more terminals are configured by a third server 3 ), and it should be noted that the test candidate terminal 4 can be connected within a preset limit in consideration of the socket or traffic of the third server 3.

In the embodiments described above with reference to FIG. 1, the first server 1, the second server 2, the third server 3, the test candidate terminal 4, and the test automation service device 100 exchange and receive. A set of information can be transmitted through a communication network, such as the Internet, one or more local area networks, wire area networks, cellular networks, mobile networks, and other types of networks. , or a combination of these networks.

2 is a block diagram illustrating a test automation service device 100 according to an exemplary embodiment.

As shown, the test automation service device 100 according to an embodiment includes a test script acquisition unit 110, a test request unit 120, a snapshot acquisition unit 130, and a report providing unit 140. .

The test script acquisition unit 110 acquires a test script corresponding to a test option selected by a user from a server where one or more test scripts are registered.

In the following embodiments, a 'test script' refers to a file in which one or more actions necessary for a developer to perform a software test are described in code form.

In addition, in the following embodiments, a 'test option' refers to selectable details provided to users so that they can select a test script or a corresponding action in relation to a software test.

The test requesting unit 120 transmits a test request including the obtained test script to a server connected to one or more test target terminals.

The snapshot acquisition unit 130 acquires snapshots of tests performed in one or more test target terminals.

According to an embodiment, the snapshot acquisition unit 130 may obtain a snapshot for the test directly from each terminal under test, or through a server to which the test request unit 120 has transmitted the test request. . However, the path through which the snapshot acquisition unit 130 acquires a snapshot is not limited thereto, and according to an embodiment, the snapshot acquisition unit 130 may use a separate server (for example, a cloud service) to which each terminal under test is connected. You can also get a snapshot of the test by accessing the server that provides the test.

According to an embodiment, the snapshot acquisition unit 130 may obtain a snapshot of a game screen output from each of one or more test target terminals as the test is performed.

Specifically, the snapshot acquired by the snapshot acquiring unit 130 is a game application execution screen, a game login screen, a game play screen, a game event screen, a game story transmission screen, a game logout screen, a game end screen, and the like. Snapshots of arbitrary screens that can be output on the device under test from execution to termination may be included.

According to an embodiment, the snapshot acquisition unit 130 may obtain snapshots for each of one or more actions performed in each of one or more test target terminals according to a test script.

According to an embodiment, the snapshot acquisition unit 130 may acquire a snapshot captured after a predetermined time elapses after a command according to a test script is executed in each of one or more test target terminals.

The report providing unit 140 provides a report including a snapshot of the test to the user.

Specifically, the test script may include a command to capture a game screen output as the test is performed, and when the corresponding command is called, the report providing unit 140 reports the snapshot captured by the corresponding command. Including can be provided to the user.

According to an embodiment, the report providing unit 140 may provide a report in which snapshots are arranged according to the order in which tests were performed for each of one or more test target terminals.

Specifically, in the report provided by the report providing unit 140, the snapshots described above may be arranged in a table in a preset format. For example, a row or column of a table in which snapshots are arranged may be set as identification information for each of one or more terminals under test, and the remaining rows or columns may be set in the order in which tests were performed.

Through this, the user who is provided with the report can intuitively recognize whether the test action has been successfully executed as the test is performed for each type of terminal under test simply by viewing the sorted snapshots.

According to an embodiment, the report providing unit 140 may provide a user with a report in which snapshots corresponding to actions that fail to be executed among one or more actions performed in each of one or more test target terminals are separately sorted.

According to an embodiment, the report providing unit 140 includes identification information on one or more test target terminals, a name of a server that provides a game service to each of the one or more test target terminals, and one or more information performed in each of the one or more test target terminals. A report further including at least one of identification information on an action may be provided.

Specifically, the 'server providing game service' is a separate server from the first server 1, second server 2, and third server 3 described above in FIG. 1, and is provided in each terminal to be tested. Through the game application, a series of information required for game operation may be transmitted to each terminal under test, and a response may be transmitted to the terminal under test based on an input input to the terminal under test.

3 is an exemplary view showing a test automation service screen according to an embodiment.

Referring to FIG. 3 , a 'test option editing page' is shown on the left side of the screen, a 'build registration page' is shown on the upper right corner of the screen, and a 'test script management page' is shown on the lower right corner of the screen.

First, the 'test option edit page' is a graphical user interface (GUI) provided to the user so that the user can select a test option, and includes 'name', 'description', 'test resource', 'device', It includes items such as 'result receiver' and 'autorun'.

'Name' is an item that can be arbitrarily entered by a user to distinguish a software test, and 'description' is an item in which a user writes a comment about a corresponding software test.

On the other hand, 'test resource' is an item for selecting files and test scenarios to be used for performing software tests.

Specifically, the user may select one of the Android operating system and the iOS operating system to select a test virtual environment under the corresponding operating system. To this end, the 'test resource' item includes a graphic object 301 providing a list of test virtual environment files under the Android operating system and a graphic object 302 providing a list of test virtual environment files under the iOS operating system.

In addition, the 'test resource' item includes a graphic object 303 that provides a list of one or more predefined test scenarios so that the user can select a desired test scenario.

In addition, in addition to the test scripts registered in the second server 2, the user can directly upload a test script he/she wants and apply it to the test target terminal. A 'select file' graphical object 305 is included to upload the test script stored in the storage space of the computing device of the computer.

'Device' is an item through which the user can select a terminal to be tested from among test candidate terminals 4, and for this purpose, a 'device selection' graphic object 306 is included in the 'device' item.

The 'result recipient' is an item through which the user can designate a target to receive the test result, and for this purpose, a recipient input box 307 is provided in the 'result recipient' item. In addition, a 'receive intermediate result' check button 308 is provided in the 'result recipient' item so that the user can check the intermediate result not only after the entire test is performed, but also in the middle of the test.

'Auto Execution' refers to a check button that determines whether or not to automatically execute a software test so that, when a new build file is registered in the first server 1, software tests are automatically performed without user intervention through test option selection, and information about elapsed time conditions. An input field is provided.

On the other hand, the 'build registration page' is a GUI that provides a list of build files registered in the first server 1 to the user, and displays related build files listed under an upper level build set (build 1, build 2, etc.). (builds 1-1, 1-2, 1-3, 2-1, 2-2, 2-3, etc.).

At this time, a third party who wants to register the build file to the first server 1 can register the build file by logging in to the 'build registration page', and after completing the registration, click the 'logout' graphic object 309. By doing so, you can log out from the 'Build Registration Page'.

In addition, the user of the 'build registration page' can easily download related build files by clicking the 'download' graphic objects 310 and 311 shown next to each upper build set.

In this case, the 'build file' refers to a file in which a source code file prepared by a developer is implemented in the form of a software product executable on a computing device.

On the other hand, the 'test script management page' is a GUI that provides a list of test scripts registered in the second server 2 to the user. display information

In addition, the name of each registered test script is provided through the 'test script name' item 313, and a description of the content recently modified in each test script is provided through the 'recent commit' item 314, Through the 'recent registration' item 315, the date of the recent registration of each test script is provided.

Each item, graphic object, check button, input box, etc. shown in FIG. 3 above is illustrative, and additional configurations may be included in the 'test option edit page', 'build registration page' or 'test script management page'. self-explanatory

Hereinafter, a report provided as a test execution result will be described with reference to FIG. 4 as an example.

4 is an exemplary diagram illustrating a screen on which a report is provided according to an exemplary embodiment.

In detail, FIG. 4 shows a report page in which snapshots of game screens output as actions are performed in each of a plurality of test target terminals are arranged in a predefined table form.

First of all, the snapshot 401 placed in 48 columns of a table with 8 rows and 6 columns is a game that is output through the output device of each terminal or an external output device connected to the terminal as the action is performed in each terminal under test. Represents a snapshot of the screen.

At this time, six columns of the table are classified according to the type of each terminal under test, and eight rows are divided according to the order of tests performed in each terminal under test.

In other words, the six columns of the table represent a total of six terminals under test 406. Columns 1 to 4 are terminals under test of different 'Galaxy Note8' models, and columns 5 and 6 are driven devices. Indicates different terminals under test where the 'Nox' service is running. In addition, according to the embodiment, the six columns of the table further indicate the names of in-game servers (Deforge 01, Kenlauhel 01, Pandora 01, Death Knight 01, Duke Devil 01, and Antaras 01) accessed by each test target device. can indicate

In addition, eight columns of the table indicate a test sequence of a total of eight steps, and each step corresponds to an action performed in a terminal under test. As shown in FIG. 4, looking at the 'test case 402', which is a name indicating the type of each action, the order in which the test is performed is the 'test_install_execution' step in which the game application is installed and then executed, the game You can see that it goes through the 'test_login' step of trying to access the game with your account, and the 'test_mail' step of checking the mail sent and received within the game.

On the other hand, among the snapshots placed in 48 spaces of the table, the snapshots in the second row, fifth column, and the snapshots in the second row and sixth column (4011) are output when login to the game fails because the password is not entered in the test target device. It is a snapshot of the game screen that displays a pop-up window informing that 'an error occurred while connecting to the server'.

In addition, among the snapshots placed in the 48 columns of the table, the snapshots in the third row, fifth column, and the third row, sixth column (4012) are output when login to the game fails due to incorrect password entry in the test terminal. This is a snapshot of the game screen that is being played, and similarly corresponds to a snapshot of the game screen displaying a pop-up window informing that 'an error occurred while connecting to the server'.

Through this, the user sees the snapshots (4011, 4012) that have a clear difference in appearance from other snapshots among the snapshots arranged in the 48 spaces, and immediately corresponds to the corresponding test target terminal ('Nox[21]', It can be recognized that a problem has occurred in the test sequence (second and third sequences) of the terminal identified as 'Nox[22]'.

In addition, in order to clearly indicate the test sequence corresponding to the columns of the table, the report contains 'Test Case 402', which is a name indicating the type of each action, as well as 'Area 403', which indicates the function of each action in the game. Elements such as 'item 404' representing a description of the report and 'step 405' describing each action in more detail may be further included, but the elements that may be included in the report are not necessarily limited thereto.

According to one embodiment, when a user selects the 'screen shot 408' tab through the input/output device of the test automation service device 100, the report provider 140 may provide a report in which snapshots are arranged. If you select the 'Total Results (407)' tab, you can provide snapshots as well as overall test results according to the test script. In addition, when the user selects the 'failed item 409' tab, the report providing unit 140 may sort snapshots of failed actions separately and provide the snapshots to the user.

According to one embodiment, the report provider 140 determines the column width of the table in which the snapshots are arranged when the user selects the 'column width adjustment 410' button through the input/output device of the test automation service device 100. can be adjusted. In this case, the column width may be automatically adjusted according to a predetermined width according to the selection of the button, but depending on the embodiment, a separate window may be popped up and then adjusted according to a value set by the user in the corresponding window.

According to one embodiment, the report providing unit 140 provides a report including a snapshot to the user when the user selects the 'export to CSV file (411)' button through the input/output device of the test automation service device 100. may be provided in the form of a file with a CSV (Comma-Separated Values) extension.

5 is a flowchart illustrating a test automation service method according to an embodiment.

The method shown in FIG. 5 may be performed, for example, by the test automation service device 100 described above.

First, the test automation service device 100 obtains a test script corresponding to a test option selected by a user from a server where one or more test scripts are registered (510).

Thereafter, the test automation service device 100 transmits a test request including the obtained test script to a server connected to one or more test target terminals (520).

Thereafter, the test automation service device 100 obtains snapshots of tests performed in one or more test target terminals (530).

Thereafter, the test automation service device 100 provides a report including a snapshot of the performed test to the user (540).

In the illustrated flowchart, the operation is divided into a plurality of operations, but at least some operations are performed in reverse order, combined with other operations, performed together, omitted, divided into detailed operations, or not shown. One or more actions may be added and performed.

6 is a block diagram illustrating and describing a computing environment 10 including a computing device according to an exemplary embodiment. In the illustrated embodiment, each component may have different functions and capabilities other than those described below, and may include additional components other than those described below.

The illustrated computing environment 10 includes a computing device 12 . In one embodiment, computing device 12 may be test automation service device 100 .

Computing device 12 includes at least one processor 14 , a computer readable storage medium 16 and a communication bus 18 . Processor 14 may cause computing device 12 to operate according to the above-mentioned example embodiments. For example, processor 14 may execute one or more programs stored on computer readable storage medium 16 . The one or more programs may include one or more computer-executable instructions, which when executed by processor 14 are configured to cause computing device 12 to perform operations in accordance with an illustrative embodiment. It can be.

Computer-readable storage medium 16 is configured to store computer-executable instructions or program code, program data, and/or other suitable form of information. Program 20 stored on computer readable storage medium 16 includes a set of instructions executable by processor 14 . In one embodiment, computer readable storage medium 16 includes memory (volatile memory such as random access memory, non-volatile memory, or a suitable combination thereof), one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, other forms of storage media that can be accessed by computing device 12 and store desired information, or any suitable combination thereof.

Communications bus 18 interconnects various other components of computing device 12, including processor 14 and computer-readable storage medium 16.

Computing device 12 may also include one or more input/output interfaces 22 and one or more network communication interfaces 26 that provide interfaces for one or more input/output devices 24 . An input/output interface 22 and a network communication interface 26 are connected to the communication bus 18 . Input/output device 24 may be coupled to other components of computing device 12 via input/output interface 22 . Exemplary input/output devices 24 include a pointing device (such as a mouse or trackpad), a keyboard, a touch input device (such as a touchpad or touchscreen), a voice or sound input device, various types of sensor devices, and/or a photographing device. input devices, and/or output devices such as display devices, printers, speakers, and/or network cards. The exemplary input/output device 24 may be included inside the computing device 12 as a component constituting the computing device 12, or may be connected to the computing device 12 as a separate device distinct from the computing device 12. may be

Meanwhile, embodiments of the present invention may include a program for performing the methods described in this specification on a computer, and a computer readable recording medium including the program. The computer readable recording medium may include program instructions, local data files, local data structures, etc. alone or in combination. The media may be specially designed and configured for the present invention, or may be commonly available in the field of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and specially configured to store and execute program instructions such as ROM, RAM, and flash memory. Hardware devices are included. Examples of the program may include not only machine language codes generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter.

Although representative embodiments of the present invention have been described in detail above, those skilled in the art will understand that various modifications are possible to the above-described embodiments without departing from the scope of the present invention. . Therefore, the scope of the present invention should not be limited to the described embodiments and should not be defined, and should be defined by not only the claims to be described later, but also those equivalent to these claims.

1: first server
2: Second server
3: 3rd server
4 (4-1, 4-2, ..., 4-N): test candidate terminal
10: Computing environment
12: computing device
14: Processor
16: computer readable storage medium
18: communication bus
20: program
22: I/O interface
24: I/O device
26: network communication interface
100: test automation service device
110: test script acquisition unit
120: test request unit
130: snapshot acquisition unit
140: report providing unit

Claims (12)

obtaining a test script corresponding to a test option selected by a user from a server in which one or more test scripts are registered;
transmitting a test request including the acquired test script to a server connected to one or more terminals under test;
acquiring a snapshot of a test performed in the one or more terminals under test; and
providing the user with a report including a snapshot of the test;
The operation of providing the report,
According to the user's request, a report in which snapshots corresponding to actions that have failed to be executed among the one or more actions performed in each of the one or more test target terminals is separately sorted is provided to the user. The method of claim 1,
The operation of acquiring the snapshot is,
Acquiring a snapshot of a game screen output from each of the one or more test target terminals as the test is performed. The method of claim 1,
The operation of acquiring the snapshot is,
Acquiring a snapshot for each of one or more actions performed in each of the one or more test target terminals according to the acquired test script. The method of claim 1,
The operation of providing the report,
The test automation service method of providing a report in which the snapshots are sorted according to the order in which the test was performed for each of the one or more terminals under test. The method of claim 4,
The operation of providing the report,
The test automation service method of providing a report in which the snapshots are arranged in a table in which the identification information for each of the one or more test target terminals is set as a row or column, and the order in which the tests were performed is set as the remaining rows or columns. The method of claim 1,
The operation of providing the report,
At least one of identification information on the one or more terminals under test, a name of a server providing a game service to each of the one or more terminals under test, and identification information on one or more actions performed in each of the one or more terminals under test A test automation service method that provides reports containing one or more processors; and
An apparatus comprising a memory storing one or more programs configured to be executed by the one or more processors,
said program,
obtaining a test script corresponding to a test option selected by a user from a server in which one or more test scripts are registered;
transmitting a test request including the acquired test script to a server connected to one or more terminals under test;
acquiring a snapshot of a test performed in the one or more terminals under test; and
Includes instructions for executing an operation of providing the user with a report containing a snapshot of the test;
The operation of providing the report,
According to the user's request, among the one or more actions performed in each of the one or more test target terminals, a report in which snapshots corresponding to actions that have failed to be executed are separately sorted is provided to the user. The method of claim 7,
The operation of acquiring the snapshot is,
Acquire a snapshot of a game screen output from each of the one or more test target terminals as the test is performed. The method of claim 7,
The operation of acquiring the snapshot is,
Acquiring a snapshot for each of one or more actions performed in each of the one or more test target terminals according to the acquired test script. The method of claim 7,
The operation of providing the report,
The test automation service device providing a report in which the snapshots are arranged according to the order in which the test was performed for each of the one or more terminals under test. The method of claim 10,
The operation of providing the report,
The test automation service device providing a report in which the snapshots are arranged in a table in which the identification information for each of the one or more terminals under test is set as a row or column, and the order in which the tests were performed is set as the remaining rows or columns. The method of claim 7,
The operation of providing the report,
At least one of identification information on the one or more terminals under test, a name of a server providing a game service to each of the one or more terminals under test, and identification information on one or more actions performed in each of the one or more terminals under test A test automation service unit that provides reports including

Images