Automatic screen operation test support device, and automatic screen operation test support method

Abstract

To provide an automatic screen operation test support device capable of extracting problematic defect differences without manual labor in an automatic screen operation test of the screen system, and an automatic screen operation test support method.SOLUTION: The automatic screen operation test support device executes a series of non-defective list creation processing in which the automatic screen operation test is executed multiple times on the same screen system and the resulting capture screen differences are recorded in the non-defective difference information table. The automatic screen operation test support device executes a series of defective difference check processing in which an automatic screen operation test is executed on the comparison reference screen system and the comparison target screen system to identify defective differences by removing the non-defective differences from the captured screen differences.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an automatic screen operation test support device and an automatic screen operation test support method. [Background technology]

[0002] One method of automated program testing is to compare images of the program execution results, extract differences, and identify defects (automated screen operation testing).

[0003] One example of the application of the automatic screen operation test is to execute a script that automatically executes a scenario showing the same operation content under the same conditions on a screen system before enhancement and a screen system after enhancement. Then, by comparing all the captures (bitmap data) saved at each point between each operation of the scenario on the screen systems before enhancement and after enhancement, it is checked whether any differences have occurred, identifies the points where differences have occurred, and outputs information indicating the identified differences, thereby providing the information indicating the differences to the user.

[0004] Differences that can be confirmed in an automated screen operation test can be roughly divided into defective differences that cause problems if they occur, and non-defective differences that do not cause problems if they occur. However, conventional automated screen operation tests take a large number of captures (bitmap data) at many points between each operation for each scenario, and output information indicating the identified difference each time a difference is identified without distinguishing between these two types of differences, which results in an enormous amount of work to confirm the large number of differences.

[0005] [Prior art 1] Therefore, in one example of the prior art (referred to as "Prior Art 1"), before conducting an automatic screen operation test, the user manually specifies in advance where no problematic changes will occur by covering them with a blue frame, and then performs the automatic screen operation test while excluding the specified locations from the difference comparison targets. In this way, Prior Art 1 can reduce the number of difference comparison targets.

[0006] [Prior art 2] The technology of Patent Document 1 (JP 2020-52861 A) (hereinafter referred to as "Prior Art 2") acquires a first-mode result image, which is an image of a result screen output as an execution result of a first program executed under first execution conditions. Prior Art 2 acquires a second-mode result image, which is an image of a result screen output as an execution result of a second program executed under second execution conditions. Prior Art 2 compares the first-mode result image with the second-mode result image to detect differences. A control unit of Prior Art 2 identifies candidate areas, which are candidates for areas that do not require verification in a verification test, from the detected differences based on predetermined rules. Prior Art 2 displays a third-mode result image, in which candidate areas can be identified, on a display unit and accepts the setting of a verification-free area, which is an area that does not require verification in a verification test. The user visually checks the third-mode result image displayed on the display unit and sets the verification-free area. This enables Prior Art 2 to easily set verification-free areas for performing program verification tests.

[0007] [Prior art 3] The technology of Patent Document 2 (JP 2001-282578 A) (hereinafter referred to as "Prior Art 3") records test operation procedures for a program under test and the output results of the program under test for those procedures. Prior Art 3 plays back the recorded test operation procedures for the same program under test, calculates the difference between the output results and the recorded output results, and sets this as comparison exclusion data. Prior Art 3, after amending the program under test, plays back the recorded test operation procedures for the revised program under test, calculates the difference between the output results and the recorded output results, and outputs the differences that do not exist in the comparison exclusion data as true differences. In this way, Prior Art 3 automatically sets parts to be excluded from comparison, eliminating setting omissions and effort, and enabling program testing by making it easy to understand that the displayed differences in the comparison are due to defects rather than due to the specifications of the program under test. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] Japanese Patent Publication No. 2020-52861 [Patent Document 2] Japanese Patent Application Laid-Open No. 2001-282578 Summary of the Invention [Problem to be solved by the invention]

[0009] In conventional technique 1, it is necessary to manually specify the locations where non-problematic changes occur, which results in a large amount of manual work.In conventional technique 1, differences in the specified locations are not detected, so if a problematic defect occurs within the specified location, there is a problem that the problematic defect may go unnoticed and be overlooked.

[0010] Conventional technique 2 also has the problem that the user must manually set the verification-free area, which is an area that does not require verification. Furthermore, conventional technique 2 sets a fixed verification-free area and does not detect differences in the verification-free area, so it is not possible to extract problematic defective differences that occur in the verification-free area.

[0011] Prior art 3 sets the difference (non-problematic difference) that occurs by a single comparison of the output result of the program under test before revision as comparison exclusion data. However, there are also non-problematic differences that do not appear by a single comparison of the output result (for example, differences caused by blinking), and it is possible that non-problematic differences will not be set as comparison exclusion data.

[0012] Therefore, one object of the present invention is to provide an automatic screen operation test support device and an automatic screen operation test support method that can extract problematic defective differences without requiring manual work in automatic screen operation tests of a screen system. [Means for solving the problem]

[0013] In order to solve the above-mentioned problems, the automatic screen operation test support device of the present invention is an automatic screen operation test support device including an information processing device having a storage device in which non-faulty difference list data and difference information list data are stored, wherein the information processing device executes a first automatic screen operation test a plurality of times to extract differences that have occurred in the first comparison target screen relative to the first comparison reference screen by comparing a first comparison reference screen and a first comparison target screen, which are obtained by performing automatic screen operations of operation contents indicated by a specific scenario on each of the same screen systems for non-faulty difference registration that are a comparison reference and a comparison target, and executes a non-faulty list creation process to distinguish the extracted differences and record them in the non-faulty difference list data as non-faulty differences, and and a second automatic screen operation test is executed for each of the screen systems that are the target of defect extraction, to compare a second comparison reference screen and a second comparison target screen obtained by performing an automatic screen operation of an operation content indicated by a scenario identical to the specific scenario, thereby extracting differences that have occurred in the second comparison target screen from the second comparison reference screen, to determine the extracted differences and record them in the difference information list data, and to execute a defect difference check process that identifies, based on the difference information list data and the non-defective difference list data, the differences that are identical to the non-defective differences recorded in the non-defective difference list data in the difference information list data as non-defective differences, and to identify the differences other than the non-defective differences identified from the difference information list data as defective differences.

[0014] The automatic screen operation test support method of the present invention is an automatic screen operation test support method using an information processing device having a storage device in which non-fault difference list data and difference information list data are stored, and the information processing device compares a first comparison reference screen and a first comparison target screen, which are obtained by performing automatic screen operations of operation contents indicated by a specific scenario on each of the same screen systems for non-fault difference registration of a comparison reference and a comparison target, to execute a first automatic screen operation test multiple times to extract differences that have occurred in the first comparison target screen relative to the first comparison reference screen, and executes a non-fault list creation process to distinguish the extracted differences and record them in the non-fault difference list data as non-fault differences, and For each of the screen systems that are the target of defect extraction, a second automatic screen operation test is executed to compare a second comparison reference screen obtained by performing an automatic screen operation of the operation content indicated by a scenario identical to the specific scenario with a second comparison target screen, thereby extracting differences that have occurred in the second comparison target screen relative to the second comparison reference screen, and the extracted differences are determined and recorded in the difference information list data. Based on the difference information list data and the non-defective difference list data, differences in the difference information list data that are identical to the non-defective differences recorded in the non-defective difference list data are identified as non-defective differences, and a defective difference check process is executed to identify differences other than the non-defective differences identified from the difference information list data as defective differences. [Effects of the Invention]

[0015] According to the present invention, in an automatic screen operation test of a screen system, problematic defective differences can be extracted without requiring manual labor. Note that the effects described herein are not necessarily limited to those described herein, and may be any of the effects described in this disclosure. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a schematic diagram showing an example of the configuration of an automatic screen operation test support device according to a first embodiment of the present invention. [Figure 2] FIG. 2 is a diagram for explaining the screen information table. [Figure 3] FIG. 3 is a diagram for explaining the non-bad difference information table. [Figure 4] FIG. 4 is a diagram for explaining the difference information table. [Figure 5] Figure 5 shows an example of a captured screen where a difference occurs at a certain point in a scenario. [Figure 6] Figure 6 shows an example of a captured screen where a difference occurs at a certain point in a scenario. [Figure 7A] FIG. 7A is a diagram for explaining the prior art and the problems involved. [Figure 7B] FIG. 7B is a diagram for explaining the conventional technology and the problems. [Figure 8A] FIG. 8A is a diagram for explaining an outline of the non-bad list creation process. [Figure 8B] FIG. 8B is a diagram for explaining an outline of the non-bad list creation process. [Figure 8C] FIG. 8C is a diagram for explaining an outline of the non-bad list creation process. [Figure 8D] FIG. 8D is a diagram for explaining an outline of the non-bad list creation process. [Figure 9A] FIG. 9A is a diagram for explaining a specific example of the non-bad list creation process. [Figure 9B] FIG. 9B is a diagram for explaining a specific example of the non-bad list creation process. [Figure 9C] FIG. 9C is a diagram for explaining a specific example of the non-bad list creation process. [Figure 9D] FIG. 9D is a diagram for explaining a specific example of the non-bad list creation process. [Figure 10A] FIG. 10A is a diagram for explaining an outline of the defect difference check process. [Figure 10B] FIG. 10B is a diagram for explaining an outline of the defect difference check process. [Figure 10C] FIG. 10C is a diagram for explaining an outline of the defect difference check process. [Figure 11] FIG. 11 is a flowchart showing the process flow of the non-bad list creation process executed by the non-bad list creation unit. [Figure 12] FIG. 12 is a flowchart showing the process flow of the difference information discrimination and DB registration process executed by the non-bad list creation unit. [Figure 13] FIG. 13 is a flowchart showing the processing flow of the defect difference check process executed by the defect difference check unit. [Figure 14] FIG. 14 is a flowchart showing the process flow of the difference information determination process executed by the defect difference check unit. [Figure 15] FIG. 15 shows the user confirmation screen. [Figure 16] FIG. 16 is a diagram showing the defect difference display screen after the defect difference check processing. [Figure 17] FIG. 17 shows a comparison screen including a capture screen in which a difference has occurred. [Figure 18] FIG. 18 is a diagram showing the defect difference display screen after the narrowing down release button is operated on the defect difference display screen of FIG. [Figure 19] FIG. 19 is a diagram for explaining the non-bad difference information table. [Figure 20] FIG. 20 is a diagram showing a part of the threshold number setting screen. [Figure 21] FIG. 21 is a flowchart showing the process flow of the non-bad list creation process executed by the non-bad list creation unit. [Figure 22] FIG. 22 shows the user confirmation screen. [Figure 23] FIG. 23 is a diagram showing a portion of the allowable coordinate setting screen. [Figure 24] FIG. 24 is a diagram showing an example of a non-bad difference information table. [Figure 25] FIG. 25 is a diagram showing an example of a difference information table. [Figure 26] FIG. 26 is a flowchart showing the processing flow of the defect difference check process executed by the defect difference check unit. [Figure 27A]FIG. 27A is a diagram showing a defect difference display screen after the defect difference check. [Figure 27B] FIG. 27B is a diagram showing the defect difference display screen. [Figure 28] FIG. 28 is a diagram for explaining the difference information table. [Figure 29] FIG. 29 is a diagram for explaining the importance table. [Figure 30] FIG. 30 shows the importance setting screen. [Figure 31] FIG. 31 is a flowchart showing the processing flow of the defect difference check process. [Figure 32] FIG. 32 shows the defect difference display screen after the defect difference check. [Figure 33] FIG. 33 is a diagram for explaining the criteria table. [Figure 34] FIG. 34 is a diagram for explaining the judgment criteria input screen. [Figure 35] FIG. 35 is a flowchart showing the process flow of the difference information discrimination and DB registration process executed by the non-failure list creation unit 111a. [Figure 36] FIG. 36 is a diagram for explaining a non-bad difference determination definition table. [Figure 37] FIG. 37 is a flowchart showing the processing flow of the defect difference check process executed by the defect difference check unit. DETAILED DESCRIPTION OF THE INVENTION

[0017] Hereinafter, each embodiment of the present invention will be described with reference to the drawings. In all the drawings of the embodiments, the same or corresponding parts may be denoted by the same reference numerals.

[0018] In the following explanation, various information may be described using expressions such as "table," "record," "column," "row," and "list," but the various information may be expressed using data structures other than these. When describing identification information, expressions such as "ID," "identification number," and "name" are used, but these are interchangeable.

[0019] In the following explanation, processing may be described using functional blocks as the subject, but the subject of processing may also be a CPU or device instead of a functional block. The subject of processing performed by executing a program may be a computing unit, and may include a dedicated circuit that performs specific processing. Here, the dedicated circuit may be, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a CPLD (Complex Programmable Logic Device).

[0020] In the following description, a program may be installed on a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in each embodiment, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0021] <<First Embodiment>> An automatic screen operation test support device 100 (see FIG. 1) according to a first embodiment of the present invention will be described. In this example, the automatic screen operation test support device 100 is applied to an EC (Electronic Commerce) product order screen system (hereinafter referred to as a "screen system"). Application examples are not limited to EC product order screen systems, and the automatic screen operation test support device 100 can be applied to various other screen systems.

[0022] In the following description, automatic screen operation, automatic screen operation test (screen saving), and automatic screen operation test (screen comparison) refer to the following operations and tests.

[0023] Automatic screen operation: Executing a script to automatically execute a scenario showing the operation content on the screen system.

[0024] Automatic screen operation test (screen saving): Performing automatic screen operations on the screen system and capturing the screen at points (also called "steps") between each operation performed in the scenario, thereby obtaining and saving the captured screen (bitmap data).

[0025] Automated screen operation test (screen comparison): Using the captured screens saved by the automated screen operation test (screen saving) for the comparison reference screen system and the comparison target screen system, the captured screens of the same steps for the comparison reference screen system and the comparison target screen system are compared, and differences that have occurred in the captured screen of the comparison target screen system relative to the captured screen of the comparison reference screen system are extracted.

[0026] The automatic screen operation test (screen saving) and the automatic screen operation test (screen comparison) are collectively referred to as the "automatic screen operation test."

[0027] FIG. 1 is a schematic diagram showing an example of the configuration of an automatic screen operation test support device 100 according to a first embodiment of the present invention. As shown in FIG. 1, the automatic screen operation test support device 100 includes a non-volatile storage device 110 that can read and write data, a memory 120 (e.g., RAM), a CPU 130, an input / output interface 140, a network interface 150, and a display 160. For convenience, the device including the CPU 130, the storage device 110, the memory 120, the input / output interface 140, the network interface 150, and the bus 170 is also referred to as an "information processing device." The information processing device may be a plurality of information processing devices or a virtual information processing device built on a cloud.

[0028] The storage device 110 holds (stores, stores) a program 111 and a database 112 .

[0029] The CPU 130 loads the program 111 stored in the storage device 110 into the memory 120. The CPU 130 executes the program 111 loaded into the memory 120, thereby realizing various functions of the automatic screen operation test support device 100.

[0030] The program 111 includes a non-defective list creation unit 111a and a defective difference check unit 111b. The non-defective list creation unit 111a performs an automatic screen operation test multiple times using the screen system for which the non-defective difference information table 114 is created as a comparison reference screen system and a comparison target screen system, and registers (stores, updates) information about the resulting differences in the non-defective difference information table 114. This process is referred to as the "non-defective list creation process." The non-defective difference information table 114 may be referred to as "non-defective difference list data." The automatic screen operation test performed by the non-defective list creation unit 111a may be referred to as the "first automatic screen operation test."

[0031] The defective difference check unit 111b performs an automatic screen operation test once, using the pre-enhancement screen system as a comparison reference screen system and the post-enhancement screen system as a comparison target screen system, and registers (stores, updates) information about the differences in the difference information table 115 based on the results. This process is referred to as a "defective difference check process." The difference information table 115 may be referred to as "difference information list data." The "automatic screen operation test" performed by the defective difference check unit 111b may be referred to as a "second automatic screen operation test." Details of the processes performed by the non-defective list creation unit 111a and the defective difference check unit 111b will be described later.

[0032] The database 112 includes a screen information table 113, a non-bad difference information table 114, and a difference information table 115. Details of these pieces of information will be described later.

[0033] As described above, the program 111 executed by the CPU 130 is loaded into the memory 120, and data used when the CPU 130 executes the program 111 is temporarily stored therein.

[0034] The input / output interface 140 is an interface for connecting operation devices (operation devices) such as a keyboard and a mouse, and a display 160 capable of displaying images. The network interface 150 is an interface for connecting the automatic screen operation test support device 100 to a network NW1 such as the Internet. The display 160 may not be included in the automatic screen operation test support device 100, and may be located outside the automatic screen operation test support device 100. For convenience, the display 160 may also be referred to as a "display device." The display 160 may be a touch panel having the functions of displaying images and operating a device.

[0035] FIG. 2 is a diagram illustrating the screen information table 113. As shown in FIG. 2, the screen information table 113 includes a screen ID 113a, a scenario ID 113b, and a step number 113c as columns for storing information (values). In the screen information table 113, information corresponding to each column regarding a captured screen acquired by the automatic screen operation test (screen saving) is associated with each other and stored as row-based information (records). Specifically, the screen ID 113a stores a screen information ID (identification number) for identifying the captured screen. The scenario ID 113b stores an identification number for identifying the scenario from which the captured screen was acquired. The step number 113c stores an identification number for identifying the point (step) at which the captured screen was acquired.

[0036] Fig. 3 is a diagram illustrating the non-bad difference information table 114. As shown in Fig. 3, the non-bad difference information table 114 includes, as columns for storing information (values), an ID 114a, a screen information ID 114b, coordinate information 114c, a content type 114d, a difference type 114e, a difference content ID 114f, an original content 114g, an execution content 114h, and an occurrence count 114i.

[0037] In the non-fault difference information table 114, information corresponding to each column regarding differences generated by the automatic screen operation test (difference comparison) of the non-fault list creation process is associated with each other and stored as row-by-row information (records).

[0038] Specifically, ID 114a stores an identification number for identifying the non-fault difference information indicated by a row (record) of this table. The non-fault difference information is information about differences that have occurred as a result of multiple automatic screen operation tests executed by the non-fault list creation unit 111a. Note that one row (record) is "non-fault difference information" that indicates one non-fault difference.

[0039] The screen information ID 114b stores a screen information ID, which is an identification number for identifying a captured screen in which a difference has occurred. The coordinate information 114c stores coordinates indicating the position in the captured screen in which a difference has occurred. The content type 114d stores the content type of the difference. The content type refers to the type of content of the difference, such as date, image, and character string. The difference type 114e stores the type of difference. The difference type refers to the type of difference, such as size, background color, character color, language, font, content, coordinates, and format.

[0040] The difference content ID 114f stores an identification number for identifying the difference content (original content and execution content). The same identification number is assigned to difference content at the same position. The original content 114g stores the content of the image area in the comparison reference capture screen where a difference has occurred with respect to the comparison target capture screen. The execution content 114h stores the content of the image area in the comparison target capture screen where a difference has occurred with respect to the comparison reference capture screen. The number of occurrences 114i stores the number of times the same difference has occurred as a result of multiple repetitions of the automatic screen operation test in the non-fault list creation process.

[0041] The coordinates indicating the position where the difference occurred, the content type of the difference, and the difference type may be referred to as "difference attribute information" or "difference attribute." Information including difference identification information (identification number), difference attribute information, and information indicating the content of the difference is referred to as "difference information." Of the difference information, difference information indicating a non-bad difference is referred to as "non-bad difference information."

[0042] Fig. 4 is a diagram illustrating difference information table 115. As shown in Fig. 4, difference information table 115 includes, as columns for storing information (values), ID 115a, screen information ID 115b, coordinate information 115c, content type 115d, difference type 115e, original content 115f, runtime content 115g, non-fault difference information ID 115h, and fault 115i.

[0043] In the difference information table 115, information corresponding to each column regarding differences that occur as a result of executing an automatic screen operation test in the defective difference check process is associated with each other and stored as information (records) in row units.

[0044] Specifically, ID 115a stores an identification number for identifying the difference information indicated by a row (record) of this table. The difference information is information regarding the difference generated by one automatic screen operation test executed in the defective difference check process. Note that one row (record) is "difference information" indicating one difference. Screen information ID 115b stores an identification number for identifying the capture screen. Coordinate information 115c stores coordinate values ​​indicating the position in the capture screen where the difference occurred. Content type 115d stores the type of content of the difference. Difference type 115e stores the type of difference. Original content 115f stores the content of an image area in the comparison reference capture screen where a difference occurred from the comparison target capture screen. Execution content 115g stores the content of an image area in the comparison target capture screen where a difference occurred from the comparison reference capture screen. Non-defective difference information ID 115h stores the ID (identification number) of non-defective difference information for the same non-defective difference as the difference generated by one automatic screen operation test. The failure 115i stores information ("0" or "1") indicating whether the difference is failure or not. When the value of the failure 115i is "0", it indicates that the difference is a non-failure difference (i.e., not a failure difference), and when the value of the failure 115i is "1", it indicates that the difference is a failure difference.

[0045] <Summary> An outline of the present invention will be described.

[0046] (Prior art and issues) First, in order to facilitate understanding of the present invention, the prior art and problems will be described in detail.

[0047] An example of an automatic screen operation test is performed when a display system is enhanced (improved) in order to identify differences caused by the enhancement. The automatic screen operation test is performed on the display system before the enhancement and the display system after the enhancement, and differences occurring between the captured screen of the display system before the enhancement and the captured screen of the display system after the enhancement are extracted.

[0048] Differences that arise from automated screen operation tests can be broadly divided into non-defective differences, which do not cause problems if they occur, and defective differences, which cause problems if they occur. Figures 5 and 6 show examples of captured screens where differences occurred at certain points in a scenario. Figure 5 is a captured screen of the screen system before enhancement, and Figure 6 is a captured screen of the screen system after enhancement. In Figure 6, the differences surrounded by dashed line R1 are non-defective differences, and the differences surrounded by dashed line R2 are defective differences. In this example, the non-defective differences are non-defective difference 1 (purchase date and time), non-defective difference 2 (delivery date), and non-defective difference 3 (illustration), all surrounded by dashed line R1. The defective difference is defective difference 1 (price of product C), surrounded by dashed line R2.

[0049] Non-defective difference 1 (purchase date and time) is a non-problematic difference (non-defective difference) because, if the program operates normally, the purchase date and time is entered in this field, and it can be determined that this was caused by a difference in the execution date and time of the scenario. Non-defective difference 2 (delivery date) is a non-problematic difference (non-defective difference) because, if the program operates normally, the delivery date corresponding to the purchase date and time is entered in this field, and it can be determined that this was caused by a difference in the execution date and time of the scenario. Non-defective difference 3 (illustration) is a non-problematic difference (non-defective difference) because, if the program operates normally, an illustration to be displayed is randomly selected from multiple illustrations and displayed when the order is completed.

[0050] On the other hand, defective difference 1 (price of product C) is a problematic difference (defective difference) because a difference in the price of product C occurred despite the execution of the same scenario (a scenario including operations to purchase the same quantity of the same product). This can be determined to be due not to normal program operation but to abnormal program operation caused by an enhancement to the screen system.

[0051] Conventional automatic screen operation test support devices take a large number of screen captures at a large number of points between each operation for each scenario, and output information indicating the identified difference each time a difference is identified without distinguishing between these two types of differences, resulting in an enormous amount of work to check the large number of differences.

[0052] Therefore, as shown in Figure 7A, conventional automatic screen operation test support devices have reduced the number of areas to be compared for difference by manually covering the areas where changes occur due to normal program operation (areas indicated by arrows a1 to a3) with frames filled in a specific color (e.g., blue) indicated by hatching. However, conventional automatic screen operation test support devices have the following two problems. Namely, the manual setting of the difference comparison exclusion area is time-consuming. Because the difference comparison exclusion area does not detect the differences themselves, as shown in Figure 7B, when a problematic difference (bad difference) occurs in the difference comparison exclusion area (area indicated by arrow a4), it may not be detected and the bad difference may be overlooked.

[0053] Furthermore, in conventional automatic screen operation test support devices such as [Prior Art 3] described in [Background Art], as described in [Problem to be Solved by the Invention], it may happen that differences that are not problematic and do not appear when comparing only one output result (for example, differences caused by blinking) are not set as comparison exclusion data.

[0054] (Summary of the Invention) In order to solve the above problems, the automatic screen operation test support device 100 according to the first embodiment of the present invention executes a non-fault list creation process using a non-fault list creation unit 111a. The non-fault list creation unit 111a executes an automatic screen operation test multiple times using the same scenario and the same screen system as a comparison reference screen system and a comparison target screen system, determines the attributes and contents of the differences that result, and registers information about the determined differences (difference information) in a non-fault difference information table 114 as non-fault difference information.

[0055] After executing the non-fault list creation process, the automatic screen operation test support device 100 causes the faulty difference check unit 111b to execute the faulty difference check process. The faulty difference check unit 111b determines the attributes and contents of the differences that have occurred as a result of executing one automatic screen operation test using the same scenario, with the pre-enhancement screen system as the comparison reference screen system and the post-enhancement screen system as the comparison target screen system, and registers information about the determined differences as difference information in the difference information table 115.

[0056] Based on the difference information table 115 and the non-faulty difference information table 114, the faulty difference check unit 111b identifies a non-faulty difference from one or more differences indicated by the difference information table 115, and extracts (identifies) the remaining difference as a faulty difference by removing the identified non-faulty difference from the one or more differences indicated by the difference information table 115.

[0057] As described above, the automatic screen operation test support device 100 can extract (identify) problematic defective differences without requiring manual labor. Furthermore, in the non-fault list creation process, the automatic screen operation test support device 100 looks at the differences in all image areas and does not set fixed areas that do not require verification, as in conventional technology. This reduces the possibility that a problematic difference (defective difference) will be overlooked if it occurs in an area excluded from difference comparison. Furthermore, in the non-fault list creation process, the automatic screen operation test support device 100 registers differences that occur by performing multiple automatic screen operation tests as non-faultive differences, so that non-problematic differences that do not appear in a single comparison of output results (for example, differences caused by blinking) can be registered as non-faultive differences.

[0058] (Non-bad list creation process) An overview of the non-fault list creation process will be described. The non-fault list creation unit 111a first performs an automatic screen operation test (screen storage) on a comparison reference screen system (in this example, the screen system before enhancement). Specifically, the non-fault list creation unit 111a executes a script that executes a scenario on the target screen system (in this example, the screen system before enhancement), thereby performing automatic screen operation.

[0059] An example of a scenario is composed of, for example, the following operations 1 to 26. Operation 1: Enter the user ID (user A) on the login screen (login screen shown in FIG. 8A). Operation 2: Enter the password (***). Operation 3: Press the "Login" button. Transition to the shopping screen (shopping screen shown in FIG. 8B). Operation 4: Enter "product A" as the keyword. Operation 5: Press the "Search" button. Operation 6: Display the lower screen while scrolling. Operation 7: Press the "Add to cart" button for the target product. Operations 8 to 23: Repeat operations 4 to 7 as many times as the number of products to be purchased (product B twice, product C, product D). Operation 24: Press the "View cart" button. Operation 25: Transition to the purchase confirmation screen (purchase confirmation screen shown in FIG. 8C). Operation 25: Press the "Confirm purchase" button. Transition to the purchase details screen (purchase details screen shown in FIG. 8D). Operation 26: Press the "Close x" button. In this example, step 1 to step 25 are assigned to the points (steps) between the operations as names (step numbers) for identifying these points (steps).

[0060] The non-failure list creation unit 111a holds (stores, memorizes) in the storage device 110 a plurality of capture screens captured at each point (step) of the scenario. For ease of explanation, each of these plurality of capture screens may be referred to as a "comparison reference screen" or a "first comparison reference screen." FIG. 9A shows a comparison reference screen GM90, which is an example of one comparison reference screen. The comparison reference screen GM90 is a capture screen captured at a point (step 25) between operations 25 and 26.

[0061] The non-faulty list creation unit 111a performs an automatic screen operation test (screen saving) on ​​a comparison target screen system (the same pre-enhancement screen system as above). Specifically, the non-faulty list creation unit 111a executes the same scenario and obtains capture screens captured at each step of the scenario. For ease of explanation, each of these multiple capture screens may be referred to as a "comparison target screen" or a "first comparison target screen." FIG. 9B shows a comparison target screen GM91, which is an example of one comparison target screen. Like the comparison reference screen 90, the comparison target screen GM91 is also a capture screen captured at a point (step 25) between operation 25 and operation 26.

[0062] The non-bad list creation unit 111a performs an automatic screen operation test (screen comparison), and if any differences are found, determines the attributes and contents of the differences, assigns an identification number to information relating to the determined differences (non-bad difference information), and registers it in the non-bad difference information table 114 (adds a new row (record) or updates the value of an existing row (record)).

[0063] The non-fault list creation unit 111a repeats such an automatic screen operation test (automatic screen operation test (screen saving) and automatic screen operation test (screen comparison)) a predetermined number of times (10 times in this example). As a result, the non-fault list creation unit 111a creates the non-fault difference information table 114.

[0064] Hereinafter, a specific example in which the non-bad list creating unit 111a creates the non-bad difference information table 114 through the non-bad list creating process will be described with reference to FIGS. 9A to 9D.

[0065] The non-fault list creation unit 111a performs a first automatic screen operation test (automatic screen operation test (screen saving) and automatic screen operation test (screen comparison)). The non-fault list creation unit 111a executes a scenario and, for each of a plurality of steps in the scenario, compares the comparison reference screen and the comparison target screen captured in the same step. As a result, it is assumed that a difference surrounded by a dashed line R11 has occurred between the comparison reference screen GM90 shown in FIG. 9A captured in step 25 and the comparison target screen GM91 shown in FIG. 9B. In this case, the non-fault list creation unit 111a determines the attribute and content of the difference, assigns an identification number to information related to the determined difference, and adds it to the non-fault difference information table 114 as non-fault difference information.

[0066] The non-fault list creation unit 111a performs a second automatic screen operation test (automatic screen operation test (screen saving) and automatic screen operation test (screen comparison)). The non-fault list creation unit 111a executes a scenario and, for each of a plurality of steps in the scenario, compares a comparison reference screen and a comparison target screen captured in the same step. As a result, it is assumed that a difference surrounded by a dashed line R12 has occurred between the comparison reference screen GM90 shown in FIG. 9A captured in step 25 and the comparison target screen GM92 shown in FIG. 9C. In this case, the non-fault list creation unit 111a determines the attribute and content of the difference, assigns an identification number to information related to the determined difference, and adds it to the non-fault difference information table 114 as non-fault difference information. For the second and subsequent automatic screen operation tests, the method of adding non-fault difference information differs depending on whether the difference is a difference that has occurred for the first time. Note that the color of the text "Thank you for your purchase" on the comparison screen GM92 in Figure 9C is different from the color of the text "Thank you for your purchase" on the comparison reference screen GM90 in Figure 9A (since the application drawings are black and white images, the color difference is not expressed in Figures 9A and 9C).

[0067] If, as a result of determining the attribute and content of the difference, the non-defective list creation unit 111a determines that a difference (non-defective difference information) identical to the difference already exists in the non-defective difference information table 114, the non-defective list creation unit 111a increments the value of the occurrence count 114i of the same difference (non-defective difference information) by "1" and updates the information of the execution content 114h as necessary. In this example, the difference (purchase date and time) in FIG. 9C is the same as the difference (purchase date and time) in FIG. 9B, so the information corresponding to these differences is updated in the non-defective difference information table 114. In principle, whether two differences (difference information) to be compared are identical is determined based on the "difference attribute information." If all of the "difference attribute information" of the two differences match, these differences are determined to be identical. If at least one of the "difference attribute information" of the two differences differs, these differences are determined to be not identical.

[0068] If, as a result of determining the attribute and content of the difference, the non-fault list creation unit 111a finds that the same difference (non-fault difference information) does not exist in the non-fault difference information table 114 (that is, the difference is the first time the difference has occurred), it assigns an identification number to information about the determined difference and adds it as non-fault difference information to the non-fault difference information table 114. In this example, the difference (illustration) that occurred in Figure 9C corresponds to a case where the same difference does not exist (the difference is the first time the difference has occurred), so it assigns an identification number to information about the determined difference (illustration) and adds it to the non-fault difference information table 114 as non-fault difference information.

[0069] The non-fault list creation unit 111a repeats the same automatic screen operation test (automatic screen operation test (screen saving) and automatic screen operation test (screen comparison)) as the second time up to a predetermined number of times (10 times in this example), and then terminates the non-fault list creation process.

[0070] FIG. 9D shows an example of a comparison target screen GM93 when the final (tenth) automatic screen operation test (automatic screen operation test (screen saving) and automatic screen operation test (screen comparison)) is executed. As in the second test, the non-fault list creation unit 111a compares the comparison reference screen and the comparison target screen captured in each of the multiple steps of the scenario. As a result, it is assumed that a difference surrounded by a dashed line R13 has occurred between the comparison reference screen GM90 shown in FIG. 9A captured in step 25 and the comparison target screen GM93 shown in FIG. 9D. In this case, as in the second test, the non-fault list creation unit 111a determines the attribute and content of the difference, assigns an identification number to information related to the determined difference, and adds it to the non-fault difference information table 114.

[0071] In this example, the difference (purchase date and time) in Figure 9D is the same as the difference (purchase date and time) in Figure 9B (Figure 9C), so the value of the occurrence count 114i of this non-fault difference information is incremented by "1" in the non-fault difference information table 114. Furthermore, in this example, the difference (delivery date) corresponds to a case where there is no difference identical to that difference (the difference is the first time that the difference has occurred), so an identification number is assigned to information regarding the identified difference (illustration), and it is added to the non-fault difference information table 114 as non-fault difference information.

[0072] As a result of executing the non-failure list creation process described above, the non-failure difference information table 114 shown in FIG. 3 is created.

[0073] After executing the non-defective list creation process, the non-defective list creation unit 111a outputs a user confirmation screen 1500 (see FIG. 15 ) including information related to the non-defective differences to the display 160 based on the non-defective difference information table 114, and displays the user confirmation screen 1500 on the display 160. By viewing the user confirmation screen 1500 displayed on the display 160, the user can confirm the contents of the non-defective differences obtained as a result of the execution of the non-defective list creation process. The user confirmation screen 1500 will be described in detail later.

[0074] (Outline of the bad difference check process) An overview of the defect difference check process will be explained. The defect difference check unit 111b first performs an automatic screen operation test (screen saving) on ​​a comparison reference screen system (in this example, the screen system before enhancement). Specifically, the defect difference check unit 111b executes a script that executes a scenario on a screen system before enhancement for the screen system that is the target of the defect difference check, thereby executing an automatic screen operation. Note that the screen system before enhancement is the same as the screen system before enhancement used in the non-defective list creation process, and the scenario is the same as the scenario executed in the non-defective list creation process.

[0075] The defect difference check unit 111b holds (stores, memorizes) a plurality of capture screens captured at each step of the scenario in the storage device 110. Each of these plurality of capture screens may be referred to as a "defect check comparison reference screen" or a "second comparison reference screen." Fig. 10A shows a defect check comparison reference screen GM100, which is an example of a defect check comparison reference screen.

[0076] The defect difference check unit 111b performs an automatic screen operation test (screen saving) on ​​the screen system to be checked for defects (in this example, the enhanced screen system). Specifically, the defect difference check unit 111b executes a scenario and obtains multiple capture screens captured at each step of the scenario. Each of these multiple capture screens may be referred to as a "defect check comparison screen" or a "second comparison screen." FIG. 10B shows a defect check comparison screen GM101, which is an example of one defect check comparison screen.

[0077] The defect difference check unit 111b performs an automatic screen operation test (screen comparison), and if there is a difference between the defect check comparison reference screen and the defect check comparison target screen, it determines the attributes and contents of the difference, assigns an identification number to information relating to the determined difference, and registers it as difference information in the difference information table 115 (adds a new row (record)).

[0078] For example, suppose that difference 1 (purchase date and time) and difference 2 (price of product C) surrounded by a dashed line R21 have occurred on the defect check comparison target screen GM101 shown in Fig. 10B compared to the defect check comparison reference screen GM100 shown in Fig. 10A. In this case, the defect difference check unit 111b determines the attribute and content of each difference, difference 1 (purchase date and time) and difference 2 (price of product C), assigns an identification number to information (information other than the defect 115i) relating to each of the determined differences 1 and 2, and adds it to the difference information table 115 as difference information.

[0079] The defect difference check unit 111b determines whether or not the difference occurring between the defect check comparison reference screen GM100 and the defect check comparison target screen GM101 is a non-defective difference.

[0080] The defect difference check unit 111b determines, among the differences (difference information) that have occurred on the defect check comparison screen GM101, differences (difference information) that are identical to non-defective differences (non-defective difference information) registered in the non-defective difference information table 114 as non-defective differences. For example, on the defect check comparison screen GM101 of FIG. 10B, for difference 1 (purchase date and time), a non-defective difference that is the same as this difference 1 (purchase date and time) is registered in the non-defective difference information table 114. Therefore, as shown in FIG. 10C, the defect difference check unit 111b determines difference 1 (purchase date and time) surrounded by a frame 31 as a non-defective difference, and sets the value of defect 115i of the difference (difference information) determined to be a non-defective difference to "0" in the difference information table 115.

[0081] The defective difference check unit 111b determines, among the differences generated in the defect check, a difference that is not registered in the non-defective difference information table 114 as a defective difference. For example, on the defect check comparison screen in FIG. 10B, difference 2 (price of product C) is not registered in the non-defective difference information table 114. Therefore, as shown in FIG. 10C, the defective difference check unit 111b determines difference 2 (price of product C) surrounded by frame line 32 as a defective difference, and sets the value of defect 115i of the difference (difference information) determined to be a defective difference in the difference information table 115 to "1."

[0082] As described above, the defect difference check unit 111b can determine whether the difference occurring in the defect check comparison target screen with respect to the defect check comparison reference screen is a non-defective difference or a defective difference.

[0083] The defect difference check unit 111b creates a defect difference display screen 1600 (see FIG. 16) based on the difference information table 115. The defect difference check unit 111b outputs the defect difference display screen 1600 to the display 160 and displays it on the display 160. By looking at the defect difference display screen 1600, the user can confirm the contents of the difference that has occurred as a result of executing the defect difference check process. The defect difference display screen 1600 will be described in detail later.

[0084] <Specific operation> FIG. 11 is a flowchart showing the processing flow of the non-fault list creation process executed by the non-fault list creation unit 111a of the automatic screen operation test support device 100.

[0085] The non-failure list creating section 111a starts the process from step 1100 in FIG. 11, and executes the processes from step 1105 to step 1175 described below.

[0086] Step 1105: When the non-failure list creation unit 111a proceeds to step 1105, which is the start point of loop 1 processing, it starts executing loop 1 processing from step 1105 to step 1175. This loop 1 processing is repeatedly executed until the end condition of loop 1 (repeated the number of times the number of scenarios to be executed) is met at step 1175, which is the end point of loop 1 processing.

[0087] Step 1110: The non-fault list creation unit 111a selects an unexecuted scenario from the scenarios scheduled for execution, and executes the selected scenario on the target screen system. Hereinafter, for convenience of explanation, the scenario selected in step 1110 may be referred to as the "execution target scenario."

[0088] Step 1115: The non-failure list creating unit 111a acquires a screen capture (Xn) of each step. Note that the screen capture refers to a captured screen.

[0089] Step 1120: The non-fault list creation unit 111a acquires screen information (A) to be assigned to each screen capture. The screen information (A) includes a screen information ID assigned to the screen capture, a scenario ID assigned to the scenario to be executed, and a step number assigned to the step that acquired the screen capture.

[0090] Step 1125: The non-failure list creating unit 111a registers the screen information (A) of the scenario in the screen information table 113.

[0091] Step 1130: When the non-fault list creation unit 111a proceeds to step 1130, which is the start point of the loop 2 process, it starts executing the loop 2 process from step 1130 to step 1170. This loop 2 process is repeatedly executed until the end condition of the loop 2 process (repeated N times) is met at step 1170, which is the end point of the loop 2 process. In this example, N=10 times.

[0092] Step 1135: The non-faulty list creating unit 111a executes the execution target scenario on the target screen system.

[0093] Step 1140: The non-fault list creating unit 111a acquires a screen capture (Yn) of each step.

[0094] Step 1145: When the non-fault list creation unit 111a proceeds to step 1145, which is the start point of the loop 3 process, it starts executing the loop 3 process from step 1145 to step 1165. This loop 3 process is repeatedly executed until the end condition of the loop 3 process (repeated the number of times equal to the number of acquired screen captures (n)) is met at step 1165, which is the end point of the loop 3 process.

[0095] Step 1150: The non-bad list creation unit 111a selects one screen capture (Y) from the output N screen captures (Yn) (n=1 to N) in order starting from 1, and compares the selected screen capture (Y) with the screen capture (X).

[0096] Step 1155: The non-fault list creation unit 111a determines whether or not a difference has occurred between the screen capture (X) and the screen capture (Y). If a difference has occurred between the screen capture (X) and the screen capture (Y), the non-fault list creation unit 111a determines "YES" in step 1155 and proceeds to step 1160. If no difference has occurred between the screen capture (X) and the screen capture (Y), the non-fault list creation unit 111a determines "NO" in step 1155 and proceeds directly to step 1165.

[0097] Step 1160: In order to determine the attribute and content of the difference that has occurred in the screen capture (Y), the non-fault list creating unit 111a executes the difference information determination and DB registration process of Fig. 10. The details of this process will be described later.

[0098] Step 1165: When the non-fault list creation unit 111a proceeds to step 1165, which is the end point of the loop 3 processing, it determines whether the termination condition of the loop 3 processing (repeated the number of times equal to the number (n) of acquired screen captures) is met. If the termination condition of the loop 3 processing (repeated the number of times equal to the number (n) of acquired screen captures) is not met, the non-fault list creation unit 111a returns to step 1145, which is the start point of the loop 3 processing. If the termination condition of the loop 3 processing (repeated the number of times equal to the number (n) of acquired screen captures) is met, the non-fault list creation unit 111a ends the loop 3 processing and proceeds to step 1170.

[0099] Step 1170: When the non-fault list creation unit 111a proceeds to step 1170, which is the end point of the loop 2 processing, it determines whether the end condition of the loop 2 processing (repeated N times) is met. If the end condition of the loop 2 processing (repeated N times) is not met, the non-fault list creation unit 111a returns to step 1130, which is the start point of the loop 2 processing. If the end condition of the loop 2 processing (repeated N times) is met, the non-fault list creation unit 111a ends the loop 2 processing and proceeds to step 1175.

[0100] Step 1175: When the non-fault list creation unit 111a proceeds to step 1175, which is the end point of the loop 1 processing, it determines whether the termination condition of the loop 1 processing (repeating the number of scenarios scheduled to be executed) is met. If the termination condition of the loop 1 processing (repeating the number of scenarios scheduled to be executed) is not met, the non-fault list creation unit 111a returns to step 1110, which is the start point of the loop 1 processing. If the termination condition of the loop 1 processing (repeating the number of scenarios scheduled to be executed) is met, the non-fault list creation unit 111a ends the loop 1 processing, proceeds to step 1195, and temporarily ends this processing flow.

[0101] FIG. 12 is a flowchart showing the process flow of the difference information discrimination and DB registration process executed by the non-fault list creation unit 111a of the automatic screen operation test support device 100.

[0102] When the non-fault list creating section 111a proceeds to step 1160 in FIG. 11, it starts the process from step 1200 in FIG. 12 and executes the processes of steps 1205 to 1230 described below in order.

[0103] Step 1205: The non-failure list creating unit 111a acquires the screen information (scenario ID and step number) corresponding to the screen capture (Y).

[0104] Step 1210: The non-failure list creating unit 111a obtains, from the screen information table 113, the screen information ID corresponding to the scenario ID and the step number.

[0105] Step 1215: The non-fault list creating unit 111a acquires the coordinate information (X, Y) of at least one difference location that has occurred in the screen capture (Y).

[0106] Step 1220: The non-fault list creating unit 111a determines the content type and difference type of the difference portion, and acquires difference information (attribute information of the difference).

[0107] Step 1225: The non-fault list creating unit 111a holds the content of the difference part of the screen capture (X) (original content) and the content of the difference part of the screen capture (Y) (content at the time of execution).

[0108] Step 1230: The non-bad list creating unit 111a creates a difference information table (B) of the screen information ID, coordinate information, content type, and difference content (original content and execution content) acquired in steps 1210 to 1225. Note that the difference information table (B) is information corresponding to one row (record) of the non-bad difference information table 114. If there are multiple difference locations, a difference information table (B) corresponding to each of the multiple locations is created.

[0109] When the non-defective list creating unit 111a proceeds to step 1235, it determines whether or not the non-defective difference information table 114 contains the same information as the difference information table (B). Note that the presence of the same information here means that the screen information ID is the same, the coordinate information is the same, the content type is the same, and the difference type is the same.

[0110] If the non-fault differential information table 114 does not contain the same information as the differential information table (B), the non-fault list creation unit 111a determines "NO" in step 1235 and proceeds to step 1240 to add (register) the differential information table (B) to the non-fault differential information table 114. Thereafter, the non-fault list creation unit 111a proceeds to step 1295 to temporarily end this processing flow.

[0111] If the non-fault differential information table 114 contains the same information as the differential information table (B), the non-fault list creation unit 111a determines "YES" in step 1235 and proceeds to step 1245, where it increments by "1" the value of the number of occurrences of non-fault differential information corresponding to the already registered differential information table (B) in the non-fault differential information table 114. Thereafter, the non-fault list creation unit 111a proceeds to step 1295 and temporarily ends this processing flow.

[0112] 13 is a flowchart showing the processing flow of the defect difference check processing executed by the defect difference check unit 111b of the automatic screen operation test support device 100. The defect difference check unit 111b starts the processing from step 1300 in FIG. 13 and executes the processing of steps 1300 to 1360 described below.

[0113] Step 1305: When the defect difference check unit 111b proceeds to step 1305, which is the start point of loop 1 processing, it starts executing loop 1 processing from step 1305 to step 1360. This loop 1 processing is repeatedly executed until the end condition of loop 1 (repeated the number of times the number of scenarios to be executed) is met at step 1360, which is the end point of loop 1 processing.

[0114] Step 1310: The defect difference check unit 111b selects an unexecuted scenario from the scenarios scheduled to be executed, and executes the selected scenario on the pre-enhancement screen system corresponding to the screen system to be checked for defects. The defect difference check unit 111b executes the selected scenario on the screen system to be checked for defects.

[0115] Step 1315: The defect difference check unit 111b acquires a screen capture (defect check comparison reference screen) of each step for the screen system before enhancement. The defect difference check unit 111b acquires a screen capture (defect check comparison target screen) of each step for the screen system to be checked for defects.

[0116] Step 1320: When the defect difference check unit 111b proceeds to step 1320, which is the start point of the loop 2 process, it starts executing the loop 2 process from step 1320 to step 1355. This loop 2 process is repeatedly executed until the end condition of the loop 2 process (the loop 2 process has been repeated the number of times equal to the number of acquired screen captures (n)) is met at step 1355, which is the end point of the loop 2 process.

[0117] Step 1325: The defect difference check unit 111b selects a pair of screen captures (a pair of a defect check comparison reference screen and a defect check comparison target screen) for which the loop 2 process has not been executed, and compares the defect check comparison reference screen with the defect check comparison target screen.

[0118] Step 1330: The defect difference check unit 111b determines whether or not at least one difference has occurred between the defect check comparison reference screen and the defect check comparison target screen as a result of the comparison. If at least one difference has occurred between the defect check comparison reference screen and the defect check comparison target screen, the defect difference check unit 111b determines "YES" in step 1330 and proceeds to step 1335. If no difference has occurred between the defect check comparison reference screen and the defect check comparison target screen, the defect difference check unit 111b determines "NO" in step 1330 and proceeds to step 1355.

[0119] Step 1335: The defect difference check unit 111b executes the process of determining the difference information shown in Fig. 14. Details of this process will be described later.

[0120] Step 1340: The defective difference check unit 111b determines whether or not non-defective difference information that is the same as the difference information determined in step 1335 is present in the non-defective difference information table 114. Note that the difference information and non-defective difference information being the same means that the screen information ID is the same, the coordinate information is the same, the content type is the same, and the difference type is the same.

[0121] If the non-faulty difference information table 114 contains the same non-faulty difference information as the difference information determined in step 1335 , the faulty difference check unit 111 b determines “YES” in step 1340 and proceeds to step 1345 .

[0122] If the non-faulty difference information table 114 does not contain the same non-faulty difference information as the difference information determined in step 1335 , the faulty difference check unit 111 b determines “NO” in step 1340 and proceeds to step 1350 .

[0123] Step 1345: The defective difference check unit 111b determines the determined difference information as a non-defective difference, stores a value of "0" in the defect column of the difference information table 115, and stores (registers) the difference information in the corresponding row.

[0124] Step 1350: The defective difference check unit 111b determines the determined difference information as a problematic difference (defective difference), stores a value of "1" in the defect column of the difference information table 115, and stores (registers) the difference information in the corresponding row.

[0125] Step 1355: When the defect difference check unit 111b proceeds to step 1355, which is the end point of the loop 2 processing, it determines whether the end condition of the loop 2 processing (repeated the number of times equal to the number (n) of acquired screen captures) is met. If the end condition of the loop 2 processing (repeated the number of times equal to the number (n) of acquired screen captures) is not met, the defect difference check unit 111b returns to step 1320, which is the start point of the loop 2 processing. If the end condition of the loop 2 processing (repeated the number of times equal to the number (n) of acquired screen captures) is met, the defect difference check unit 111b ends the loop 2 processing and proceeds to step 1360.

[0126] Step 1360: When the defect difference check unit 111b proceeds to step 1360, which is the end point of the loop 1 processing, it determines whether the termination condition of the loop 1 processing (repeating the number of scenarios scheduled to be executed) is met. If the termination condition of the loop 1 processing (repeating the number of scenarios scheduled to be executed) is not met, the defect difference check unit 111b returns to step 1305, which is the start point of the loop 1 processing. If the termination condition of the loop 1 processing (repeating the number of scenarios scheduled to be executed) is met, the defect difference check unit 111b ends the loop 1 processing, proceeds to step 1395, and temporarily ends this processing flow.

[0127] Fig. 14 is a flowchart showing the processing flow of the difference information discrimination processing executed by the defect difference check unit 111b of the automatic screen operation test support device 100. When the defect difference check unit 111b proceeds to step 1335 in Fig. 13, it starts processing from step 1400 in Fig. 14, and executes the processing of steps 1405 to 1425 described below in order, and then temporarily ends this processing flow.

[0128] Step 1405: The defect difference check unit 111b acquires screen information (scenario ID and step number) corresponding to the defect check comparison target screen.

[0129] Step 1410: The defect difference check unit 111b obtains from the screen information table 113 the screen information ID corresponding to the scenario ID and step number.

[0130] Step 1415: The defect difference check unit 111b acquires coordinate information of at least one difference location.

[0131] Step 1420: The defective difference check unit 111b determines the content of the difference.

[0132] Step 1425: The defective difference check unit 111b uses existing technology (OCR) to determine the content type and difference type of the difference portion.

[0133] <Output screen> After the non-fault list creation process, the non-fault list creation unit 111a of the automatic screen operation test support device 100 displays a user confirmation screen 1500 on the display 160. Fig. 15 shows the user confirmation screen 1500. As shown in Fig. 15, the user confirmation screen 1500 includes an occurrence count narrowing down button 1501, an upper and lower limit narrowing down button 1502, and a non-fault difference list table 1503.

[0134] The occurrence count narrowing button 1501 is a button that the user operates to select one of the "plural numbers" indicating the occurrence counts displayed as options.

[0135] The upper / lower limit narrowing button 1502 is a button that the user operates to select either "greater than" or "less than" displayed as options.

[0136] When occurrence count narrowing down button 1501 is operated to select any number from "multiple numbers", and when upper / lower limit narrowing down button 1502 is operated to select "more than or equal to", "more than or equal to selected occurrence count (number)" is set as the narrowing down condition for the occurrence count. When occurrence count narrowing down button 1501 is operated to select any number from "multiple numbers", and when upper / lower limit narrowing down button 1502 is operated to select "less than or equal to selected occurrence count (number)", the narrowing down condition for the occurrence count is set as the narrowing down condition.

[0137] When the occurrence count narrowing down button 1501 and the upper and lower limit narrowing down button 1502 are operated, the non-fault list creation unit 111a creates a non-fault difference list table 1503 whose contents correspond to the selected conditions based on the screen information table 113 and the non-fault difference information table 114, and outputs and displays it on the display 160.

[0138] Non-defective difference list table 1503 displays multiple non-defective difference lists organized by scenario, and displays the information items of the non-defective difference list, including the step in which the difference occurred, coordinates, content type, difference type, difference content (original content and content at the time of execution), and number of occurrences. A non-defective difference list corresponds to one row of non-defective difference list table 1503. One non-defective difference list displays the content corresponding to one piece of non-defective difference information in non-defective difference information table 114.

[0139] The user can understand the discrimination results (attributes and contents) and occurrence count of differences that occurred in the non-defective list creation process by looking at the non-defective difference list table 1503 on the user confirmation screen 1500. Although not shown in the figure, when the user performs an operation to select a step number (for example, step 3 of scenario 1) in the non-defective difference list table 1503 (for example, by double-clicking the mouse (operating device) with cursor Cs1 over step 3), that step (step 3) is selected, and a comparison screen (not shown) is displayed that includes capture screens (comparison reference screen and comparison target screen) that correspond to the selected step (step 3).

[0140] 16 shows a defect difference display screen 1600 after the defect difference check process. The defect difference check unit 111b displays the defect difference display screen 1600 on the display 160 after the defect difference check process.

[0141] The defective difference display screen 1600 includes a difference presence / absence narrowing button 1601 , a defectiveness narrowing button 1602 , a content type narrowing button 1603 , a difference type narrowing button 1604 , a cancel narrowing button 1605 , and a difference list table 1606 .

[0142] The difference list table 1606 includes a plurality of difference lists organized by scenario, and information items in the difference list table such as step, presence or absence of difference, defect, content type, difference type, and difference content (original content and execution content). A difference list corresponds to one row in the difference list table 1606. One difference list displays content corresponding to one piece of difference information in the difference information table 115.

[0143] The difference presence / absence narrowing down button 1601 is a button that is operated by the user to select one of "all," "presence," and "-" displayed as options.

[0144] When the user operates the difference presence / absence narrowing down button 1601 and selects "all", the narrowing down conditions are set to "all difference lists where the information in the difference presence / absence item is "yes" and all difference lists where the information in the difference presence / absence item is "no".

[0145] When the user operates the difference existence narrowing down button 1601 to select "existence", the "list of differences for which the information in the difference existence item is 'existence'" is set as the narrowing down condition.

[0146] When the user operates the difference presence / absence narrowing down button 1601 to select "-", the "list of differences with information "-" in the difference presence / absence item" is set as the narrowing down condition.

[0147] The defect narrowing down button 1602 is a button that is operated by the user to select one of "all," "defective," and "non-defective," which are displayed as options.

[0148] When the user operates the defect narrowing down button 1602 and selects "all", the narrowing down condition is set to "all difference lists where the defect item information is 'defective' and all difference lists where the defect item information is 'non-defective'".

[0149] When the user operates the defect narrowing down button 1602 to select "defective", the "difference list in which the defect item information is 'defective'" is set as the narrowing down condition.

[0150] When the user operates the defect narrowing down button 1602 to select "non-defective", the "difference list in which the information in the defect item is 'non-defective'" is set as the narrowing down condition.

[0151] The content type narrowing button 1603 is a button that the user operates to select one of the displayed options such as "All," "Image," "Date," and "Character string."

[0152] When the user operates the content type narrowing down button 1603 to select "all", "all difference lists in which the information in the content type item is one of the options" is set as the narrowing down condition.

[0153] When the user operates the content type narrowing down button 1603 to select one of "Image," "Date," and "Character string," etc., the "difference list in which information on the content type item is the selected option" is set as the narrowing down condition.

[0154] The difference type narrowing down button 1604 is a button that the user operates to select from options such as "All," "Size," "Background color," "Text color," "Color," "Language," "Font," "Content," and "Coordinates."

[0155] When the user operates the difference type narrowing down button 1604 to select "all", "all difference lists in which the information in the difference type item is one of the options" is set as the narrowing down condition.

[0156] When the user operates the difference type narrowing down button 1604 and selects one of the options from "size," "background color," "text color," "color," "language," "font," "content," and "coordinates," the narrowing down condition is set to "difference list in which the information in the difference type item is the selected option."

[0157] The defective difference check unit 111b sets a final narrowing condition that uses the set narrowing condition as an "AND" condition, includes a difference list according to the final narrowing condition in the difference list table 1606, and displays the difference list table 1606.

[0158] In the example of FIG. 16, difference list table 1606 is displayed with difference lists that satisfy the following conditions: "all difference lists for which the information in the difference presence / absence field is 'present', and all difference lists for which the information in the difference presence / absence field and the difference presence / absence field is 'absent'", "all difference lists for which the information in the defective field is 'defective'", "all difference lists for which the information in the content type field is one of the options", and "all difference lists for which the information in the difference type field is one of the selected options".

[0159] 16, only the defective differences are displayed so that problematic defective differences can be easily identified. By looking at the difference list table 1606 on the defective difference display screen 1600, the user can easily understand the results (attributes and details) of the defective differences that occurred in the defective difference check process.

[0160] The filter cancel button 1605 is a button that is operated by the user to reset (cancel, clear) the filter conditions that have been set.

[0161] FIG. 17 shows a comparison screen 1700 including a capture screen in which a difference has occurred. When a user selects "Yes" in the difference list on the defective difference display screen 1600 of FIG. 16, the comparison screen 1700 of FIG. 17 is displayed. The comparison screen 1700 includes a difference content 1701 including detailed content (attributes and content) of the difference corresponding to the selected "Yes" difference list, the screen in which the difference has occurred (a comparison reference screen 1702 and a comparison target screen 1703), and a border button 1704. The border button 1704 is a button operated by the user to select either "Do not add border" or "Add border," which are displayed as options. When the user operates the border button 1704 to select "Do not add border," a border 1705 is not superimposed on the difference portion in the capture screen (comparison target screen 1703) after checking. When the user selects "Add border," a border 1705 is superimposed on the difference portion in the capture screen (comparison target screen 1703) after checking. By viewing the comparison screen 1700, the user can grasp the details of the differences (attributes and contents) and visually grasp the locations where the differences have occurred.

[0162] FIG. 18 shows the defective difference display screen 1600 after the cancel filter button 1605 is operated on the defective difference display screen 1600 of FIG. 17. When the cancel filter button 1605 is operated on the defective difference display screen 1600 of FIG. 17, the filter conditions are reset. As a result, as shown in FIG. 18, "All" is selected on the difference presence / absence filter button 1601, "All" is selected on the defect filter button 1602, "All" is selected on the content type filter button 1603, and "All" is selected on the difference type filter button 1604. A difference list table 1606 displays a difference list according to the set filter conditions. The defective difference display screen 1600 of FIG. 18 displays differences resulting from the defective difference check process and step numbers corresponding to captured images in which no differences have occurred. In other words, not only is a difference list corresponding to differences resulting from the defective difference check process displayed, but also information on step numbers corresponding to captured images in which no differences have occurred in the defective difference check process (referred to as a "difference list (no differences)") is displayed. The difference list (no differences) includes, as step item information, step numbers corresponding to capture screens with no differences, and as information for other items, includes "-" indicating that no information exists. On the failure difference display screen 1600 in Fig. 18, the row for step 1 of scenario 1 and the row for step 2 of scenario 2 correspond to the difference list (no differences).

[0163] <Effects> As described above, the automatic screen operation test support device 100 according to the first embodiment of the present invention can extract problematic defective differences without requiring manual labor. The automatic screen operation test support device 100 according to the first embodiment considers differences in all image regions in the non-fault list creation process and does not set fixed verification-unnecessary regions as in the prior art. This reduces the possibility that a problematic difference (defective difference) will be overlooked if it occurs in a difference comparison exclusion region. The automatic screen operation test support device 100 according to the first embodiment registers differences resulting from multiple automatic screen operation tests as non-faultive differences in the non-fault list creation process. This allows non-problematic differences that would not appear in a single comparison of output results (e.g., differences due to blinking) to be registered as non-faultive differences.

[0164] <<Second embodiment>> An automatic screen operation test support device 100 according to a second embodiment of the present invention will be described. The automatic screen operation test support device 100 according to the second embodiment differs from the automatic screen operation test support device 100 according to the first embodiment only in the following points.

[0165] In the non-fault list creation process, the automatic screen operation test support device 100 according to the second embodiment presents to the user non-fault differences whose difference count is less than or equal to a threshold count, and determines whether or not to exclude them from the non-fault differences (non-fault difference information) used in the fault difference check process based on the user's judgment.

[0166] The following description will focus on this difference.

[0167] <Summary> In the non-failure list creation process, a difference that occurs frequently is likely to be a non-failure difference, while a difference that occurs infrequently tends to be difficult to determine whether it is a non-failure difference or not.

[0168] Therefore, the automatic screen operation test support device 100 according to the second embodiment presents the non-faulty difference to the user as a target for exclusion if the number of occurrences of the difference is equal to or less than a threshold number in the non-faulty list creation process. Based on the user's judgment, the automatic screen operation test support device 100 determines whether or not to exclude the non-faulty difference from the non-faulty difference (non-faulty difference information) used in the faulty difference check process.

[0169] FIG. 19 is a diagram illustrating the non-bad difference information table 114. The non-bad difference information table 114 is similar to the non-bad difference information table 114 shown in FIG. 3, except that a threshold flag 114j is added as a column for storing information. The threshold flag 114j stores information ("0" or "1") indicating whether the number of occurrences is equal to or less than the threshold number. "0" indicates that the number of occurrences is greater than the threshold number, and "1" indicates that the number of occurrences is equal to or less than the threshold number. Non-bad difference information for which the threshold flag 114j is "1" is excluded from the non-bad difference information used in the bad difference check process (step 1235 in FIG. 12).

[0170] 20 is a diagram partially showing a threshold count setting screen 2000. The threshold count setting screen 2000 includes a threshold count setting button 2001. The threshold count setting button 2001 is a button that is operated by the user to select one of a plurality of number (number) options displayed as options.

[0171] When the user operates the threshold number of times setting button 2001 to select one of a plurality of number of times (numbers) options, the selected number of times (numbers) is set as the threshold number of times.

[0172] <Specific operation> The automatic screen operation test support device 100 according to the second embodiment executes the processing flow of Fig. 21 instead of the processing flow of Fig. 11. Fig. 21 is a flowchart showing the processing flow of non-fault list creation processing executed by the non-fault list creation unit 111a of the automatic screen operation test support device 100 according to the second embodiment.

[0173] The processing flow in Fig. 21 is the same as the processing flow in Fig. 11 except that steps 2105 and 2110 have been added between steps 1170 and 1175 in the flowchart in Fig. 11. Therefore, the following explanation will focus on these different steps 2105 and 2110.

[0174] When the non-fault list creation unit 111a proceeds to step 2105, it determines whether or not a threshold number of times of difference occurrence is set. If the threshold number of times of difference occurrence is set, the non-fault list creation unit 111a determines "YES" in step 2105 and proceeds to step 2110.

[0175] When the non-fault list creation unit 111a proceeds to step 2110, it determines whether the occurrence count 114i of non-fault difference information in the non-fault difference information table 114 for the scenario executed in step 1110 is equal to or less than a threshold count. Based on the determination result, the non-fault list creation unit 111a stores (inputs) "1" in the threshold flag 114j of non-fault difference information that is equal to or less than the threshold count. As a result, non-fault difference information that is equal to or less than the threshold count is excluded from the non-fault difference information used in the fault difference check process (step 1235 in FIG. 12). Thereafter, the non-fault list creation unit 111a proceeds to step 1175, which is the end point of loop 1 processing, and executes the above-mentioned process.

[0176] If the threshold number of difference occurrences has not been set, the non-fault list creating section 111a determines "NO" in step 2105, proceeds to step 1175 which is the end point of the loop 1 process, and executes the above-described process.

[0177] <Output screen> After the non-fault list creation process, the non-fault list creation unit 111a of the automatic screen operation test support device 100 displays a user confirmation screen 2200 on the display 160. Fig. 22 shows the user confirmation screen 2200. As shown in Fig. 22, the user confirmation screen 2200 includes a threshold judgment narrowing button 2201 and a non-fault difference list table 2202.

[0178] The threshold judgment narrowing button 2201 is a button that is operated by the user to select one of "all," "non-fault," and "exclude," which are displayed as options.

[0179] The non-fault difference list table 2202 includes a judgment result button 2203 as information corresponding to the threshold judgment item. The judgment result button 2203 is a button that the user operates to select either "non-fault" or "exclude" from the options displayed. In the initial state after the non-fault list creation process, if the number of occurrences of the corresponding non-fault difference is greater than the threshold number (if the threshold flag is "0"), the judgment result button 2203 is in a state where "non-fault" is selected and the word "non-fault" is displayed. If the number of occurrences of the corresponding non-fault difference is equal to or less than the threshold number (if the threshold flag is "1"), the judgment result button 2203 is in a state where "exclude" is selected and the word "exclude" is displayed.

[0180] When exclusion is selected while "non-bad" is displayed, the non-bad list creation unit 111a changes the value of the threshold flag 114j of the non-bad difference information in the non-bad difference information table 114 corresponding to that non-bad difference list from "0" to "1."

[0181] When "Non-bad" is selected with "Exclude" displayed, the non-bad list creation unit 111a changes the value of the threshold flag 114j of the non-bad difference information in the non-bad difference information table 114 corresponding to that non-bad difference list from "1" to "0."

[0182] When "All" is selected by operating the threshold judgment narrowing down button 2201, "all difference lists for which the judgment result button 2203 displays "Not Bad" and all difference lists for which the judgment result button 2203 displays "Exclude"" are set as the narrowing down conditions. When "Non-Bad" is selected by operating the threshold judgment narrowing down button, "all difference lists for which the judgment result button 2203 displays "Not Bad"" is selected as the narrowing down conditions. When "Exclude" is selected by operating the threshold judgment narrowing down button, "all difference lists for which the judgment result button 2203 displays "Exclude"" is selected as the narrowing down conditions.

[0183] When the threshold judgment narrowing button 2201 is operated, the non-fault list creation unit 111a creates a non-fault difference list table 2202 with content corresponding to the selected conditions based on the screen information table 113 and the non-fault difference information table 114, and outputs and displays it on the display 160.

[0184] Non-faulty difference list table 2202 includes multiple non-faulty difference lists organized by scenario, and displays the information items of the non-faulty difference list, such as the step in which the difference occurred, coordinates, content type, difference type, difference content (original content and content at runtime), number of occurrences, and threshold judgment. A non-faulty difference list corresponds to one row of non-faulty difference list table 2202. One non-faulty difference list displays the content corresponding to one piece of non-faulty difference information.

[0185] The display mode of the information (number indicating the number of occurrences) in the occurrence count item included in non-fault difference list table 2202 may be different when the number of occurrences of the non-fault difference list is greater than a threshold number and when the number of occurrences of the non-fault difference list is equal to or less than the threshold number. For example, when the number of occurrences of the non-fault difference list is greater than the threshold number, the number indicating the number of occurrences may be black, and when the number of occurrences of the non-fault difference list is equal to or less than the threshold number, the number indicating the number of occurrences may be red.

[0186] <Effects> As described above, the automatic screen operation test support device 100 according to the second embodiment of the present invention achieves the same effects as those of the first embodiment. Furthermore, the automatic screen operation test support device 100 according to the second embodiment can record the number of times a difference occurs in a comparison of differences in the automatic screen operation test of the non-fault list creation process, and can register the difference in the non-fault difference list taking the number of occurrences into consideration.

[0187] <<Third Embodiment>> An automatic screen operation test support device 100 according to a third embodiment of the present invention will be described. The automatic screen operation test support device 100 according to the third embodiment differs from the automatic screen operation test support device 100 according to the first embodiment only in the following points.

[0188] In the automatic screen operation test support device 100 according to the third embodiment, in the defective difference check process executed by the defective difference check unit 111b, among the differences generated by the automatic screen operation test that cannot be identified as non-defective differences, differences whose coordinates differ from those of the non-defective differences registered in the non-defective difference information table 114, whose content type and difference type match, and whose coordinate difference is within a threshold value, are identified as non-defective differences.

[0189] The following description will focus on this difference.

[0190] <Summary> In the defective difference check process, among the differences generated by the automatic screen operation test that cannot be identified as non-defective differences, there may be differences that can be identified as non-defective differences. For example, differences that differ only slightly in coordinate values ​​from the non-defective difference information registered in the non-defective difference information table 114 tend to be able to be identified as non-defective differences.

[0191] Therefore, in the defective difference check process, the automatic screen operation test support device 100 according to the third embodiment identifies, as a non-defective difference, a difference that cannot be identified as a non-defective difference if, among the differences generated by the automatic screen operation test that cannot be identified as a non-defective difference, there is a difference whose coordinates differ from those of the non-defective difference in the non-defective difference information table 114, whose content type and difference type match, and whose coordinate difference is within a threshold value. This enables the automatic screen operation test support device 100 to improve the accuracy of extracting defective differences.

[0192] 23 is a diagram partially showing an allowable coordinate setting screen 2300. The allowable coordinate setting screen 2300 includes an x-coordinate error setting button 2301 and a y-coordinate error setting button 2302. The x-coordinate error setting button 2301 is a button that the user operates to select one of the pixel values ​​displayed as options. When the user operates the x-coordinate error setting button 2301 to select a pixel value, the selected pixel value is set as the allowable error for the x-coordinate value.

[0193] The y coordinate error setting button 2302 is a button that the user operates to select one of the pixel values ​​displayed as options. When the user operates the y coordinate error setting button 2302 to select a pixel value, the selected pixel value is set as the allowable error for the y coordinate value.

[0194] An overview of the defect difference check process will be explained using the non-defective difference information table 114 in Fig. 24 and the difference information table 115 in Fig. 25. Fig. 24 shows an example of the non-defective difference information table 114 created by the non-defective list creation unit 111a through the non-defective list creation process. Fig. 25 shows an example of the difference information table 115 that shows the differences that have occurred as a result of the defect difference check unit 111b executing an automatic screen operation test in the defect difference check process.

[0195] In the failure difference check process, the difference information in the difference information table 115 in FIG. 25 is compared with the non-failure difference information in the non-failure difference information table 114 in FIG.

[0196] As a result, the difference information having ID 115a of 00001 in the difference information table 115 matches the attribute information other than the coordinate information with the non-fault difference information having ID 114a of 00004 in the non-fault difference information table 114, and the difference in the coordinate values ​​of the coordinate information is within the allowable error. Therefore, the value of fault 115i is set to "0" for the difference information having ID 115a of 00001 in the difference information table 115. In other words, of the differences that cannot be identified as non-fault differences, differences that differ only in coordinate values ​​from the non-fault difference and whose coordinate difference from the non-fault difference is within the threshold are identified as non-fault differences.

[0197] The difference information with ID 00002 in the difference information table 115 does not completely match any of the non-fault difference information in the non-fault difference information table 114, and attribute information other than coordinate values ​​also does not match. Therefore, for the difference information with ID 115a of 00002 in the difference information table 115, the value of fault 115i is set to "0." In other words, a difference that cannot be identified as a non-fault difference is identified as a fault difference.

[0198] The difference information with ID 00003 in difference information table 115 exactly matches the non-faulty difference information with ID 114a of 00004 in non-faulty difference information table 114 (the screen information ID, coordinates, content type, and difference type are all identical). Therefore, the value of defect 115i for the difference information with ID 00003 in difference information table 115 is set to "0," and the ID (identification number) of the matching non-faulty difference information is stored in non-faulty difference information ID 115h. In other words, a difference that can be identified as a non-faulty difference is identified as a non-faulty difference.

[0199] <Specific operation> The automatic screen operation test support device 100 according to the third embodiment executes the processing flow of Fig. 26 instead of the processing flow of Fig. 13. Fig. 26 is a flowchart showing the processing flow of the defect difference check processing executed by the defect difference check unit 111b of the automatic screen operation test support device 100 according to the third embodiment.

[0200] The processing flow in Fig. 26 is the same as the processing flow in Fig. 13 except that step 2605 is added between step 1300 and step 1305 in the flowchart in Fig. 13, and step 2610 is added between step 1340 and step 1350. Therefore, the following explanation will focus on these different steps 2605 and 2610.

[0201] 26, the defect difference check unit 111b starts processing at step 2600 and proceeds to step 2605, where it reads the allowable error of the coordinate information set by the user. After that, the defect difference check unit 111b executes the processing of steps 1305 to 1335 described above, and then proceeds to step 1340, where it determines whether or not the non-defective difference information table 114 contains the same difference information (non-defective difference information) as the difference (difference information) determined in step 1335.

[0202] If the same difference information exists in the non-faulty difference information table 114, the faulty difference check unit 111b judges "YES" in step 1340 and proceeds to step 1345, where it executes the processing of step 1345 described above, and then proceeds to step 1355.

[0203] If there is no difference information in non-bad difference information table 114 that is the same as the difference (difference information) determined in step 1335, bad difference check unit 111b determines "NO" in step 1340 and proceeds to step 2610. In step 2610, bad difference check unit 111b determines whether there is a difference (difference information) in non-bad difference information table 114 that has the same content type as the difference (difference information) determined in step 1335, the difference type is coordinates, and the difference in coordinate difference is within a threshold value.

[0204] If the non-bad difference information table 114 contains a difference (difference information) for the target difference where the content type is the same, the difference type is coordinates, and the difference in coordinates is within the threshold, the bad difference check unit 111b judges "YES" in step 2610 and proceeds to step 1345, executes the processing of step 1345 described above, and then proceeds to step 1355.

[0205] If the content type of the target difference is the same, the difference type is coordinates, and there is no difference (difference information) in the non-bad difference information table 114 where the difference in coordinates is within the threshold, the bad difference check unit 111b judges "NO" in step 2610 and proceeds to step 1350, performs the processing of step 1350 described above, and then proceeds to step 1355.

[0206] <Effects> As described above, the automatic screen operation test support device 100 according to the third embodiment of the present invention achieves the same effects as the first embodiment. Furthermore, in the defective difference check process, the automatic screen operation test support device 100 according to the third embodiment identifies a difference that cannot be identified as a non-defective difference as a non-defective difference if the non-defective difference information table 114 contains a difference whose coordinate value difference is within a threshold value. This allows the automatic screen operation test support device 100 according to the third embodiment to improve the accuracy of extracting defective differences.

[0207] <<Fourth Embodiment>> An automatic screen operation test support device 100 according to a fourth embodiment of the present invention will be described. The automatic screen operation test support device 100 according to the fourth embodiment differs from the automatic screen operation test support device 100 according to the second embodiment only in the following points.

[0208] The automatic screen operation test support device 100 according to the fourth embodiment is configured so that the user can change the result that has been determined (either a defective difference or a non-defective difference) from a defective difference to a non-defective difference, or from a non-defective difference to a defective difference, while checking the difference contents on the defective difference display screen 2700 (see FIG. 27A) that is output after the defective difference check process.

[0209] The following description will focus on this difference.

[0210] <Output screen> 27A shows a defect difference display screen 2700 after the defect difference check. The defect difference check unit 111b displays the defect difference display screen 2700 on the display 160 after the defect difference check process.

[0211] The defect difference display screen 2700 includes a difference presence / absence narrowing down button 2701 , a defect narrowing down button 2702 , a user change button 2703 , a redisplay button 2704 , and a difference list table 2705 .

[0212] The difference list table 2705 includes a plurality of difference lists organized by scenario, and information items displayed in the difference list table 2705, such as step, presence / absence of difference, defect, content type (not shown), difference type (not shown), difference content (original content and content at execution time) (not shown), and user changes. A difference list corresponds to one row in the difference list table 2705. One difference list displays content corresponding to one piece of difference information. The difference list includes a non-defective setting button 2706 as information corresponding to an item changed by the user. Note that in the difference list table 2705, information in the defect item of the difference list corresponding to a difference for which it is difficult to determine whether it is defective or not is displayed as [SUGGESTED] Not defective.

[0213] For example, if non-faulty difference information exists in the non-faulty difference information table 114 that has the same coordinate information, content type, and difference type but a different screen information ID for difference information in the difference information table, "SUGGESTED] NOT FAULT" is displayed in the information for the faulty item in the difference list corresponding to that difference information. If the same "non-faulty difference information excluded by threshold judgment" exists in the non-faulty difference information table 114 for difference information in the difference information table, "SUGGESTED] NOT FAULT" is displayed in the information for the faulty item in the difference list corresponding to that difference information. "SUGGESTED] NOT FAULT" is displayed, for example, in a different display mode (for example, a different color) from the display modes for faulty and non-faulty.

[0214] The difference presence / absence narrowing down button 2701 and the defect narrowing down button 2702 are buttons having the same functions as the difference presence / absence narrowing down button 1601 and the defect narrowing down button 1602 in Fig. 16. The user change button 2703 is a button operated by the user to select one of "all", "non-defective", and "none" displayed as options.

[0215] When "All" is selected by operating the user change button 2703, "all difference lists for which the non-fault setting button 2706 displays "non-fault" and all difference lists for which the non-fault setting button 2706 displays "no display"" are set as the narrowing down conditions.

[0216] When "non-fault" is selected by operating the user change button 2703, "all difference lists for which the non-fault setting button 2706 displays "non-fault"" is set as the narrowing-down condition. When "none" is selected by operating the user change button 2703, "all difference lists for which the non-fault setting button 2706 displays no display" is set as the narrowing-down condition.

[0217] The defect difference check unit 111b sets the narrowing down conditions set by operating the difference presence / absence narrowing down button 2701, the defect narrowing down button 2702, and the user change button 2703 as the final narrowing down conditions as an "AND" condition, includes a difference list according to the final narrowing down conditions in the difference list table 2705, and displays the difference list table 2705.

[0218] The non-fault setting button 2706 is a button that the user operates to select either "non-fault" or "fault" displayed as options. When the user operates the non-fault setting button 2706 to select "non-fault", the information in the corresponding fault item in the difference list is changed to non-fault.

[0219] When the user operates the non-fault setting button 2706 to select "fault" for a difference list in which the information for the fault item is "non-fault" or "probably" non-fault, the information for the fault item in the corresponding difference list is changed to "fault." Furthermore, the non-fault difference information (column (record)) corresponding to the difference list that has been changed to faulty is deleted from the non-fault difference information table 114.

[0220] When the user operates the non-fault setting button 2706 and selects "non-fault" for a difference list in which the information for the fault item is "fault" or "probably" non-fault, the information for the fault item in the corresponding difference list is changed to "non-fault."

[0221] For example, in Fig. 27A, when "non-fault" is selected from the difference list displaying "fault" or "probable" non-fault as indicated by arrows b1, b2, and b3, the fault difference check unit 111b updates the value of fault 115i in the corresponding difference information in the difference information table 115 to "0." Furthermore, the fault difference check unit 111b changes the display of "fault" or "probable" non-fault in Fig. 27A to "non-fault" as indicated by arrows b1, b2, and b3 in Fig. 27B.

[0222] <Effects> As described above, the automatic screen operation test support device 100 according to the fourth embodiment of the present invention achieves the same effects as the automatic screen operation test support device 100 according to the second embodiment. The automatic screen operation test support device 100 according to the fourth embodiment allows the user to change a defective difference to a non-defective difference while checking the content of the difference on the defective difference display screen.

[0223] <<Fifth Embodiment>> An automatic screen operation test support device 100 according to a fifth embodiment of the present invention will be described. The automatic screen operation test support device 100 according to the fifth embodiment differs from the automatic screen operation test support device 100 according to the first embodiment only in the following points.

[0224] The automatic screen operation test support device 100 according to the fifth embodiment determines the importance of differences in the defective difference check process so that defective differences with high importance are easily identified. The automatic screen operation test support device 100 selects and outputs defective differences according to their importance from among the defective differences.

[0225] The following description will focus on this difference.

[0226] Fig. 28 is a diagram for explaining the difference information table 115. The difference information table 115 is similar to the difference information table 115 shown in Fig. 4, except that importance 115j has been added as a column for storing information. Information indicating the importance of the difference (in this example, either low, medium, or high) is stored in importance 115j.

[0227] 29 is a diagram illustrating an importance table 2900. The importance table 2900 is information indicating criteria for determining the importance of a defective difference, and is included in the database 112 stored in the storage device 110. As shown in FIG. 29, the importance table 2900 includes, as columns for storing information (values), an ID 2901, a content type 2902, a difference type 2903, and an importance 2904. In the importance table 2900, information corresponding to each column relating to the importance of the difference is associated with one another and stored as row-by-row information (records).

[0228] Specifically, ID 2901 stores an identification number for identifying importance information indicated by a row (record) of this table. Content type 2902 stores the content type. Difference type 2903 stores the difference type. Importance 2904 stores information indicating the importance of the content type and difference type (in this example, either low, medium, or high).

[0229] 30 shows an importance setting screen 3000 for creating the importance table 2900. The importance setting screen 3000 is a tabular GUI screen, and each cell has an input area for inputting information indicating the importance. The user can register the importance of the content type and difference type in the importance table 2900 by inputting the information indicating the importance in the input area via the operation device.

[0230] <Specific operation> The automatic screen operation test support device 100 according to the fifth embodiment executes the processing flow of Fig. 31 instead of the processing flow of Fig. 13. Fig. 31 is a flowchart showing the processing flow of the defect difference check processing executed by the defect difference check unit 111b of the automatic screen operation test support device 100 according to the fifth embodiment.

[0231] The processing flow in Figure 31 is the same as the processing flow in Figure 13, except that step 1350 in the flowchart in Figure 13 is replaced with step 3110. Therefore, the following description will focus on this different step 3110.

[0232] When the defective difference check unit 111b proceeds to step 3110, it determines the determined difference information as a problematic difference (defective difference), stores a value of "1" in the defect column of the difference information table 115, and stores (registers) the difference information in the corresponding row. Furthermore, the defective difference check unit 111b determines the importance based on the difference information and the importance table 2900. For example, if the content type of the determined difference information is an image and the difference type is size, the defective difference check unit 111b determines the importance to be "small," which corresponds to the image and size in the importance table 2900. The defective difference check unit 111b stores the determined importance in the importance 115j of the difference information table 115. Thereafter, the defective difference check unit 111b proceeds to step 1355.

[0233] <Output screen> 32 shows a defect difference display screen 3200 after the defect difference check. After the defect difference check, the defect difference check unit 111b displays the defect difference display screen 3200 on the display 160. The defect difference display screen 3200 includes an importance narrowing down button 3201 and a difference list table 3202.

[0234] The importance narrowing button 3201 is a button that is operated by the user to select one of "high," "medium," and "low" that are displayed as options. When the user operates the importance narrowing button to select one of "high," "medium," and "low," "all difference lists that include the selected "high," "medium," or "low" are set as the narrowing condition. The defect difference check unit 111b displays the difference list table 3202 by including in it a difference list that corresponds to the narrowing condition that was set by operating the importance narrowing button 3201.

[0235] <Effects> As described above, the automatic screen operation test support device 100 according to the fifth embodiment of the present invention achieves the same effects as those of the first embodiment. The automatic screen operation test support device 100 according to the fifth embodiment can analyze the importance of differences based on attribute information of the differences extracted and determined by the defective difference check process, and select difference information according to the importance set by the user and output it to the screen.

[0236] <<Sixth Embodiment>> An automatic screen operation test support device 100 according to a sixth embodiment of the present invention will be described. The automatic screen operation test support device 100 according to the sixth embodiment differs from the automatic screen operation test support device 100 according to the first embodiment only in the following points.

[0237] The automatic screen operation test support device 100 according to the sixth embodiment is configured to allow the user to set criteria for determining whether the differences generated by the automatic screen operation test are identical differences during the non-fault list creation process.

[0238] The following description will focus on this difference.

[0239] FIG. 33 is a diagram illustrating a judgment criterion table 3300. The judgment criterion table 3300 is included in the database 112 stored in the storage device 110. As shown in FIG. 33, the judgment criterion table 3300 includes ID 3301, name 3302, and content 3303 as columns for storing information (values). In the judgment criterion table 3300, information corresponding to each column regarding the judgment criteria for determining whether or not the difference is identical is associated with each other and stored as information (records) on a row-by-row basis. Specifically, ID 3301 stores an identification number for identifying the judgment criterion information indicated in a row (record) of this table. Name 3302 stores the name of the judgment criterion. Content 3303 stores the content of the judgment criterion. For example, the content corresponding to the first judgment criterion is stored as "if the difference in coordinate values ​​is within the tolerance of 5 pixels, the difference is considered to be identical."

[0240] Fig. 34 is a diagram illustrating a judgment criterion input screen 3400. As shown in Fig. 34, the judgment criterion input screen 3400 includes a name input field 3401, a judgment criterion content input field 3402, and a register button 3403. When the register button 3403 is operated with the name of the judgment criterion input in the name input field 3401 and the content of the judgment criterion input in the judgment criterion content input field 3402, the input name and content of the judgment criterion are registered in the judgment criterion table 3300.

[0241] <Specific operation> The automatic screen operation test support device 100 according to the sixth embodiment executes the processing flow of Fig. 35 instead of the processing flow of Fig. 12. Fig. 35 is a flowchart showing the processing flow of difference information discrimination and DB registration processing executed by the non-fault list creation unit 111a of the automatic screen operation test support device 100 according to the sixth embodiment.

[0242] The processing flow in Figure 35 is the same as the processing flow in Figure 12, except that the processing in step 1235 in the flowchart in Figure 12 is replaced with step 3505, and the processing in step 1245 is replaced with step 3510. Therefore, the following explanation will focus on this different step 3505.

[0243] In step 3505, the non-fault list creating unit 111a determines whether the non-fault differential information table 114 contains the same non-fault differential information as the differential information table (B) or non-fault differential information that satisfies the same criterion.

[0244] If the non-bad differential information table 114 does not contain any non-bad differential information that is the same as the differential information table (B) or any non-bad differential information that meets the same judgment criteria, the non-bad list creation unit 111a judges ``NO'' in step 3505 and proceeds to step 1240, performs the processing of step 1240 described above, and then proceeds to step 3595.

[0245] If the non-defective difference information table 114 contains non-defective difference information that is the same as that in the difference information table (B) or non-defective difference information that satisfies the same judgment criterion, the non-defective list creation unit 111a judges as "YES" in step 3505 and proceeds to step 3510, where it increments by "1" the value of the number of occurrences of the same non-defective difference information (row (record)) or non-defective difference information (row (record)) that satisfies the same judgment criterion) in the already registered difference information table (B). Thereafter, the non-defective list creation unit 111a proceeds to step 3595 and temporarily ends this processing flow.

[0246] <Effects> As described above, the automatic screen operation test support device 100 according to the sixth embodiment of the present invention achieves the same effects as those of the first embodiment. In the automatic screen operation test support device 100 according to the sixth embodiment, in the non-fault list creation process, the user can set a criterion for determining whether or not differences generated by the automatic screen operation test are identical differences.

[0247] <<Seventh Embodiment>> An automatic screen operation test support device 100 according to a seventh embodiment of the present invention will be described. The automatic screen operation test support device 100 according to the seventh embodiment differs from the automatic screen operation test support device 100 according to the first embodiment only in the following points.

[0248] The automatic screen operation test support device 100 according to the seventh embodiment is configured so that, in the defective difference check process, any criterion can be set to determine whether or not a difference generated by the automatic screen operation test is a non-defective difference.

[0249] The following description will focus on this difference.

[0250] FIG. 36 is a diagram illustrating a non-faulty difference determination definition table 3600. The non-faulty difference determination definition table 3600 is included in the database 112 stored in the storage device 110. As shown in FIG. 36, the non-faulty difference determination definition table 3600 includes ID 3601, name 3602, and content 3603 as columns for storing information (values). In the non-faulty difference determination definition table 3600, information corresponding to each column regarding criteria for determining whether or not a difference that cannot be identified as a non-faulty difference is considered a non-faulty difference in the faulty difference check process is associated with each other and stored as row-based information (records). Specifically, ID 3601 stores an identification number for identifying the determination criteria information shown in a row (record) of this table. Name 3602 stores the name of the determination criterion. Content 3603 stores the content of the corresponding determination criterion. For example, the content corresponding to the first determination criterion may be, "If the content type of both differences is 'date', then the difference type of both differences is 'format'." " is stored. The content corresponding to the second criterion is "If the content type of both differences is an image and the difference type is size, the percentage (%) indicating the difference in image size between both differences is within a predetermined threshold." The content corresponding to the third criterion is "If the content type of both differences is an image and the difference type is color, the difference in RGB values ​​between both differences is within a predetermined threshold."

[0251] In the non-bad difference determination definition table 3600, the name and definition (content) of the determination criterion inputted via the determination criterion input screen similar to that of FIG. 34 are registered.

[0252] The automatic screen operation test support device 100 according to the seventh embodiment executes the processing flow of Fig. 37 instead of the processing flow of Fig. 13. Fig. 37 is a flowchart showing the processing flow of the defect difference check processing executed by the defect difference check unit 111b of the automatic screen operation test support device 100 according to the seventh embodiment.

[0253] The processing flow in Fig. 37 is the same as the processing flow in Fig. 13 except that step 3705 is added between step 1300 and step 1305 in the flowchart in Fig. 13, and step 3710 is added between step 1340 and step 1350. Therefore, the following will only explain these different steps 3705 and 3710, and will not explain the processing in the other steps.

[0254] 37, the defective difference check unit 111b starts processing at step 3700 and proceeds to step 3705, where it reads the judgment criteria set by the user. Thereafter, the defective difference check unit 111b executes the processing of steps 1305 to 1335 described above, and then proceeds to step 1340, where the defective difference check unit 111b determines whether or not non-defective difference information that is the same as the difference information determined at step 1335 is present in the non-defective difference information table 114. Note that, as described above, the difference information and the non-defective difference information being the same means that the screen information ID is the same, the coordinate information is the same, the content type is the same, and the difference type is the same.

[0255] If the non-faulty difference information table 114 contains the same non-faulty difference information as the difference information determined in step 1335 , the faulty difference check unit 111 b determines “YES” in step 1340 and proceeds to step 3710 .

[0256] When the defective difference check unit 111b proceeds to step 1340, it determines whether the determined difference information and the non-defective difference information that is the same as the determined difference information satisfy the criteria set by the user. At this time, the defective difference check unit 111b also compares the difference contents (contents at the time of execution).

[0257] If the determined difference information and the non-faulty difference information that is the same as the determined difference information satisfy the judgment criteria set by the user, the faulty difference check unit 111b judges ``YES'' in step 3710 and proceeds to step 1345, performs the processing of step 1345 described above, and then proceeds to step 1355.

[0258] If the determined difference information and the non-bad difference information that is the same as the determined difference information do not satisfy the criteria set by the user, the bad difference check unit 111b determines "NO" in step 3710 and proceeds to step 1350, where it executes the processing of step 1350 described above, and then proceeds to step 1355. In this case, the screen information ID is the same, the coordinate information is the same, the content type is the same, and the difference type is the same, but the content of the difference does not satisfy the allowable range of the criteria, so it is determined to be a bad difference.

[0259] <Effects> As described above, the automatic screen operation test support device 100 according to the seventh embodiment of the present invention achieves the same effects as the first embodiment. In the defective difference check process, the automatic screen operation test support device 100 according to the seventh embodiment allows the user to set criteria for determining whether a difference generated by an automatic screen operation test is the same as a non-defective difference in the non-defective difference information table 114. As a result, in the defective difference check process, the automatic screen operation test support device 100 according to the seventh embodiment can determine, as a defective difference, a difference whose attribute information is the same as that of a non-defective difference recorded in the non-defective difference information table 114 but whose execution content is significantly different. Therefore, the automatic screen operation test support device 100 according to the seventh embodiment can extract defective differences with greater accuracy.

[0260] <<Modifications>> The present invention is not limited to the above-described embodiments, and various modifications can be adopted within the scope of the present invention. Furthermore, the above-described embodiments can be combined with each other without departing from the scope of the present invention. [Explanation of symbols]

[0261] 100...automatic screen operation test support device, 110...storage device, 111...program, 111a...non-defective list creation unit, 111b...defective difference check unit, 112...database, 113...screen information table, 114...non-defective difference information table, 115...difference information table, 130...CPU, 160...display, 1500...user confirmation screen, 1600...defective difference display screen

Claims

1. An automatic screen operation test support device including an information processing device having a storage device in which non-fault difference list data and difference information list data are stored, The information processing device includes: a first automatic screen operation test is executed a plurality of times to extract differences that have occurred in the first comparison target screen relative to the first comparison reference screen by comparing the first comparison reference screen and the first comparison target screen, which are acquired by performing automatic screen operations according to operation contents indicated by a specific scenario on each of the same screen systems for registering non-fault differences, which are the comparison reference and the comparison target; and a non-fault list creation process is executed to identify the extracted differences and record them in the non-fault difference list data as non-fault differences. a second automatic screen operation test is executed to extract differences that have occurred in the second comparison target screen relative to the second comparison reference screen by comparing a second comparison reference screen and a second comparison target screen obtained by performing automatic screen operations of the operation contents indicated by a scenario identical to the specific scenario for each of the screen system for registering non-defective differences as a comparison reference and the screen system for defect extraction as a comparison target, and the extracted differences are identified and recorded in the difference information list data, and a defective difference check process is executed to identify, based on the difference information list data and the non-defective difference list data, differences that are identical to the non-defective differences recorded in the non-defective difference list data in the difference information list data as non-defective differences, and to identify differences other than the non-defective differences identified from the difference information list data as defective differences; It was configured as follows: Automatic screen operation test support device.

2. 2. The automatic screen operation test support device according to claim 1, The information processing device includes: In the non-fault list creation process, attribute information of the difference including coordinate information of the difference, content type and difference type is determined and recorded in the non-fault difference list data; In the defective difference check process, attribute information of the difference including coordinate information of the difference, content type and difference type is determined and recorded in the difference information list data, and the non-defective difference in the difference information list data is identified based on the attribute information of the difference recorded in the non-defective difference list data and the attribute information of the difference recorded in the difference information list data. It was configured as follows: Automatic screen operation test support device.

3. 3. The automatic screen operation test support device according to claim 2, The information processing device includes: In the non-fault list creation process, the number of occurrences of the same difference that occurs when the first automatic screen operation test is executed a plurality of times is recorded in the non-fault difference list data, and based on the number of occurrences, it is determined whether or not to record the difference as the non-fault difference in the non-fault difference list data. It was configured as follows: Automatic screen operation test support device.

4. 4. The automatic screen operation test support device according to claim 3, The information processing device includes: In the non-fault list creation process, it is determined whether the differences are identical based on attribute information of the differences. It was configured as follows: Automatic screen operation test support device.

5. 5. The automatic screen operation test support device according to claim 4, The information processing device includes: In the non-fault list creation process, if the occurrence count is greater than a threshold count, the difference is recorded as the non-fault difference in the non-fault difference list data, and if the occurrence count is equal to or less than the threshold count, the difference is recorded as a difference excluded from the non-fault differences in the non-fault difference list data. It was configured as follows: Automatic screen operation test support device.

6. 6. The automatic screen operation test support device according to claim 5, an operation device that is operated by a user to input information into the information processing device; The information processing device includes: setting the threshold number of times based on information input from the operation device; It was configured as follows: Automatic screen operation test support device.

7. 5. The automatic screen operation test support device according to claim 4, an operation device that is operated by a user to input information into the information processing device; The information processing device includes: setting a determination criterion for determining whether or not the differences are the same in the non-failure list creation process based on the information input from the operation device; It was configured as follows: Automatic screen operation test support device.

8. 3. The automatic screen operation test support device according to claim 2, The information processing device includes: In the defective difference check process, among the differences in the difference information list data that cannot be identified as the non-defective differences, differences that satisfy a specific judgment criterion are identified as the non-defective differences. It was configured as follows: Automatic screen operation test support device.

9. 9. The automatic screen operation test support device according to claim 8, The information processing device includes: In the defective difference check process, among the differences that cannot be identified as the non-defective differences, if the difference in attribute information of the difference with respect to the difference recorded in the non-defective difference list data is only the coordinate information and the deviation of the coordinate information is equal to or less than a predetermined threshold, the difference is determined to be a difference that satisfies the specific judgment criterion and is identified as the non-defective difference. It was configured as follows: Automatic screen operation test support device.

10. 9. The automatic screen operation test support device according to claim 8, an operation device that is operated by a user to input information into the information processing device; The information processing device includes: setting the specific judgment criteria based on information input from the operation device; It was configured as follows: Automatic screen operation test support device.

11. 2. The automatic screen operation test support device according to claim 1, a display device capable of displaying an image; an operation device that is operated by a user to input information into the information processing device; Equipped with The information processing device includes: In the defective difference check process, attribute information of the differences recorded in the difference information list data that cannot be identified as non-defective differences is compared with attribute information of the non-defective differences recorded in the non-defective difference list data, and information indicating the differences that are difficult to determine as non-defective differences is displayed on the display device based on the comparison result; Identifying a difference that is difficult to determine as a non-defective difference as either the defective difference or the non-defective difference based on information input from the operation device. It was configured as follows: Automatic screen operation test support device.

12. 2. The automatic screen operation test support device according to claim 1, a display device capable of displaying an image; The information processing device includes: In the defective difference check process, the specified defective difference is selected from the difference information list data, and an image including information indicating the selected defective difference is displayed on the display device. It was configured as follows: Automatic screen operation test support device.

13. 2. The automatic screen operation test support device according to claim 1, a display device capable of displaying an image; The information processing device includes: In the defect difference check process, determining the importance of the extracted defective difference based on attribute information of the defective difference extracted by the comparison of the differences in the second automatic screen operation test and specific importance judgment criteria, recording the importance in the difference information list data, and displaying an image including information indicating the importance on the display device; It was configured as follows: Automatic screen operation test support device.

14. 14. The automatic screen operation test support device according to claim 13, an operation device that is operated by a user to input information into the information processing device; The information processing device includes: setting the specific importance determination criteria based on information input from the operation device; It was configured as follows: Automatic screen operation test support device.

15. An automatic screen operation test support method using an information processing device having a storage device in which non-fault difference list data and difference information list data are stored, By the information processing device, a first automatic screen operation test is executed a plurality of times to extract differences that have occurred in the first comparison target screen relative to the first comparison reference screen by comparing the first comparison reference screen and the first comparison target screen, which are acquired by performing automatic screen operations according to operation contents indicated by a specific scenario on each of the same screen systems for registering non-fault differences, which are the comparison reference and the comparison target; and a non-fault list creation process is executed to identify the extracted differences and record them in the non-fault difference list data as non-fault differences. a second automatic screen operation test is executed to extract differences that have occurred in the second comparison target screen relative to the second comparison reference screen by comparing a second comparison reference screen and a second comparison target screen obtained by performing automatic screen operations of the operation contents indicated by a scenario identical to the specific scenario for each of the screen system for registering non-defective differences as a comparison reference and the screen system for defect extraction as a comparison target, and the extracted differences are identified and recorded in the difference information list data, and a defective difference check process is executed to identify, based on the difference information list data and the non-defective difference list data, differences that are identical to the non-defective differences recorded in the non-defective difference list data in the difference information list data as non-defective differences, and to identify differences other than the non-defective differences identified from the difference information list data as defective differences; A method for supporting automated screen operation testing.

Images