JP6781688B2 - Programs, information processing equipment and screen test systems - Google Patents

Description

The present invention relates to a program, an information processing device and a screen test system.

Tools for automating screen tests in system development have long been known. For example, in the testing of a graphical user interface (GUI) application, a test support device is used to record the user's operation, and the test support device reproduces and verifies the recorded operation to automatically execute the test, that is, to automate the test. (See, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2010-198479

Traditional tools that automate screen testing perform testing by running the application under test according to a set test scenario. For example, in the test scenario used in the screen test, the user operation on the screen of the application to be tested was set by the script. Therefore, there is a problem that knowledge of scripts is required to automate screen tests using conventional tools.

The above-mentioned Patent Document 1 describes the content of saving the operation of the test executor on the target application as a test script. However, in the content of Patent Document 1 described above, when an ID is not assigned to the object displayed on the screen to be tested, it is necessary to specify the object by the coordinates on the display, the window size, etc. There was a problem that the test scenario (test procedure) was not versatile and depended on.

An object of the present invention is to provide a program, an information processing apparatus, and a screen test system capable of creating a highly versatile test procedure and performing a screen test by the created test procedure.

In order to solve the above-mentioned problems, the program of claim 1 of the present application receives from the user an operation for instructing the computer to create a test procedure by designating an object displayed on the first screen to be tested. When the second identification information is not set for the object displayed on the first screen, the position information of the object displayed on the first screen is acquired, and the order determined by the position information is obtained. According to the setting step of assigning a number to the object and setting the numbered first identification information to the object, the first identification information or the second identification information is designated as the specific information of the object. A screen test is performed by the creation step of creating a test procedure for one or more objects from the operation contents for the object, the test procedure having the same structure as the first screen, and the test procedure created on the first screen. it displays a second screen of the test object can, if certain objects displayed on the second screen by the specifying information specified in the test procedure, the second identification information is the object deeds screen test before Symbol second screen in accordance with the test procedure that is specified as the specific information, said to be able to identify the object by the specific information, the setting step in the same manner as before Symbol displayed on the second screen is performed numbering objects are, the first identification information numbered set to the object, the first identification information is pre-Symbol second according to the test procedure that is specified as the specific information of the object It is characterized by being a program for executing an execution step of performing a screen test of the screen of.

According to the present invention, it is possible to create a highly versatile test procedure and to perform a screen test using the created test procedure.

It is a block diagram of an example of the screen test system which concerns on this embodiment. It is a hardware block diagram of an example of a computer. It is a software configuration diagram of an example of the screen test system which concerns on this embodiment. It is a flowchart of an example of the processing of the screen test system which concerns on this embodiment. It is explanatory drawing of an example of the test scenario setting process using an input assist tool. It is an image diagram of an example of a test target screen and a test scenario screen. It is an image diagram of an example of a test scenario screen when the ID of an object is not included in the information about an object. It is a flowchart of an example of a test scenario setting process using an input assist tool. It is explanatory drawing of an example of screen test execution processing and test result output processing. It is an image diagram of an example of a test scenario setting screen. It is an image diagram of an example of a login screen. It is an image diagram of an example of a search screen. It is an image diagram of an example of a search result screen. It is an image diagram of an example of the screen on which the test result report is displayed. It is a flowchart of an example of a screen test execution process and a test result output process.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[First Embodiment]
<System configuration>
FIG. 1 is a configuration diagram of an example of a screen test system according to the present embodiment. The screen test system according to the present embodiment may be configured by one information processing device 1 as shown in FIG. 1 (A), or may be configured by a plurality of information processing devices 2 as shown in FIG. 1 (B). And 3 may be configured. In the screen test system of FIG. 1B, the information processing device 2 functioning as a server device and the information processing device 3 functioning as a client device can perform data communication via a network 4 such as a local area network (LAN) or the Internet. It is connected.

The information processing device 1 of FIG. 1A is an example of a terminal device operated by a user who performs a screen test, and is a personal computer (PC), a smart device, a mobile phone, or the like. For example, the screen test system of FIG. 1A is downloaded to the information processing device 1 and used for a screen test of a client application executed by the information processing device 1 or a screen test of a Web application executed from a Web browser via a Web service. Applicable.

The information processing device 2 in FIG. 1B is an example of a server device that executes a Web application, and is a PC, a workstation, a mainframe, or the like. Further, the information processing device 3 is an example of a client device operated by a user who performs a screen test, and is a PC, a smart device, a mobile phone, or the like. The information processing device 3 is equipped with a Web browser, and operates a Web application from the Web browser via a Web service. For example, the screen test system of FIG. 1B can be applied to a screen test of a Web application and a screen test of a client application.

It should be noted that the screen test system of FIG. 1 is an example, and it goes without saying that there are various system configuration examples depending on the application and purpose. For example, in the screen test system of FIG. 1B, the information processing device 2 that functions as a server device is one example, but a plurality of information processing devices 2 may be used, and various configurations are possible.

<Hardware configuration>
The information processing devices 1, 2 and 3 of the screen test system of FIG. 1 are realized by, for example, the computer having the hardware configuration of FIG. FIG. 2 is a hardware configuration diagram of an example of a computer.

The computer 500 shown in FIG. 2 includes an input device 501, a display device 502, an external I / F 503, a RAM 504, a ROM 505, a CPU 506, a communication I / F 507, an HDD 508, and the like, and are connected to each other by a bus B. The input device 501 and the display device 502 may be connected and used when necessary.

The input device 501 is a keyboard, a mouse, a touch panel, or the like, and is used by a user or the like to input each operation signal. The display device 502 is a display or the like, and displays a processing result by the computer 500. The communication I / F 507 is an interface for connecting the computer 500 to the network 4. The HDD 508 is an example of a non-volatile storage device that stores programs and data.

The external I / F 503 is an interface with an external device. The computer 500 can read and / or write to a recording medium 503a such as an SD memory card via an external I / F 503. The ROM 505 is an example of a non-volatile semiconductor memory (storage device) in which programs and data are stored. RAM 504 is an example of a volatile semiconductor memory (storage device) that temporarily holds programs and data.

The CPU 506 is an arithmetic unit that realizes control and functions of the entire computer 500 by reading a program or data from a storage device such as a ROM 505 or an HDD 508 onto the RAM 504 and executing processing. The information processing devices 1, 2 and 3 of the screen test system of FIG. 1 can realize various functions as described later by, for example, the hardware configuration of the computer 500 of FIG.

<Software configuration>
Hereinafter, the software configuration in the case of the screen test system of FIG. 1A will be described as an example. The information processing device 1 of the screen test system of FIG. 1A is realized by, for example, the software configuration of FIG.

FIG. 3 is a software configuration diagram of an example of the screen test system according to the present embodiment. The information processing device 1 of FIG. 3 is equipped with an input assist tool 10, a test target application 12, and a screen test tool 14. The input assist tool 10 is a tool that assists in creating a test scenario necessary for executing a screen test as described later. The test target application 12 is a test target application that executes a screen test. The screen test tool 14 is a tool that performs a screen test of the test target application 12 according to a test scenario as described later. The software configuration shown in FIG. 3 is an example, for example, a configuration in which the input assist tool 10 and the screen test tool 14 are integrated, or a configuration in which the input assist tool 10 and the screen test tool 14 are subdivided. You may. The functional blocks realized by the input assist tool 10 and the screen test tool 14 will be described later.

<Processing>
The screen test system according to the present embodiment performs a screen test of the application to be tested by a procedure as shown in FIG. 4, for example. FIG. 4 is a flowchart of an example of processing of the screen test system according to the present embodiment.

In step S11, the user uses the input assist tool 10 to create a test scenario necessary for the screen test of the application to be tested 12. By capturing the screen to be tested (first screen), the input assist tool 10 can identify the object (screen item) displayed on the screen and set the test scenario as described later.

In step S12, the user instructs the screen test tool 14 to execute the screen test, and causes the screen test tool 14 to perform the screen test according to the test scenario created in step S11. The screen test tool 14 operates the screen (second screen) of the test target application 12 according to the test scenario as described later.

In step S13, the screen test tool 14 outputs the result of the screen test (test result image, test result report, etc.) to the test target application 12. The test scenario created in step S11 can be saved. When using the saved test scenario, the process of step S11 is omitted.

Note that the procedure of FIG. 4 is an example, and the user may manually input the test scenario represented in the tabular format instead of the test scenario setting process using the input assist tool 10 in step S11. In this case, manually input a predetermined ID described later, or manually input the ID output to the tool that outputs the order of the objects (screen items) displayed on the screen to be tested.

<< Details of step S11 >>
FIG. 5 is an explanatory diagram of an example of the test scenario setting process using the input assist tool. The input assist tool 10 of FIG. 5 has a configuration including a test target application designation unit 22, an object operation reception unit 24, an object information processing unit 26, and a test scenario output unit 28.

The test target application designation unit 22 specifies, for example, the screen of the test target application 12 (test target screen 1000) as shown in FIG. 6 (A). Further, the test scenario output unit 28 controls the display of the test scenario screen 1100 as shown in FIG. 6 (B). FIG. 6 is an image diagram of an example of the test target screen and the test scenario screen.

The object operation receiving unit 24 receives, for example, an operation (object operation) such as input to the input field displayed on the test target screen 1000 shown in FIG. 6A and click of a button from the user. The test target screen of FIG. 6A shows an example in which the user inputs "f000001" to the input field 1001 of "user ID:".

By capturing the test target screen 1000, the object information processing unit 26 acquires information about objects such as input fields and buttons displayed on the test target screen 1000. Information about the object includes the ID of the object, the type of the object, the position information of the object on the screen, the input value of the object, and the like. The object displayed on the test target screen 1000 may not have an ID assigned. In the case of an object for which an ID has not been assigned, the ID of the object is not included in the information about the object.

If the acquired information about the object does not include the ID of the object, the object information processing unit 26 determines the ID according to its own rule and assigns the ID to the object. The original rule used by the object information processing unit 26 is programming that describes the size of the screen, the type of the information processing device 1 that displays the screen, or the structure of the screen if the screen structure (object arrangement order, etc.) is the same. It is a rule that the same ID is determined regardless of the difference in language and the like. For example, in the original rule used by the object information processing unit 26, the ID is numbered so as to be a uniquely determined identifier. Further, in the original rule used by the object information processing unit 26, the ID may be numbered so as to be a serial number for each object type, or the ID may be numbered so as to be a total serial number. Further, in the original rule used by the object information processing unit 26, when a confusing ID is assigned to a plurality of objects, an identifier can be separately added to the end of the ID so as to distinguish them. The details of the original rule will be described later.

The test scenario output unit 28 displays a test scenario based on the object operation received by the object operation reception unit 24 on the test scenario screen 1100 as shown in FIG. 6B, for example. The test scenario screen 1100 of FIG. 6B is an example in which the object ID is included in the information about the object acquired by the object information processing unit 26.

In the test scenario shown on the test scenario screen 1100 of FIG. 6B, an operation of inputting the value "f000001" to the object to which the ID "loginUserId" is assigned is set.

On the other hand, when the information about the object acquired by the object information processing unit 26 does not include the object ID, the test scenario output unit 28 sets the test scenario based on the object operation received by the object operation reception unit 24, for example, FIG. 7 ( It is displayed on the test scenario screen 1200 as shown in B). FIG. 7 is an image diagram of an example of a test scenario screen when the ID of the object is not included in the information about the object.

In the information about the object of FIG. 7A, the values of the name attribute and the id attribute are not set. Therefore, the object information processing unit 26 determines the ID ".1" according to its own rule, and assigns the ID to the object. As a result, in the test scenario shown on the test scenario screen 1200 of FIG. 7B, the operation of inputting the value "f000001" to the object to which the ID ".1" is assigned is set.

FIG. 8 is a flowchart of an example of the test scenario setting process using the input assist tool. In step S31, for example, after inputting "f000001" in the input field 1001 of the test target screen 1000 shown in FIG. 6A, the user moves the mouse cursor to the position of the test scenario creation instruction (for example, the position of the input field 1001). Move and press the "Ctrl + Shift + z" key, etc.). The object operation reception unit 24 of the input assist tool 10 accepts an operation for instructing the creation of a test scenario in which an object is specified.

Proceeding to step S32, the object information processing unit 26 of the input assist tool 10 acquires information about the object (for example, the input field 1001) that has received the operation for the test scenario creation instruction. Proceeding to step S33, the object information processing unit 26 acquires an object type (Button, Text, etc.) from the information about the object, and determines an operation according to the object type and an input value of the object.

Proceeding to step S34, the object information processing unit 26 determines whether or not an ID is assigned (assigned) to the object that has received the operation for the test scenario creation instruction based on the information about the object acquired in step S32. To judge. If an ID is assigned to the object that has received the operation for the test scenario creation instruction, the test scenario output unit 28 proceeds to step S35, specifies the ID in the item ID column, and the operation and object determined in step S33. Specify the input value of in the operation column and value column. Then, the test scenario output unit 28 displays the test scenario screen 1100 shown in FIG. 6 (B).

If no ID is assigned to the object that has received the operation for creating the test scenario, the object information processing unit 26 proceeds to step S36, and the information and position regarding all the objects displayed on the screen of the test target application 12 are displayed. Get information (relative coordinates). Proceeding to step S37, the object information processing unit 26 determines the object to be numbered from the objects acquired in step S36. For example, the object information processing unit 26 may include an object having an ID in advance as a numbering target, or may delete the object from the numbering target.

For example, the object information processing unit 26 targets all objects, including objects having an ID in advance, for numbering. The object information processing unit 26 saves the advance ID of the object having an ID in the cache (temporary area) for saving in advance.

Proceeding to step S38, the object information processing unit 26 determines priorities in the order of, for example, the X-axis and the Y-axis, and performs numbering for each type of object to be numbered. After the numbering, the object information processing unit 26 adopts the ID saved in the cache (temporary area) for saving in advance for the object having the ID in advance.

For example, the object information processing unit 26 assigns ".1", ".2", and ".3" to the objects with IDs "None", "Login", and "None" in advance, and saves them in advance with the ID "Login". By applying ".1", ".1", "Login", and ".3" IDs can be adopted.

Further, the object information processing unit 26 may delete the object having an ID in advance from the numbering targets among the objects acquired in step S36. In this case, the object information processing unit 26 excludes the object with the ID "Login" from the numbering target in advance, and assigns ".1" and ".2" to the object with the ID "none" in advance to obtain ".1". "Login" ".2" ID can be adopted. Further, the object information processing unit 26 may provide both an ID column and an ID column numbered in step S38 in advance and treat them as different item IDs. In this case, the numbered ID can be used when the ID has changed in advance when the screen test is executed.

Proceeding to step S39, the test scenario output unit 28 designates the ID numbered in step S38 in the item ID column, and specifies the input value of the operation and the object determined in step S33 in the operation column and the value string. Then, the test scenario output unit 28 displays the test scenario screen 1200 shown in FIG. 7B. The user can set the test scenario by performing the test scenario setting process using the input assist tool of FIG. 8 one or more times.

<< Details of Steps S12 and S13 >>
FIG. 9 is an explanatory diagram of an example of the screen test execution process and the test result output process. The screen test tool 14 of FIG. 9 has a configuration including a test scenario setting reception unit 52, a test execution request processing unit 54, and a test result output unit 56.

The test scenario setting reception unit 52 controls the display of the test scenario setting screen 1300 as shown in FIG. 10, for example. FIG. 10 is an image diagram of an example of the test scenario setting screen. The test scenario setting reception unit 52 receives, for example, a test scenario setting operation on the test scenario setting screen 1300 of FIG. 10 from the user. The user can copy the test scenario displayed on the test scenario screen 1100 shown in FIG. 6B or the test scenario screen 1200 shown in FIG. 7B and paste it on the test scenario setting screen 1300. You may perform a test scenario setting operation.

The test execution request processing unit 54 receives an instruction for screen test execution from the user, such as pressing the test execution button 1302 on the test scenario setting screen 1300 of FIG. The test execution request processing unit 54 reads the data in the library 62 and generates a test code according to the test scenario. The test execution request processing unit 54 compiles the generated test code.

The test execution request processing unit 54 executes the compiled screen test module to perform a screen test according to the test scenario. The test result output unit 56 outputs the result of the screen test (test result image file 64, test result report 66, etc.) to the test target application 12.

The screen test performed by the test execution request processing unit 54 is assumed to be a test based on various test scenarios. Here, the user ID and password are input to the login screen, and the search conditions are input to the search screen. An example of checking the search result on the search result screen will be described.

FIG. 11 is an image diagram of an example of the login screen. FIG. 12 is an image diagram of an example of the search screen. FIG. 13 is an image diagram of an example of the search result screen. For example, the test execution request processing unit 54 performs a screen test based on the test scenario displayed in FIG. The test execution request processing unit 54 transitions to the search screen of FIG. 12 by inputting the user ID and password on the login screen of FIG. 11 and clicking the login button.

The test execution request processing unit 54 clicks the clear button on the search screen of FIG. 12, selects "2017/01" from the dropdown of the target month, inputs the name "1", inputs the search condition, and searches. By causing the test target application 12 to execute the search by clicking the button, the screen transitions to the search result screen shown in FIG.

The test execution request processing unit 54 verifies whether or not "100001" is included in the value of the search result item displayed on the search result screen of FIG. In the test scenario of FIG. 10, an example of "fuzzy verification" is shown as an example of verification items. The verification item is an example of information used for verifying whether or not the result of the screen test is correct.

When all the test scenarios are completed, the test result output unit 56 displays the test result report 66 as shown in FIG. 14, for example, on the screen. FIG. 14 is an image diagram of an example of a screen on which the test result report is displayed. In the test result report 66 of FIG. 14, the test result is displayed for each screen test. The test result report 66 shows where in the test scenario it failed. In addition, since the test scenario in this embodiment is in tabular format (for example, if the report at the time of failure says "9th line of the specification" (see Fig. 14), see the 9th line of the tabular test scenario. It has the advantage that it is easy to follow the failed part. The screen test of "Screen test B" in FIG. 14 shows an example when the result of the screen test is not correct, and the reason why it is not correct is described. Further, the test result report 66 of FIG. 14 is provided with a link 67 to a screen for displaying the test result image, and when the link 67 is clicked, the test result image file 64 is displayed. When the link 67 is clicked, the test result report 66 shows not only the test result image file 64 at the time of failure, but also the test result image file 64 at the time of success, or the test result image file 64 at the time of failure and success. May be displayed in a list.

Further, FIG. 15 is a flowchart of an example of the screen test execution process and the test result output process. In step S51, the test execution request processing unit 54 receives an instruction to execute the screen test from the user, such as pressing the test execution button 1302 on the test scenario setting screen 1300 of FIG.

Proceeding to step S52, the test execution request processing unit 54 determines whether or not the object displayed on the screen of the test target application 12 can be acquired using the item ID specified in the test scenario. If it cannot be acquired, the test execution request processing unit 54 determines that the value specified for the item ID of the test scenario is the number assigned by the input assist tool 10 (first identification information). Further, the test execution request processing unit 54 acquires information on all objects and their relative coordinates from the screen of the test target application 12. Proceeding to step S54, the test execution request processing unit 54 determines the object to be numbered from the objects acquired in step S53. For example, the object information processing unit 26 may include an object having an ID in advance as a numbering target, or may delete the object from the numbering target, as in step S37 of FIG.

Proceeding to step S55, the test execution request processing unit 54 determines priorities in the order of, for example, the X-axis and the Y-axis in the same manner as the numbering rule of the input assist tool 10, and performs numbering for each object type. Proceeding to step S56, the test execution request processing unit 54 uses the number (first) assigned in step S55 based on the value (first identification information or second identification information) specified in the item ID of the test scenario. Of the identification information), the ones having the same numbers are identified, and the process proceeds to step S57. If the object displayed on the screen of the test target application 12 can be specified by using the item ID specified in the test scenario in step S52, the test execution request processing unit 54 proceeds to step S57.

In step S57, the test execution request processing unit 54 performs an actual operation process (click, input, etc.) on the identified object by using the operation or verification and the value specified in the test scenario. Proceeding to step S58, the test result output unit 56 saves the test result image file 64 of the screen of the test target application 12. Proceeding to step S58, the test result output unit 56 determines whether or not the test scenario is completed. The processes of steps S52 to S59 are repeated until the test scenario is completed. When it is determined that the test scenario is completed, the test result output unit 56 proceeds to step S60 and outputs whether or not each operation or verification is correct, for example, as an HTML test result report 66.

As described above, according to the present embodiment, the screen size, the type of the information processing device 1 for displaying the screen, or the screen structure in the renovation of the application package, the repeated screen test in the migration project, the screen test comparing old and new, and the like. It is possible to create a highly versatile test scenario that does not depend on the difference in the programming language to be described, and to perform a screen test using that test scenario.

A migration project is a project for transferring software, systems, data, etc. to another environment or switching to a new environment. In many cases, the screen structure of a migration project is the same so that the user's operability does not change before and after the migration work.

Therefore, in migration projects, there are many cases where there is no change in the test scenario before and after the migration work, so create a test scenario on the screen before the migration work and use that test scenario in the screen test after the migration work. Available. As described above, this embodiment is particularly effective when the same screen test is repeated, such as in a migration project. In addition, since the test scenarios are displayed in a table format in this embodiment, the excellent effect that the test scenarios can be easily modified is also obtained.

[Other Embodiments]
In the first embodiment described above, an example in the case of the screen test system of FIG. 1 (A) has been described, but the screen test system of FIG. 1 (B) may be used.

The present invention is not limited to the above-described embodiments specifically disclosed, and various modifications and modifications can be made without departing from the scope of claims. It goes without saying that the screen test system described in this embodiment is an example, and there are various system configuration examples depending on the application and purpose. The "operation for instruction to create a test procedure" described in the claims corresponds to the "operation for instruction to create a test scenario" of the first embodiment, and the position of the input field 1001 exemplified in step S31. In addition to the operation of moving the mouse cursor to and pressing the "Ctrl + Shift + z" key, an operation (object operation) such as inputting to an input field or clicking a button may be performed.

1, 2, 3 Information processing device 4 Network 10 Input assist tool 12 Test target application 14 Screen test tool 22 Test target application specification unit 24 Object operation reception unit 26 Object information processing unit 28 Test scenario output unit 52 Test scenario setting reception unit 54 Test execution request processing unit 56 Test result output unit 62 Library 64 Test result image file 66 Test result report 1000 Test target screen 1100, 1200 Test scenario screen 1300 Test scenario setting screen 1302 Test execution button

Claims (9)

On the computer
A reception step that accepts from the user an operation for creating a test procedure that specifies the object displayed on the first screen to be tested.
When the second identification information is not set for the object displayed on the first screen, the position information of the object displayed on the first screen is acquired, and the order determined by the position information is obtained. A setting step in which the object is numbered according to the above and the numbered first identification information is set in the object.
A creation step of creating a test procedure for one or more objects for which the first identification information or the second identification information is designated as specific information for the object from the operation contents for the object.
A second screen to be tested, which has the same structure as the first screen and can be screen-tested by the test procedure created on the first screen, is displayed and designated by the test procedure. wherein if a particular object displayed in the second screen by the specific information, the second identification information screen test before Symbol second screen in accordance with the test procedure that is specified as the specific information of the object was carried out, to be able to identify the object by the specifying information, performs numbering to object displayed before Symbol second screen similarly to the setting step, the first identification information numbered objects execution step of setting, the first identification information is a screen test before Symbol second screen in accordance with the test procedure that is specified as the specific information of the object,
A program to execute. The creation step, when receiving an operation for pre-Symbol test procedure generation instruction specifying an object displayed on the first screen the user, the operation for the type of the object, and is input to the object The program according to claim 1, wherein the value is output as the operation content to assist the creation of a test procedure for the object. The creation step is characterized in that an operation according to the type of the object required for creating a test procedure for the object, and a value input to the object as the operation content are input or modified by a user in a tabular format. The program according to claim 2. The setting step displays the difference in size between the first and second screens and the first and second screens if the structure of the first screen is similar to the structure of the second screen. The feature is that the order determined by the position information is the same as the execution step regardless of the difference in the type of the computer or the difference in the programming language that describes the structure of the first and second screens. The program according to any one of claims 1 to 3. The setting before Symbol first screen the object is displayed to acquire the position information in step is a screen before the migration process, the screen before Symbol second screen testing in the executing step, The program according to any one of claims 1 to 4, wherein the screen is a screen after migration work. The program according to any one of claims 1 to 5, wherein the setting step can separately add an identifier to the end of the first identification information set in the object. The computer is further executed with an output step for outputting the result of the screen test, and the output step lists at least one screen data of success or failure of the test procedure represented in a tabular format. The program according to any one of claims 1 to 6, wherein the link is displayed on the result screen of the screen test. A reception means that accepts from the user an operation for instructing the creation of a test procedure that specifies the object displayed on the first screen to be tested, and
When the second identification information is not set for the object displayed on the first screen, the position information of the object displayed on the first screen is acquired, and the order determined by the position information is obtained. The object is numbered according to the above, and the numbered first identification information is set in the object.
A creating means for creating a test procedure for one or more objects in which the first identification information or the second identification information is designated as specific information for the object from the operation contents for the object.
A second screen to be tested, which has the same structure as the first screen and can be screen-tested by the test procedure created on the first screen, is displayed and designated by the test procedure. wherein if a particular object displayed in the second screen by the specific information, the second identification information screen test before Symbol second screen in accordance with the test procedure that is specified as the specific information of the object was carried out, to be able to identify the object by the specifying information, performs numbering the objects displayed in the same manner before Symbol second screen and the setting unit, wherein the first identification information numbered objects execution means for performing screen test before Symbol second screen in accordance with the test procedures set, the first identification information is specified as the specific information of the object,
Information processing device with. A screen test system with one or more information processing devices
A reception means that accepts from the user an operation for instructing the creation of a test procedure that specifies the object displayed on the first screen to be tested, and
When the second identification information is not set for the object displayed on the first screen, the position information of the object displayed on the first screen is acquired, and the order determined by the position information is obtained. The object is numbered according to the above, and the numbered first identification information is set in the object.
A creating means for creating a test procedure for one or more objects in which the first identification information or the second identification information is designated as specific information for the object from the operation contents for the object.
A second screen to be tested, which has the same structure as the first screen and can be screen-tested by the test procedure created on the first screen, is displayed and designated by the test procedure. wherein if a particular object displayed in the second screen by the specific information, the second identification information screen test before Symbol second screen in accordance with the test procedure that is specified as the specific information of the object was carried out, to be able to identify the object by the specifying information, performs numbering the objects displayed in the same manner before Symbol second screen and the setting unit, wherein the first identification information numbered objects execution means for performing screen test before Symbol second screen in accordance with the test procedures set, the first identification information is specified as the specific information of the object,
Screen test system with.

Images