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

Abstract

Disclosed are an apparatus and method for test automation service. According to an embodiment of the present invention, the method for test automation service comprises: a step of providing a user with a test option including a list of one or more pre-defined test scenarios, and a list of test target terminals connected to a server; a step of acquiring a plurality of test scripts corresponding to the test scenario selected by the user from the list of one or more test scenarios based on the selection of the user for the test option; a step of respectively matching the plurality of test target terminals selected by the user among the acquired plurality of test scripts and the list of test target terminals; and a step of transmitting a test request to the server so that the test script matched in each of the plurality of test target terminals selected by the user can be conducted. The present invention aims to provide an apparatus and method for test automation service, which are capable of innovatively reducing the time required for a test.

Description

TEST AUTOMATION SERVICE APPARATUS AND METHOD FOR TEST AUTOMATION SERVICE

Disclosed embodiments relate to techniques for providing test automation services.

Since most software, including online games, are distributed and used by many users, they must be produced with high quality to meet the diverse needs of users.

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

However, recently, as the structure of software becomes more complex, the number of items to be tested is gradually increasing, and when a test is performed by applying one test scenario to one device from beginning to end, there is a problem that the test takes an excessive amount of time. .

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

The disclosed embodiments are for performing one test scenario by dividing it in several devices.

The test automation service method according to the disclosed embodiment provides an operation of providing a test option including a list of one or more predefined test scenarios and a list of a test target terminal connected to a server to a user, a user's selection of the test option Based on the operation of obtaining a plurality of test scripts corresponding to the test scenario selected by the user from the list of one or more test scenarios, It includes an operation of matching each and an operation of transmitting a test request to the server so that the matched test script is performed in each of a plurality of test target terminals selected by the user.

The test option may further include a list of test scripts for each test scenario constituting each of one or more test scenarios, and the matching operation includes a list of test scripts constituting a test scenario selected by the user and a plurality of test scripts selected by the user. It may include an operation of obtaining matching information between the test target terminals of , and an operation of respectively matching a plurality of test scripts obtained based on the matching information and a plurality of test target terminals selected by the user.

In the matching operation, a plurality of acquired test scripts and a plurality of test target terminals selected by the user may be matched based on a preset matching criterion.

In the matching operation, at least one test script may be matched to each of the plurality of test target terminals selected by the user.

The matching operation may be performed so that each of the plurality of acquired test scripts is not repeatedly applied to the plurality of test target terminals selected by the user.

In the matching operation, the test script stored in the specific folder is matched with the test target terminal corresponding to the specific folder by dividing and storing a plurality of test scripts obtained in a pre-generated folder corresponding to each of the plurality of test target terminals selected by the user can do.

A test automation service apparatus according to an embodiment of the present disclosure is a device including a memory for storing one or more programs configured to be executed by one or more processors, wherein the program includes a list of one or more test scenarios predefined to a user and Acquire a plurality of test scripts corresponding to the test scenario selected by the user from the list of one or more test scenarios based on the operation of providing a test option including a list of test target terminals connected to the server, and the user's selection of the test option operation, the operation of matching each of the plurality of test target terminals selected by the user from the list of the acquired plurality of test scripts and the test target terminals, and testing the server so that the matched test script is performed on each of the plurality of test target terminals selected by the user Contains instructions for executing the operation of sending the request.

The test option may further include a list of test scripts for each test scenario constituting each of one or more test scenarios, and the matching operation includes a list of test scripts constituting a test scenario selected by the user and a plurality of test scripts selected by the user. may include an operation of further acquiring matching information between the test target terminals of

In the matching operation, a plurality of acquired test scripts and a plurality of test target terminals selected by the user may be matched based on a preset matching criterion.

In the matching operation, at least one test script may be matched to each of the plurality of test target terminals selected by the user.

The matching operation may be performed so that each of the plurality of acquired test scripts is not repeatedly applied to the plurality of test target terminals selected by the user.

In the matching operation, the test script stored in the specific folder is matched with the test target terminal corresponding to the specific folder by dividing and storing a plurality of test scripts obtained in a pre-generated folder corresponding to each of the plurality of test target terminals selected by the user can do.

According to the disclosed embodiments, a plurality of test scripts constituting a test scenario are divided and performed by a plurality of test target terminals, thereby remarkably reducing the time required for a test.

1 is a block diagram illustrating a test automation service system according to an embodiment;
2 is a block diagram of a test automation service apparatus according to an embodiment;
3 is an exemplary diagram illustrating a test automation service screen according to an embodiment;
4 is an exemplary diagram for explaining a result of a test performed according to an embodiment;
5 is a flowchart illustrating a test automation service method according to an embodiment;
6 is a block diagram illustrating and explaining a computing environment including a computing device according to an embodiment;

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

In describing the embodiments, if it is determined that a detailed description of a related known technology may unnecessarily obscure the gist of the disclosed embodiments, the detailed description thereof will be omitted. And, the 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 and operators. Therefore, the definition should be made based on the content throughout this specification. The terminology used in the detailed description is for the purpose of describing the embodiments only, and should in no way be limiting. Unless explicitly used otherwise, expressions in the singular include the meaning of the plural. In this description, expressions such as “comprising” or “comprising” are intended to indicate certain features, numbers, steps, acts, elements, some or a combination thereof, one or more other than those described. It should not be construed to exclude the presence or possibility of other features, numbers, steps, acts, elements, or any part or combination thereof.

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

Referring to FIG. 1 , a 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 apparatus 100 . ) is included.

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

Specifically, 'test' is to find defects remaining in the software, to improve inefficiently configured parts, to confirm that the software complies with the requirements in the software development specification, to confirm that it meets the user's needs, or to run a preset operation. 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 a software test are registered, and receive a request for access to specific files from the test automation service device 100 to provide a test automation service device. You can send originals or copies of requested files to (100).

Meanwhile, in FIG. 1 , the first server 1 and the second server 2 are separately illustrated, and this is to functionally classify 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 be actually different computing devices, but are not necessarily limited thereto, and may merely be functionally divided into the same 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 of the test target terminals among the test candidate terminals 4 according to a request received from the test automation service apparatus 100 . is a device that

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 the specific game A, the third server 3 ) denotes a server serving the game A to the test candidate terminal 4 .

In this case, the term 'game' refers to software that one or more gamers can enjoy using an input device mounted on or connected to a gaming device. Usually, it is performed by directly manipulating the player character or by manipulating the movement of objects in the game, and genres such as role-playing, adventure, and arcade are sometimes classified.

In addition, the 'gaming device' is hardware that executes game software but performs calculations according to the user's input through the input device and outputs the result through the output device, for example, a smartphone (Smart Phone), tablet PC ( It may be in the form of a tablet PC), a smart watch, a smart band, or a personal computer. In addition, if the device satisfies the above definition, it is interpreted as belonging to the 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 specified software test is performed.

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

1 exemplarily shows the test candidate terminal 4 as a set of a total of N terminals 4-1, 4-2, ..., 4-N, however, this means that one or more terminals use the third server 3 ), and it should be noted that the test candidate terminal 4 may 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 A set of information may be transmitted over a communication network, wherein the communication network includes the Internet, one or more local area networks, wire area networks, cellular networks, mobile networks, or any other type of network. , or a combination of these networks.

2 is a block diagram of a test automation service apparatus 100 according to an embodiment.

As shown, the test automation service apparatus 100 according to an embodiment includes a test option providing unit 110 , an acquiring unit 120 , a matching unit 130 , and a test requesting unit 140 .

The test option providing unit 110 provides the user with a test option including a list of one or more predefined test scenarios and a list of test target terminals connected to the server.

Specifically, the 'test option' refers to selectable details provided to a user so that the user can select a test scenario or a test target terminal in relation to software testing.

In the following embodiments, a 'test scenario' means information defining a combination of one or more test scripts and an order to be performed so that a user can achieve a specific purpose by performing a software test.

For example, a test scenario in which game character B of game A attacks game mob C once is tested. of the test script related to the motion of moving near game mob C, the motion of game character B attacking the game mob C with the weapon he is wearing, and the motion of applying changes to the health and state of game mob C according to the attack. Define combinations and sequences.

Also, 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. Hereinafter, for convenience of description, the code describing the test script will be referred to as the test code.

According to an embodiment, the test option may further include a list of test scripts for each test scenario constituting each of one or more test scenarios.

For example, when the test scripts C-1, C-2, and C-3 are gathered to form a test scenario called C, the test option providing unit 110 is a sub-item for the test scenario called C-1, C-1, You can provide a list of test scripts called C-2 and C-3.

The acquisition unit 120 acquires a plurality of test scripts corresponding to the test scenario selected by the user from the list of one or more test scenarios based on the user's selection of the test option.

The matching unit 130 matches the plurality of test scripts acquired by the acquiring unit 120 with the plurality of test target terminals selected by the user from the list of test target terminals, respectively.

According to an embodiment, when the test option further includes a list of test scripts for each test scenario constituting each of one or more test scenarios, the matching unit 130 includes a list of test scripts constituting the test scenario selected by the user from the user. and matching information between the plurality of test target terminals selected by the user may be obtained.

Subsequently, in the corresponding embodiment, the matching unit 130 may match the plurality of test scripts acquired by the acquiring unit 120 with the plurality of test target terminals selected by the user, respectively, based on the acquired matching information.

According to an embodiment, the matching unit 130 may match the plurality of test scripts acquired by the acquiring unit 120 and the plurality of test target terminals selected by the user based on a preset matching criterion.

For example, the matching unit 130 may match a plurality of test scripts acquired by the acquiring unit 120 sequentially from a terminal with an earlier release date among a plurality of test target terminals selected by the user.

As another example, the matching unit 130 matches the plurality of test scripts acquired by the acquiring unit 120 in the order of the terminals belonging to the smart phone, tablet PC, and others among the plurality of test target terminals selected by the user. can do.

Also, as another example, the matching unit 130 may randomly match each of the plurality of test target terminals selected by the user and each of the plurality of test scripts acquired by the acquiring unit 120 .

According to an embodiment, the matching unit 130 may match at least one test script to each of the plurality of test target terminals selected by the user. Accordingly, the matching unit 130 can prevent the occurrence of terminals to which the test script is not applied among the test target terminals selected by the user.

Meanwhile, according to an embodiment, the matching unit 130 may match each of the plurality of test scripts acquired by the acquiring unit 120 so that the plurality of test scripts are not duplicately applied to the plurality of test target terminals selected by the user. Accordingly, the matching unit 130 may prevent unnecessary time required for performing the entire test scenario by applying one test script to two or more terminals.

According to an embodiment, the matching unit 130 divides and stores the plurality of test scripts acquired by the acquiring unit 120 in a pre-created folder corresponding to each of the plurality of test target terminals selected by the user, thereby corresponding to a specific folder. It is possible to match the test target terminal to be tested and the test script stored in a specific folder.

For example, when the user selects three test target terminals X, Y, and Z, the 'folder X' corresponding to the terminal X and the terminal Y correspond to the storage space provided inside or outside the test automation service apparatus 100 A 'folder Y' and a 'folder Z' corresponding to the terminal Z may be created, and in this case, the matching unit 130 determines that the test script to be performed on the terminal X is in the 'folder X' and the test script to be performed on the terminal Y can be stored in 'folder Y', and the test script to be executed in terminal Z is stored in 'folder Z'.

The test request unit 140 transmits a test request to the server so that the matched test script is executed in each of the plurality of test target terminals selected by the user.

Through this, the user can reduce the time required to perform the entire test scenario by allowing the test scripts constituting one test scenario to be distributed and performed through several test target terminals.

3 is an exemplary diagram illustrating a test automation service screen according to an embodiment.

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

First, the 'test option editing page' is a graphic user interface (GUI) provided to a user through the test option providing unit 110, and includes 'name', 'description', 'test resource', and 'device'. , 'result recipient', 'auto run', etc.

A 'name' is an item that a user can arbitrarily input to distinguish a software test, and a 'description' is an item in which a user writes a comment about the software test.

On the other hand, the 'test resource' is an item that can select a file and test scenario to be used for performing a software test.

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 a user can select a desired test scenario.

In addition, in addition to the test script registered in the second server 2, the user can directly upload a desired test script to be applied to the test target terminal. A 'file selection' graphic object 305 is included to upload a test script stored in the storage space in the computing device of the .

The 'device' is an item through which the user can select a test target terminal from among the test candidate terminals 4 . For this purpose, the 'device' item includes a 'device selection' graphic object 306 .

The 'result recipient' is an item through which the user can designate a target to receive the test result. 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 during the test.

'Auto-run' refers to the check button that determines whether to automatically run and the elapsed time condition so that the software test is automatically performed without the user's intervention through the user's test option selection when a new build file is registered in the first server (1). An input field is provided.

On the other hand, the 'build registration page' is a GUI that provides the user with a list of build files synchronized with the first server 1, and lists related build files under the upper build set (build 1, build 2, etc.) (Build 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 in the first server 1 can log in to the 'build registration page' and register the build file, and after completing the registration, click the 'logout' graphic object 439 By doing so, you can log out of 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 written by a developer is implemented in the form of a software product executable in a computing device.

On the other hand, the 'test script management page' is a GUI that provides the user with a list of test scripts synchronized with the second server 2, and is currently using the 'test script management page' through the user information display 312 . Displays user information.

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

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

4 is an exemplary diagram for explaining a result of a test performed according to an embodiment.

As can be seen from the 'test result report page' described at the top of FIG. 4 , when a test is performed in a test target terminal according to an embodiment, the result of the performed test is transmitted to the test automation service device 100 wirelessly or by wire. It may be output in the form of a report page including a table through a connected display (not shown) or the screen of the test target terminal. However, the form in which the test result is provided is not limited thereto, and may be stored in a separate storage (not shown) without being visually output.

Items in column 1 of the table shown in FIG. 4 indicate which test script was performed in each test target terminal and which action occurred as the test script was executed.

Hereinafter, for convenience of description, each test script is referred to as a name defined in the 'test script name' item of FIG. 4 .

First, referring to the 'test script name' item in table 1 column shown in FIG. 4 and the 'terminal A', 'terminal B', and 'terminal C' items in columns 4 to 6 of the table, the test is performed on three test target terminals ( It can be seen that terminal A, terminal B, and terminal C) were performed, and the result of the action generated according to the execution of the test script for each terminal is displayed as 'Pass' or 'Skip'.

On the other hand, referring to the 'test area' item in the second column of the table and the 'tagged action' item in the third column of the table, it is possible to know which actions are tested by the actions performed on the test target terminal according to each test script.

In summary, specifically, three test scripts 'Test1_install_execution', 'Test_mail', and 'Test_NPC' were performed in terminal A, and 'Test2_install_execution', 'Test It can be seen that three test scripts called _strengthening' and 'Test_card replacement' were performed, and in terminal C, two test scripts called 'Test3_install_execution' and 'Test3_merchant' were performed.

Also, for example, as the test script 'Test_mail' was executed in terminal A, three actions such as 'send note', 'receive note', and 'delete note' occurred, and the results of the three actions were It can be seen that all are 'Pass'. On the other hand, as the test script 'Test2_install_execution' was executed in terminal B, two actions, 'game installation and execution' and 'CDN update' occurred, and the result of the action of 'CDN update' was You can see that it is 'Skip'.

The arrangement and combination of rows and columns in each table shown in FIG. 4 and the contents in each cell are exemplary, and according to the embodiment, the test results are provided to the user in various forms. It is obvious that it can be

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 above-described test automation service apparatus 100 .

First, the test automation service apparatus 100 provides a user with a test option including a list of one or more predefined test scenarios and a list of test target terminals connected to the server ( 510 ).

Thereafter, the test automation service apparatus 100 acquires a plurality of test scripts corresponding to the test scenario selected by the user from the list of one or more test scenarios based on the user's selection of the test option ( 520 ).

Thereafter, the test automation service apparatus 100 matches each of the plurality of test scripts and the plurality of test target terminals selected by the user from the list of test target terminals ( 530 ).

Thereafter, the test automation service apparatus 100 transmits a test request to the server so that the matched test script is executed in each of the plurality of test target terminals selected by the user ( 540 ).

In the illustrated flowchart, the method is described by dividing the method into a plurality of operations, but at least some operations are performed in a different order, are performed in combination with other operations, are omitted, are performed separately, or are performed as detailed operations, or are not shown. One or more operations may be added and performed.

6 is a block diagram illustrating and describing a computing environment 10 including a computing device according to an embodiment. In the illustrated embodiment, each component may have different functions and capabilities other than those described below, and may include additional components in addition to 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 , computer readable storage medium 16 , and communication bus 18 . The processor 14 may cause the computing device 12 to operate in accordance with the exemplary embodiments discussed above. For example, the processor 14 may execute one or more programs stored in the computer-readable storage medium 16 . The one or more programs may include one or more computer-executable instructions that, when executed by the processor 14, configure the computing device 12 to perform operations in accordance with the exemplary embodiment. 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. The program 20 stored in the computer readable storage medium 16 includes a set of instructions executable by the 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 It may be memory devices, other forms of storage medium accessed by computing device 12 and capable of storing desired information, or a suitable combination thereof.

Communication 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 . The input/output interface 22 and the network communication interface 26 are coupled 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 device 24 may 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 imaging devices. 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 in the computing device 12 as a component constituting the computing device 12 , and may be connected to the computing device 12 as a separate device distinct from the computing device 12 . may be

Meanwhile, an embodiment 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 used in the field of computer software. Examples of computer-readable recording media include hard disks, magnetic media such as floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and program instructions specially configured to store and execute program instructions such as ROMs, RAMs, flash memories, etc. Hardware devices are included. Examples of the program may include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.

Although representative embodiments of the present invention have been described in detail above, those of ordinary skill in the art to which the present invention pertains will understand that various modifications are possible without departing from the scope of the present invention with respect to the above-described embodiments. . Therefore, the scope of the present invention should not be limited to the described embodiments, and should be defined by the following claims as well as the claims and equivalents.

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: input/output interface
24: input/output device
26: network communication interface
100: test automation service device
110: test option providing unit
120: acquisition unit
130: matching unit
140: test request unit

Claims (12)

providing a test option including a list of one or more predefined test scenarios and a list of test target terminals connected to the server to the user;
acquiring a plurality of test scripts corresponding to the test scenario selected by the user from the list of the one or more test scenarios based on the user's selection of the test option;
matching each of the plurality of test scripts and the plurality of test target terminals selected by the user from the list of the test target terminals; and
and transmitting a test request to the server so that a matched test script is executed in each of the plurality of test target terminals selected by the user. The method according to claim 1,
The test option is
Further comprising a list of test scripts for each test scenario constituting each of the one or more test scenarios,
The matching operation is
obtaining, from the user, matching information between a list of test scripts constituting the test scenario selected by the user and a plurality of test target terminals selected by the user; and
and matching each of the plurality of obtained test scripts and the plurality of test target terminals selected by the user based on the matching information. The method according to claim 1,
The matching operation is
A test automation service method for matching the plurality of obtained test scripts and the plurality of test target terminals selected by the user based on a preset matching criterion. The method according to claim 1,
The matching operation is
A test automation service method for matching at least one test script to each of the plurality of test target terminals selected by the user. The method according to claim 1,
The matching operation is
The test automation service method, wherein each of the acquired test scripts is matched so as not to be duplicately applied to the plurality of test target terminals selected by the user. The method according to claim 1,
The matching operation is
By dividing and storing the plurality of obtained test scripts in a folder that is previously created corresponding to each of the plurality of test target terminals selected by the user, the test target terminal corresponding to the specific folder and the test script stored in the specific folder are matched, Test automation service methods. one or more processors; and
an apparatus comprising a memory to store one or more programs configured to be executed by the one or more processors;
The program is
providing a test option including a list of one or more predefined test scenarios and a list of test target terminals connected to the server to the user;
acquiring a plurality of test scripts corresponding to the test scenario selected by the user from the list of the one or more test scenarios based on the user's selection of the test option;
matching each of the plurality of test scripts and the plurality of test target terminals selected by the user from the list of the test target terminals; and
and instructions for executing an operation of transmitting a test request to the server so that a matched test script is executed in each of the plurality of test target terminals selected by the user. 8. The method of claim 7,
The test option is
Further comprising a list of test scripts for each test scenario constituting each of the one or more test scenarios,
The matching operation is
further obtaining, from the user, matching information between a list of test scripts constituting the test scenario selected by the user and a plurality of test target terminals selected by the user; and
and matching each of the plurality of obtained test scripts and the plurality of test target terminals selected by the user based on the matching information. 8. The method of claim 7,
The matching operation is
A test automation service apparatus for matching the plurality of obtained test scripts and the plurality of test target terminals selected by the user based on a preset matching criterion. 8. The method of claim 7,
The matching operation is
A test automation service apparatus for matching at least one test script to each of the plurality of test target terminals selected by the user. 8. The method of claim 7,
The matching operation is
A test automation service apparatus that matches each of the obtained plurality of test scripts so as not to be applied to the plurality of test target terminals selected by the user in duplicate. 8. The method of claim 7,
The matching operation is
By dividing and storing the plurality of obtained test scripts in a folder that is previously created corresponding to each of the plurality of test target terminals selected by the user, the test target terminal corresponding to the specific folder and the test script stored in the specific folder are matched, Test automation service device.

Images