Test scenario creation support system, test scenario creation support method, and test scenario creation support program

Abstract

To efficiently create a test scenario to be used for testing an application by automatic operation means which automatically operates the application.SOLUTION: A test scenario creation support system includes: a definition management table formed by registering definition names in association with control information including control names and the types thereof; and scenario creation means which provides a scenario creation screen, displays, on the basis of the definition management table, a list of definitions on the scenario creation screen, displays a screen layout for a definition name selected by a scenario creator from the list, displays a list of controls which can be operated in the screen layout, displays selection candidates for operation for control selected by the scenario creator from the list of controls, and creates a test scenario including the definition name, the control, and operation content thereof on the basis of the selections made by the scenario creator in the selection candidates for operation.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a test scenario creation support system, a test scenario creation support method, and a test scenario creation support program.

Background Art

[0002] For example, in a rapidly changing business environment, in order to provide valuable business solutions, it is necessary to release quickly, and in order to cope with changes in the external environment where the speed of evolution of the OS, browsers, etc. is accelerating, the efficiency of business application development and regression testing is required. Conventionally, as a system for creating an operation scenario of an application, for example, there is Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the above Patent Document 1, there is no description regarding efficiently creating a test scenario for an automatic operation means (for example, RPA) that automatically operates an application to perform a test of the application.

[0005] The present invention has been made in view of the above, and an object thereof is to provide a test scenario creation support system, a test scenario creation support method, and a test scenario creation support program capable of efficiently creating a test scenario for an automatic operation means that automatically operates an application to perform a test of the application.

Means for Solving the Problems

[0006] In order to solve the above-described problems and achieve the object, the present invention is a test scenario creation support system including a control unit and assisting in the creation of a test scenario executed by an automatic operation means of an application. The control unit is configured to be able to access a definition management table in which a definition name is associated with and registered together with control information including a control name and its type. providing a scenario creation screen, and based on the definition management table, on the scenario creation screen displaying a list of definitions, displaying a screen layout for the definition name selected by the scenario creator from the list of the definitions, displaying a list of controllable controls in the screen layout, displaying selection candidates for operations for the controls selected by the scenario creator from the list of the controls, and creating a test scenario including a definition name, a control, and its operation content based on the selection of the operation by the scenario creator among the selection candidates for the operations, and registering it in a database.

[0007] Also, according to one aspect of the present invention, the list of the controls may include controls for a common operation target.

[0008] Also, according to one aspect of the present invention, in the definition management table, in addition to the definition name and the control information, logic flow information including an ID, a name, and a group of flow elements connecting actions for each logic flow, and action information including an ID, a name, an action type, and settings for each action are associated and registered. The scenario creation means may present candidates for the next operation based on the operation selected immediately before on the scenario creation screen based on the definition management table.

[0009] Also, according to one aspect of the present invention, the automatic operation means may include RPA.

[0010] Also, according to one aspect of the present invention, the test scenario creation support system may include a low-code base or a no-code base.

[0011] Also, according to one aspect of the present invention, the application may include a business application.

[0012] In addition, in order to solve the above-described problems and achieve the object, the present invention is a test scenario creation support method for supporting the creation of a test scenario executed by an automatic operation means of an application executed by an information processing system including a control unit, wherein the control unit is configured to be able to access a definition management table in which a definition name is associated and registered with control information including a control name and its type, provide a scenario creation screen executed in the control unit, display a list of definitions on the scenario creation screen based on the definition management table, display a screen layout for the definition name selected by a scenario creator from the list of the list, display a list of controls operable in the screen layout, display selection candidates for operations for the control selected by the scenario creator from the list of the controls, and create a test scenario including a definition name, a control, and its operation content based on the selection of the operation of the scenario creator among the selection candidates for the operations, and register it in a database, characterized by including a scenario creation step.

[0013] Also, in order to solve the above-described problems and achieve the object, the present invention is a test scenario creation support program for assisting in the creation of a test scenario executed by an automatic operation means of an application for an information processing system including a control unit, wherein the control unit is configured to be able to access a definition management table in which a definition name is registered in association with control information including a control name and its type, and in the control unit, a scenario creation screen is provided, and based on the definition management table, in the scenario creation screen, a list of definitions is displayed, a screen layout for the definition name selected by the scenario creator from the list of the list is displayed, a list of controls operable in the screen layout is displayed, a selection candidate for an operation for the control selected by the scenario creator from the list of the controls is displayed, and based on the selection of the operation of the scenario creator in the selection candidate for the operation, a test scenario including a definition name, a control, and its operation content is created and registered in a database. The test scenario creation support program is characterized by this.

Effect of the Invention

[0014] According to the present invention, there is an effect that it becomes possible to efficiently create a test scenario for an automatic operation means that automatically operates an application to perform a test of the application.

Brief Description of the Drawings

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Figure 38

Figure 39

Figure 40A

Figure 40B

Figure 40C

Figure 41

Figure 42

Figure 43A

Figure 43B

[0016] Embodiments of a test scenario creation support system, a test scenario creation support method, and a test scenario creation support program according to the present invention will be described in detail below with reference to the drawings. Note that the present invention is not limited by the present embodiment.

[0017] [1. Overview] The overview of the present invention will be described in the order of (Background), (Problems), and (Solutions).

[0018] (Background) In recent years, low-code development tools have attracted attention as tools that can easily develop applications. In addition, the application areas of low-code development tools have penetrated into the core systems of mission-critical companies. Under such circumstances, a mechanism for maintaining the quality of applications created with low-code development tools has become essential. As a means thereof, regression testing using RPA has attracted attention.

[0019] (Problems) However, in the conventional method, when testing business applications, there are the following problems (1) to (2).

[0020] (1) There is a problem that leakage occurs in the creation of test patterns. Specifically, pattern leakage occurred because testing was performed after creating test patterns from the design document. Therefore, test code was generated and executed based on the design document. Although test code could be automatically generated for routine processes, non-routine processes had to be created manually.

[0021] (2) There is a problem that the test itself is costly and it is difficult to perform repeated tests. Specifically, when comprehensively testing a business application, it is risky and costly to clarify the tests that should be done manually and actually execute them. With existing methods, for routine specifications, test code could be created by reading the design document and automated tests could be performed, reducing risks and costs. However, when testing non-routine specifications (areas where it is difficult to interpret the structure of the design document), it is costly to create test scenarios manually and then perform the tests, and it is difficult to perform repeated tests.

[0022] (Solution) In this embodiment, the low-code platform holds all the property information of the controls to be operated and the processing logic within the events, enabling the viewing of the screen design and the setting of controls and operation information without executing the target job. Attention was paid to this point.

[0023] In this embodiment, when an automatic operation means (for example, RPA) creates a test scenario for executing an E2E regression test of an application, it is made possible to create it efficiently by using the information on the low-code platform.

[0024] Specifically, the test scenario creation support system of this embodiment is equipped with a function for selecting operable controls, a function for presenting operations for the controls to be operated, and a function for proposing the next operation from the previous operation, enabling the efficient creation of test scenarios.

[0025] [2. Configuration] An example of the configuration of the test scenario creation support system 100 according to this embodiment will be described with reference to FIG. 1. The test scenario creation support system 100 can be configured with a low-code platform, for example. Note that it may be configured with a no-code platform. FIG. 1 is a block diagram showing an example of the configuration of the test scenario creation support system 100. The test scenario creation support system 100 is a system for creating test scenarios used by scenario creators. The test scenario creation support system 100 is equipped with functions described in [3. Specific examples of processing] to be described later, and is configured to be able to execute the processing described by these.

[0026] The test scenario creation support system 100 may be an information processing system such as a workstation, a stationary information processing system such as a desktop personal computer, or a commercially available notebook personal computer.

[0027] The test scenario creation support system 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each unit included in the test scenario creation support system 100 is communicably connected via an arbitrary communication path.

[0028] The communication interface unit 104 communicably connects the test scenario creation support system 100 to the network 300 via a communication system such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the test scenario creation support system 100 and other devices such as terminals (not shown) used by scenario creators and testers and the server 200, and is, for example, the Internet or a LAN (Local Area Network). Note that the definition management table 106a, the development application DB 106b, the automatic operation unit 102a, and the application 102c to be described later may be installed in other systems.

[0029] An input / output interface unit 108 is connected to an input system 112 and an output system 114. In addition to a monitor (including a home TV), a speaker or a printer can be used for the output system 114. In addition to a keyboard, a mouse, and a microphone, a monitor that collaborates with the mouse to realize a pointing device function can be used for the input system 112. In the following, the output system 114 may be described as the monitor 114, and the input system 112 may be described as the keyboard 112 or the mouse 112.

[0030] The storage unit 106 stores various databases, tables, files, and the like. A computer program for giving instructions to the CPU (Central Processing Unit) in cooperation with the OS (Operating System) to perform various processes is recorded in the storage unit 106. As the storage unit 106, for example, a memory system such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk system such as a hard disk, a flexible disk, and an optical disk can be used.

[0031] The storage unit 106 includes a definition management table 106a and a development application DB 106b. The definition management table 106a can be configured by, for example, a table that registers by associating a definition ID, a definition name, control information, pull-down assignment information, pull-down information, logic flow information, action information, and event assignment definition information.

[0032] The control information may include an ID, a control name, and its type. The logic flow information may include an ID, a name, and a group of flow elements connecting actions for each logic flow. The action information may include an ID, a name, an action type, and settings for each action.

[0033] The development application database 106b is a database for storing data such as test scenarios.

[0034] The control unit 102 is a CPU or the like that comprehensively controls the test scenario creation support system 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processes based on these stored programs.

[0035] Functionally conceptually, the control unit 102 includes an automatic operation unit 102a, a scenario creation unit 102b, and an application 102c.

[0036] The automatic operation unit 102a performs an automatic operation on the application 102c according to the test scenario registered in the development application database 106b to perform a regression test. The automatic operation unit is, for example, an RPA execution program (RPA tool). RDA (Robotic Desktop Automation) or the like may be used instead of RPA.

[0037] The scenario creation unit 102b provides a scenario menu screen and a scenario creation screen for creating a test scenario in response to a request from the terminal of the scenario creator, creates a test scenario according to the operation of the scenario creator on the scenario creation screen, and stores it in the development application database 106b.

[0038] Specifically, based on the definition management table 106a, the scenario creation unit 102b displays a list of definitions on the scenario creation screen, displays the screen layout for the definition name selected by the scenario creator from the list, displays a list of controls operable in the screen layout, displays selection candidates for operations for the controls selected by the scenario creator from the list of controls, creates a test scenario including the definition name, the control, and the operation content based on the selection of the scenario creator's operation from the selection candidates for the operation, and registers it in the development application DB 106b.

[0039] The list of controls may include controls for common operation targets.

[0040] The scenario creation unit 102b may present candidates for the next operation from the operation selected immediately before based on the definition management table 106a on the scenario creation screen.

[0041] The application 102c is, for example, one or more business applications. Although the application is stored in the storage unit 106, the application stored in the storage unit 106 that is executed by the control unit 102 is conceptually represented as the application 102c of the control unit 102 in terms of function.

[0042] [3. Specific Example] A specific example of the processing of the test scenario creation support system 100 (scenario creation unit 102b) of the present embodiment will be described with reference to FIGS. 2 to 41. FIGS. 2 to 41 are diagrams for explaining a specific example of the processing of the test scenario creation support system 100 of the present embodiment.

[0043] [3-1. Overall Concept Image of Scenario Creation] Here, referring to FIGS. 2 to 4, the overall overview image of test scenario creation of the test scenario creation support system 100 according to the present embodiment will be described. FIG. 2 is a diagram for explaining the outline of test scenario creation. (A) shows an example display of a scenario creation screen, and (B) shows an example of a test scenario to be created. The scenario creator creates a scenario on the provided scenario creation screen.

[0044] As shown in FIG. 2(A), the scenario creation screen includes a scenario CD, a setting field for the scenario name, a scenario setting area, and a switching button for switching the display between the scenario setting area and the scenario execution area. When "Settings" is selected, the scenario setting area is displayed, and when "Execution" is selected, the scenario execution area is displayed. In the example shown in the figure, "Settings" is selected and the scenario setting area is displayed.

[0045] When the scenario creator specifies the scenario CD and scenario name on the scenario creation screen, selects the operation target (control) on the scenario setting screen, and makes a selection of the operation, a test scenario corresponding to the operation content is registered in the development application DB 106b.

[0046] As shown in FIG. 2(B), the test scenario includes a scenario CD, a scenario name, and RPA operation content (actions). The RPA operation content includes starting the screen, page operations, screen shots, etc.

[0047] In the example shown in the figure, the scenario CD is "S-01-001-0020", the scenario name is "Whether an error occurs when an unpermitted character is entered in the customer name of the customer master", and the RPA operation content is: start the screen: customer master maintenance (start the customer master maintenance screen), basic page operation: enter text in the text customer name, screen shot: file name S-01-001-00XX-1.png (take a screen shot and set the file name to S-01-001-00XX-1.png).

[0048] Figure 3 is a diagram for explaining the execution of a test scenario. Figure 3(A) shows an example of the display of the scenario execution area on the scenario creation screen, and Figure 3(B) shows an example of the screen of the application to be automatically operated. The test scenario is executed by the RPA execution program (automatic operation unit 102a) when a tester or scenario creator presses the execution instruction button in the scenario execution area of the scenario creation screen, or when the batch manager issues an execution instruction automatically.

[0049] For example, when a tester or scenario creator presses the execution button on the scenario screen in Figure 3(A) to press the execution instruction button to instruct execution, or when the batch manager instructs execution, the RPA execution program interprets the scenario content registered in the development application DB and automatically operates the application (Figure 3(B)) on the low-code execution platform.

[0050] Figure 4 is a diagram for explaining the basic operations during scenario creation. Here, the operations for creating a test scenario for checking whether the corrected registration of the customer name in the customer master is correctly performed are explained. As shown in (A), the screen of the customer master maintenance (list) is displayed, and as the correction target, for example, the details with customer CD = C001 are selected and the correction button is clicked. As shown in (B), the selected data is displayed, and as shown in (C), the customer name is changed and the changed content is registered with the registration button, and as shown in (D), it is confirmed that the customer name is reflected.

[0051] [3-2. Test Scenario Creation] With reference to FIGS. 5 to 19, the creation of test scenarios will be described. FIG. 5 is a diagram showing an example of the display of a scenario menu screen and a scenario creation screen, where (A) shows the scenario menu screen and (B) shows an example of the display of the scenario creation screen. When a scenario creator creates a new scenario, a new scenario is created from the scenario menu screen. On the scenario menu screen, there is a button for creating a new scenario (the "New Scenario Button"), and by clicking this button, the scenario creation screen is launched and scenario creation becomes possible.

[0052] As shown in FIG. 5(A), the scenario menu screen displays a scenario list showing the title, last updater, and update date and time of the test scenarios registered in the development application DB106b, and a "New Scenario Button" for creating a new scenario. When creating a new scenario, pressing the "New Scenario Button" will display a scenario creation screen as shown in FIG. 5(B).

[0053] As shown in FIG. 5(B), the scenario creation screen includes a scenario CD, a setting field for the scenario name, a switching button for switching the display between the scenario setting area and the scenario execution area. When "Settings" is selected, the scenario setting area is displayed, and when "Execution" is selected, the scenario execution area is displayed. In the example shown in the figure, "Settings" is selected and the scenario setting area is displayed. At the time of new creation, an operation for automatically launching the screen is set. The operation for launching the screen is set according to the procedure originally shown as a dashed line in the figure.

[0054] The scenario creator sets the operations in the order in which the RPA actually executes.

[0055] First, as shown in FIG. 6, enter the scenario CD and scenario name. In the example shown in the figure, the scenario CD "S-01-001-0020" and the scenario name "Is the correction registration of the customer name in the customer master correct?" are entered. With reference to FIGS. 7 to 9, the setting of RPA operations (launching the screen, operating the screen) will be described.

[0056] (1) Select the definition to be operated on. FIG. 7 is a diagram for explaining the selection of the definition to be operated on. FIG. 7(A) is a diagram showing an example of the display of the scenario setting area on the scenario creation screen. FIG. 7(B) is a diagram showing an example of the definition names registered in the definition management table 106a (data such as control information, action information, and logic flow information is omitted).

[0057] In FIG. 7(A), in the scenario setting area, a list of all the definition names existing in the definition management table 106a (for example, customer master maintenance (list), customer master maintenance, customer search, customer master list, ···) is displayed as a list of options. Select the definition name of the definition to be operated on from the list. In this example, "customer master maintenance (list)" is selected.

[0058] (2) Based on the control information in the definition management table 106a from the selected definition (while retaining the definition ID in the background when selecting), create a screen layout and display it below the selected list. Hereinafter, the "screen layout" refers to the screen design created from the control information stored in the definition management table 106a.

[0059] FIG. 8 is a diagram showing an example of the display of the scenario setting area on the scenario creation screen. As shown in FIG. 8, below the selected definition name "customer master maintenance (list)", a screen layout "screen layout of customer master maintenance (list)" is created and displayed based on the control information in the definition management table 106a associated with the selected definition name.

[0060] (3) Set the content to be operated on (RPA operation). Here, select whether to operate on the control of the selected definition or perform other fixed operations. FIG. 9 shows a list of RPA operations that can be set, showing typical RPA operations, operation contents, and their explanations.

[0061] For example, the RPA operation "Launch Screen" is an RPA operation where the operation content is "Screen Operation" and the robot sets the screen to be launched first. The RPA operation "Operate Screen" is an RPA operation where the operation content is "Screen Operation" and the robot launches and transitions to another screen from the currently launched screen. The RPA operation "Basic Page Operation" is an RPA operation where the operation content is "Screen Operation" and the robot operates the controls within the specified definition. The RPA operation "Operate System Common Search Dialog" is an RPA operation where the operation content is "Screen Operation" and the robot operates the system common search dialog. The RPA operation "Pause" is an RPA operation where the operation content is "Other" and the robot execution is paused (put to sleep). The RPA operation "Screen Shot" is an RPA operation where the operation content is "Other" and the content of the screen is saved as an image.

[0062] Here, the creation of the operation scenario for the list screen will be skipped halfway, and the explanation will start from the creation of the scenario for operating the vendor master maintenance screen.

[0063] (Example of selecting operation content 1: Operating the controls within the screen) Here, the basic page operation will be explained as an RPA operation.

[0064] 1. Click the "Add Operation Button". Referring to Figure 10, the process when the "Add Operation" button is clicked in the scenario setting area will be explained.

[0065] Figure 10(A) is a diagram showing an example of the display of the scenario setting area. In the scenario setting area, as shown in Figure 10(A), on the left side, a "Add Operation" button and a "Start Screen" button are displayed, and on the right side, the selected definition and its screen layout are displayed. When the "Add Operation" button is clicked, an operation selection screen as shown in Figure 10(B) is displayed. On the operation selection screen, as operation contents, selections of "Screen Operation" and "Others" can be made, and as operations, selections of "Basic Page Operation", "Operate Screen", and "Operate Screen with Page ID Specified" can be made. Here, operating the controls within the definition is defined as "Basic Page Operation". Also, starting the operation of other definitions based on the low-code platform is defined as "Operate Screen".

[0066] 2. Select the control to be operated within the definition. Details will be described in the "Creation Assist Function (1)" mentioned later. Referring to Figure 11, the selection of the control to be operated within the definition will be described. Figure 11 is a diagram showing an example of the display of the scenario setting area when the operation content "Screen Operation" and the operation "Basic Page Operation" are selected on the operation selection screen of Figure 10(B).

[0067] As shown in Figure 11, in the scenario setting area, on the left side, "Please select a page operation" is displayed. On the right side, as a list of the operation target (control) list, the operable controls within the selected definition and the common controls of the system regardless of the definition settings are displayed.

[0068] In this example, as the operable controls within the selected definition "Trading Partner Master Maintenance", "Text Trading Partner Code Text", "Text Revision Date Text", "Text Trading Partner Name Text", and "Registration Button (Modify)" are displayed. Also, as the system common operable controls regardless of the definition settings, "Message Box Yes" and "Message Box No" are displayed. Hereinafter, the case where "Text Trading Partner Name Text" is selected will be described as an example.

[0069] 3.2. Describe the selection of operations due to the control selected. Details will be described in the "Creation Assist Function (2)" described later.

[0070] (Selection Operation Example 1: Perform text input) Referring to FIG. 12, Selection Operation Example 1 (perform text input) will be described. FIG. 12 shows an example display in the scenario setting area of FIG. 11 when "Text Trader Name Text" is selected as the operation target. As shown in FIG. 12, in the scenario setting area, on the right side, for the control selected by the operation target selection, display of operation selection candidates is performed and operation selection is possible. In this example, "Text input" is selected as the operation selection. Also, on the left side, a title combining the name of the operation selected by the operation selection with the name of the control selected by the operation target selection is displayed. In this example, the title "Perform text input for Text Trader Name Text" combining the operation target selection "Text Trader Name Text" and the operation selection "Text input" is displayed.

[0071] (Selection Operation Example 2: Click the control) Referring to FIGS. 13 and 14, Selection Operation Example 2 (click the control) will be described. FIG. 13 is a diagram showing an example display in the scenario setting area when a button or the like is selected and click is selected by the operation selection. In the example shown in FIG. 13, an example is shown when "Registration Button (Modify)" is selected by the operation target selection, "Click" is selected by the operation selection, and the title "Click the Registration Button (Modify)" is displayed.

[0072] FIG. 14 is a diagram showing an example display in the scenario setting area when using the assist function to set the next operation. Details will be described in the "Creation Assist Function (3)" described later. In the example shown in FIG. 14, in FIG. 13, when clicking the registration button (modify) is selected in the immediately preceding operation and "Click Yes in the message box" is presented as the next operation candidate and OK is selected, the case where the content is reflected in the scenario setting area is shown.

[0073] (Example 2 of operation content selection: Perform other fixed operations) Here, as RPA operations, screenshots, pauses, etc. will be described.

[0074] 1. Click the "Add operation button" in the scenario setting area. Referring to Figure 15, the processing when the "Add operation button" is clicked in the scenario setting area will be described.

[0075] Figure 15(A) is a diagram showing an example of the display of the scenario setting area. In Figure 15(A), when the "Add operation button" is clicked, an operation selection screen as shown in Figure 15(B) is displayed. On the operation selection screen, select the operation content "Other" and the operation "Screenshot".

[0076] 2. Perform the shooting settings for the screenshot. Figure 16 is a diagram showing an example of the display of the scenario setting area when the operation content "Other" and the operation "Screenshot" are selected on the operation selection screen of Figure 15(B).

[0077] As shown in Figure 16, in the scenario setting area, on the right side, set (input) the screenshot name and the confirmation content. In this example, by the scenario creator, the screenshot name "S-01-001-0020-1" and the confirmation content "Confirm that only the name of the business partner has been changed and registered" are set (input). With this setting, the screenshot is taken with the screenshot name + ".png" as the file name. Also, on the left side, a shooting icon and the title "File Name Screenshot Name + ".png"" are displayed.

[0078] The completed test scenario is saved in the development application DB106b. Figure 17 shows an example of the display of the scenario creation screen where the RPA operation settings are completed. By clicking the registration button on the scenario creation screen, a test scenario corresponding to the RPA operation settings on the scenario creation screen is created and saved in the development application DB106b.

[0079] Here, the playback icon indicates the startup and screen operations of the RPA operation. The screen icon indicates the basic page operations of the RPA operation. The shooting icon indicates the screenshot of the PRA operation. It expresses that the operation in the uppermost frame of the frame directly below the startup and screen operations of the screen is the RPA operation performed within that screen.

[0080] Figure 18 is a diagram showing an example of the data image of the test scenario to be registered. The test scenario is composed of a scenario CD, a scenario name, a start RPA operation key, and RPA operation contents (each RPA operation). In the example shown in Figure 18, the scenario CD is "S-01-001-0020", the scenario name is "Is the modification registration of the customer name in the customer master correct?", the RPA operation start key is "A1", and the RPA operation contents are "Start RPA operation key: A1", "Operation type: Start screen", "Screen type: Low-code base", "Target: Customer master maintenance (list) (definition ID)", "Child RPA operation keys: A11, A12, A13, B1, A14", ···.

[0081] The "child RPA operation key" is a list of RPA operation keys for the operations performed within the screen specified by the RPA operation key. It is controlled to be nested when drawn on the screen, and the processing order is performed in sequence from left to right.

[0082] After creating the scenario, an execution confirmation is performed. Figure 19 is a diagram showing an example of the display when "Execute" is selected on the scenario creation screen. As shown in Figure 19, in the scenario execution area of the scenario creation screen, an "execution instruction button", an "execution status update button", and the RPA operation contents are displayed. When the execution instruction button is pressed, the test scenario is executed by the RPA execution program. Also, when the "execution status update button" is pressed, the execution status can be confirmed. In the confirmation of the execution status, icons for successful execution or execution failure (system error occurs in the RPA operation) are displayed.

[0083] [3-3. Execution image of the test scenario] Referring to FIGS. 20 to 23, the execution image of the test scenario will be described. Here, an example of the scenario "Will it result in an error when entering characters on the reference date?" will be used for the description. FIG. 20 is a diagram for explaining the loading of the test scenario. In FIG. 20, when a scenario CD is specified on the scenario creation screen, using the scenario CD as a key, the RPA operation content of the test scenario is displayed in the scenario execution area from the development application DB106b. Then, when the "Execution Instruction Button" is pressed, the execution of the test scenario of the specified scenario CD is instructed to the RPA execution program, and the RPA execution program reads the test scenario of the specified scenario CD from the development application DB106b and performs processing according to the operation execution order of the test scenario.

[0084] Referring to FIG. 21, the startup of the screen will be described. FIG. 21 is a diagram for explaining the startup of the screen. In FIG. 21, the RPA execution program obtains the RPA operation key (in the example shown in the figure, "A1") specified in the start RPA operation key of the test scenario of the scenario CD instructed from the development application DB106b, reads the RPA operation content (RPA operation key: A1, operation type: startup of the screen, target: definition ID of the customer master maintenance (list)) set for the obtained RPA operation key, and operates the application (in the example shown in the figure, the customer master maintenance (list)) to start the screen.

[0085] Referring to FIG. 22, the operations within the screen will be described. FIG. 22 is a diagram for explaining the operations within the screen. In FIG. 22, the RPA execution program reads the RPA operation content of the test scenario of the scenario CD instructed from the development application DB106b (in the example shown in the figure, RPA operation key: A11, operation type: basic page operation, target: control ID of the text reference date, operation content: character input, value: a) and operates the application.

[0086] Referring to FIG. 23, the taking of a screen shot will be described. FIG. 23 is a diagram for explaining the taking of a screen shot. In FIG. 23, the RPA execution program reads the RPA operation content of the test scenario of the scenario CD instructed from the development application DB106b (in the example shown in the figure, RPA operation key: A12, operation type: screen shot, file name: S-01-001-0030-1, confirmation item: whether a date error is displayed), takes a screen shot of the screen, and creates a file of S-01-001-0030-1.png.

[0087] [3-4. Assist function for test scenario creation (1)] Referring to FIGS. 24 to 31, the assist function for test scenario creation (1) will be described. The objects of operations that can be performed by RPA use the control information (setting information on the low-code basis) in the definition management table 106a, and since it is predetermined, operable controls are presented.

[0088] In FIG. 24, (A) shows the scenario setting area of the scenario creation screen. (B) shows an image of the screen layout. The screen layout is composed of a master page (button group) and a placeholder. The "master page" is a page that groups functions common to the screen (button groups for data display, addition, modification, deletion, etc.). By inheriting the master page, the cost for settings at the inheritance destination can be reduced. Since the controls arranged on the master page cannot be changed at the inheritance destination, the operations are unified.

[0089] The "placeholder" is content for arranging controls unique to the inheritance destination at the inheritance destination. The placeholder is carried over to the inheritance destination screen side, and by arranging a control on the placeholder, the control arranged in the child element property of the placeholder is registered.

[0090] FIG. 25 is a diagram showing an example of the definition management table 106a. In the example of the definition management table 106a shown in FIG. 25, it has a definition ID, a definition name, control information, action information, logic flow information, and master page information (the definition ID of the master page associated with the definition). The control information of the definition selected from the definition management table 106a is acquired and set in the list of selections of the operation target in the scenario setting area of the scenario creation screen. The control information of the master page stores the control information common to a plurality of definitions. If there is a definition corresponding to the definition ID of the master page information, the control information thereof is also referred to.

[0091] In the example shown in the figure, the definition name "Trading Partner Master Maintenance" is associated with the master page information "Definition ID of the Master Maintenance Common Master Page". The control information of the definition name "Master Maintenance Common Master Page" is control element 1 (ID: XXXM1···, name: Registration Button (Modification), type: Button), control element 2 (placeholder) (ID: XXXP1···), ···. The control information of the definition name "Trading Partner Master Maintenance" is control element 1 (ID: XXXP1···, child elements: XXXX1···, child elements: XXXX2···), control element 2 (ID: XXXX1···, name: Text Trading Partner Code, type: String Text Box), control element 3 (ID: XXXX2···, name: Text Revision Date, type: Date Text Box). The ID: XXXP1··· of the control element 2 (placeholder) of the "Master Maintenance Common Master Page" is associated with the ID: XXXP1··· of the control element 1 of the control information of the "Trading Partner Master Maintenance".

[0092] Referring to FIGS. 26 to 31, the case of adding the setting information of the definition management table 106a and adding an operable target will be described.

[0093] FIG. 26 shows a list of representative operable objects, showing the control and the operable objects. As shown in FIG. 26, typically, in the case of the control "text box", the operable object is "text".

[0094] Referring to FIGS. 27 and 28, the case of adding an operable object "pull-down button" to the control "text box" will be described.

[0095] FIG. 27 is a diagram showing an example of the definition management table 106a when a pull-down function is set for the text box. The definition management table 106a includes, in addition to control information, pull-down assignment information and pull-down information. Those in which the ID that is a control element of the control information matches the control ID that is a pull-down assignment element of the pull-down assignment information are determined as those with which the pull-down has been assigned.

[0096] In the example shown in the figure, for the definition name "trading partner master maintenance", the control information is control element 1 (ID: XXX1, name: text trading partner code, type: string text box), the pull-down assignment information is pull-down assignment element 1 (control ID: XXX1, pull-down ID: SSS1), and the pull-down information is pull-down element 1 (pull-down ID: SSS1, pull-down name: trading partner suggestion).

[0097] In FIG. 28, when the function of the pull-down button is added to the control "text box" (FIG. 28(A)), as shown in FIG. 28(B), in the scenario setting area of the scenario creation screen, "pull-down button" is displayed in the selection list of the operation target. The pull-down button is a button attached to a selection-type control as shown in FIG. 28(C). By pressing this button, a list of predetermined options can be displayed.

[0098] Referring to FIGS. 29 and 30, the case of adding "calendar" as an operable object to the control "date text box" will be described.

[0099] FIG. 29 is a diagram showing an example of the definition management table 106a when a calendar function is set in the date text box. In the example shown in this figure, for the definition name "Trading Partner Master Maintenance", the control information is control element 1 (ID: XXX2, name: Text Revision Date, type: text box, calendar display: TRUE).

[0100] In FIG. 30, when a calendar function is added to the control "text box" (FIG. 30(A)), as shown in FIG. 30(B), in the scenario setting area of the scenario creation screen, "Calendar" is displayed in the selection list of the operation target.

[0101] FIG. 31 shows an example of a list of controls to which RPA operation targets can be added by setting, showing the controls, settings, and operable targets. In FIG. 31, for example, in addition to the above, "Text" can be added as an operable target to the control "single select box", and a "download button" can be added as an operable target to the control "file upload".

[0102] [3-5. Assist Function for Test Scenario Creation (2)] Referring to FIGS. 32 to 36, the assist function (2) for test scenario creation will be described. The targets of operations that can be performed by RPA use the control information (settings information on the low-code platform) of the definition management table 106a, and since they are predetermined, the operations available for each control are presented. FIG. 32 shows an example of the display of the scenario setting area of the scenario creation screen.

[0103] FIG. 33 is a diagram showing an example of a list of operations operable on a control. As shown in FIG. 33, typically, for the control "label cell of the detail control", the operable operation is "click".

[0104] Referring to FIGS. 34 and 35, the case of adding "drag and drop" as an operable operation to the control "label cell of the detail control" will be described.

[0105] In FIG. 34, (B) shows an example of the designer setting screen. The designer setting screen is a screen for application development separately used by developers, and the settings regarding the behavior of the detail control are stored in an item that permits row rearrangement by drag and drop, which is a control element of the control information. Referring to the content, a selection option for the drag and drop operation is added to the control information.

[0106] (C) is a diagram showing an example of the definition management table 106a when the drag and drop pull function is set for the label cell of the detail control. The content set on the above-mentioned designer setting screen is set in the control information. In the example shown in this figure, for the definition name "trading partner master maintenance", the control information is control element 1 (ID: XXX3, name: detail control, type: detail control, permitting row rearrangement by drag and drop: TRUE), control element 2 (ID: XXX4, name: label trading partner name, type: string label cell, primary key: FALSE).

[0107] (D) shows an example of the drag and drop operation on the screen when the test scenario is executed.

[0108] FIG. 35 shows an example of the display of the scenario setting area of the scenario creation screen. In FIG. 35(A), when the drag and drop function is added to the control "label cell of the detail control", "drag and drop" is displayed in the selection candidates of the operation. Note that, as shown in FIG. 35(B), since the drag and drop operation operates on the control arranged in the detail control rather than on the detail control itself, it is not displayed in the selectable options available for the detail control itself.

[0109] FIG. 36 shows an example of a list of controls to which RPA operations are added according to settings, showing the controls, settings, and operable targets. In FIG. 36, for example, in addition to the above, an operation of "drag and drop" can be added to the control "text cell of the detail control".

[0110] [3-6. Assistive Function for Test Scenario Creation (3)] Referring to FIGS. 37 to 41, the assistive function for test scenario creation (3) will be described. The assistive function for test scenario creation (3) describes a function that assists in creating the next operation after a specific operation.

[0111] FIG. 37 is a diagram for explaining general settings of RPA operations. In the scenario setting area of the scenario creation screen shown in FIG. 37, as shown in (A), press the "button to add an operation", and select the operation content and operation on the selection screen shown in (B) to set the RPA operation.

[0112] In the assistive function (3), since the setting information on the low-code platform is used, the logic flow information assigned to the previous operation is analyzed, and candidates for the next operation content are displayed. Here, the processing when the registration button is pressed will be described as an example.

[0113] FIG. 38 is a diagram for explaining the processing when the registration button is pressed. Referring to FIG. 38, the processing when the registration button is pressed will be described. First, pre-registration processing is executed (step S1), and a confirmation message for selecting "Yes" or "No" is displayed (step S2). If the "Yes" button is selected in the confirmation message, registration processing is executed (step S3), and if the "No" button is selected, the flow ends.

[0114] Among these, the pre-registration processing (step S1) and the registration processing (step S3) are page-level actions, and the processing of displaying a confirmation message for selecting "Yes" or "No" (step S2) is a master page-level action.

[0115] Here, an "action" refers to something arranged for processing on a low-code basis, such as an action for displaying a message, an action for performing processing, etc. A "master page action" refers to an action arranged on a page that groups functions common to the screen. By inheritance, the cost associated with settings on the inherited page can be reduced. Since changes cannot be made on the inherited page, processing related to the actions arranged on the master page is unified.

[0116] A "page action" refers to an action arranged on a page (an inherited page such as a customer master maintenance page). When inheriting a master page, a placeholder action is arranged so that it can be implemented at the inheritance destination, and at the inheritance destination, an action for performing unique processing within the placeholder action is set. For example, in the case of the customer master maintenance example, the pre-registration process (step S1) and the registration process (step S3) are applicable.

[0117] FIG. 39 is a diagram showing an example of the display of a scenario creation screen when displaying candidates for the following operation content. In FIG. 39(A), in the scenario setting area of the scenario creation screen, "Registration button (modification)" is selected as the operation target, and "Click" is selected as the operation selection (the previous action). In this state, when the "Add operation button" is clicked, the logic flow information associated with the previous action is analyzed, and a recommended operation screen as shown in FIG. 39(B) that presents recommended operation content is displayed. In this example, as the recommended operation content, the operation "Click on the message box" of the basic page is proposed. When agreeing to this proposal and pressing the confirmation button, as shown in FIG. 39(C), it is set (reflected) in the selection of the operation target and the selection of the operation in the scenario setting area of the scenario creation screen.

[0118] Figs. 40A to 40C are diagrams showing an example of the definition management table 106a when the function of displaying candidates for the following operation contents is set. In this example, examples of the definition names "master page for master maintenance screen" and "trading partner master maintenance" are shown. In the logic flow information, information set for each logic flow (ID, name, and a group of flow elements connecting actions to each other, etc.) is set. The previous action ID is the ID of the action to be processed first, and the subsequent action ID is the ID of the action to be executed after the previous action is executed. The callback key is a key for determining the selection result when the user makes a selection to do something when an action is executed. In the action information, information set for each action (ID, name, action type, and each setting, etc.) is set.

[0119] Fig. 41 is a diagram showing an example of the analysis flow of the logic associated with the immediately preceding operation. In Fig. 41, the type of the immediately preceding operation is acquired (step S11). It is determined whether the acquired immediately preceding operation is a basic page (step S12). If the acquired immediately preceding operation is an operation on the basic page ( "Yes" in step S12), the identification ID of the set control is acquired (step S13). It is determined whether the acquired identification ID of the control exists in the definition management table 106a (step S14). If the acquired identification ID of the control exists in the definition management table 106a ( "Yes" in step S14), it is determined whether logic flow information is set (step S15).

[0120] If logic flow information is set ( "Yes" in step S15), it is determined whether there is a process that can be operated by RPA (step S16). The processes that can be operated by RPA are those for which actions such as a message display action, a screen startup action, and a screen transition action are set in the logic flow information of the definition management table 106a. If there is a process that can be operated by RPA ( "Yes" in step 16), the next operation is proposed (step S17).

[0121] On the other hand, when it is not an operation on the basic page (\"No\" in step S12), if the identification ID of the obtained control does not exist in the definition management table 106a (\"No\" in step S14), if the logic flow information is not set (\"No\" in step S15), and if there is no process that can be operated by RPA (\"No\" in step 16), the process ends (step S7).

[0122] With reference to the flows of FIG. 42, FIG. 43A, FIG. 43B, and the above FIG. 41, a specific processing image when the registration button is pressed will be described. In advance, a logic flow (logic flow 1 in FIG. 40) for performing a registration process is assigned to the registration button (S15 in FIG. 41). Since it is a common specification that a confirmation message appears after the registration button is clicked, a message display action is set in the definition management table 106a. As processes operated by RPA, there are clicks on \"Yes\" and \"No\" of the message. Therefore, the operation proposed as the next operation candidate is \"click on the message box\". Hereinafter, a specific processing image when the registration button is pressed will be described.

[0123] FIG. 42 is a diagram showing an example of a business partner master maintenance screen. FIGS. 43A and 43B are diagrams showing an example of the definition management table 106a. In the example of the definition management table 106a shown in FIGS. 43A and 43B, it includes a definition ID, a definition name, control information, action information, logic flow information, master page information (definition ID of the master page associated with the definition), and event assignment definition information.

[0124] The event assignment definition information is for associating control information with logic flow information, and includes a control ID, an event type, and a logic flow ID. In the example shown in the figure, the control ID is \"XXXM1...\", the event type is \"click\", and the logic flow ID is \"XXXX...\".

[0125] When the registration button is clicked on the customer master maintenance screen (see Fig. 42(A)), since the click operation is an operation on the basic page (steps S11 and S12 in Fig. 41), the control ID "XXXM1···" of the registration button on the master maintenance common master page is obtained, and the logic flow ID ("XXXX···") associated with the event assignment definition information is obtained for the control ID "XXXM1···". Using the logic flow ID ("XXXX···") as a key, the flow elements are obtained from the logic flow information (S13 - S15 in Fig. 41). When the obtained flow element is a process that can be operated by RPA, operation candidates are proposed (S16 and S17 in Fig. 41). The Id_action element 3 of the press-holder 1 action of flow element 1 is not a process operated by RPA, so it does not become an operation candidate. The Id_action element 2 of the message display action of flow element 2 is a message display action and is a process operated by RPA, so it is proposed as an operation candidate (see (B) and (C) in Fig. 42).

[0126] As described above, according to the present embodiment, a definition management table 106a in which a definition name is registered in association with control information including a control name and its type, a scenario creation screen is provided, and based on the definition management table, on the scenario creation screen, a list of definitions is displayed, a screen layout for the definition name selected by the scenario creator is displayed from the list, a list of controls operable in the screen layout is displayed, a selection candidate for an operation on the control selected by the scenario creator is displayed from the list of controls, and based on the selection of the operation by the scenario creator among the selection candidates for the operation, a test scenario including a definition name, a control, and its operation content is created and registered in the development application DB 106b. Therefore, an automatic operation means for automatically operating an application can efficiently create a test scenario for testing the application.

[0127] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] According to this embodiment, it is possible to contribute to improving business efficiency and promoting appropriate business judgment of the enterprise, and thus it is possible to contribute to Goals 8 and 9 of the SDGs.

[0128] In addition, according to this embodiment, it is possible to contribute to reducing waste loss and promoting paperless and digitization, and thus it is possible to contribute to Goals 12, 13 and 15 of the SDGs.

[0129] In addition, according to this embodiment, it is possible to contribute to strengthening control and governance, and thus it is possible to contribute to Goal 16 of the SDGs.

[0130] [5. Other Embodiments] In addition to the above-described embodiments, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0131] For example, among the processes described in the embodiment, all or part of the processes described as being automatically performed can be manually performed, or all or part of the processes described as being manually performed can be automatically performed by a known method.

[0132] In addition, regarding the test scenario creation support system 100, each component shown in the drawings is a functional concept, and it is not necessarily physically configured as shown in the drawings.

[0133]

[0134] ​For example, regarding the processing functions provided by the test scenario creation support system 100, particularly each processing function performed by the control unit, all or any part thereof may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing the information processing system to execute the processing described in the present embodiment, and is mechanically read by the test scenario creation support system 100 as needed. That is, a computer program for giving instructions to the CPU in cooperation with the OS to perform various processes is recorded in a storage unit such as a ROM or an HDD (Hard Disk Drive). This computer program is executed by being loaded into the RAM and constitutes the control unit in cooperation with the CPU.

[0135] Further, this computer program may be stored in an application program server connected to the test scenario creation support system 100 via an arbitrary network, and all or part of it can be downloaded as needed.

[0136] Also, a program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, this "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc.

[0137] Also, the "program" is a data processing method described in any language or description method, and is not limited to forms such as source code or binary code. Note that the "program" is not necessarily limited to being configured singly, and also includes those that are distributed as a plurality of modules or libraries, or those that achieve their functions in cooperation with other separate programs typified by an OS. Regarding the specific configuration, reading procedure, and installation procedure after reading for reading the recording medium in each system shown in the embodiment, well-known configurations and procedures can be used.

[0138] The various databases and the like stored in the storage unit are storage means such as a memory system such as a RAM or a ROM, a fixed disk system such as a hard disk, a flexible disk, and an optical disk, and store various programs, tables, databases, and web page files used for various processes and website provision.

[0139] Further, the test scenario creation support system 100 may be configured as an information processing system such as a known personal computer or workstation, or may be configured as the information processing system to which an arbitrary peripheral system is connected. Further, the test scenario creation support system 100 may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment in the system.

[0140] Furthermore, the specific forms of system distribution and integration are not limited to those shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various additions or according to the function load. That is, the above-described embodiments may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

Industrial Applicability

[0141] The present invention can be used in all industries and all fields.

Explanation of Signs

[0142] 100 Test scenario creation support system 102 Control unit 102a Automatic operation unit 102b Scenario creation unit 102c Application 104 Communication interface unit 106 Storage unit 106a Definition management table 106b Development application DB 108 Input / output interface unit 112 Input system 114 Output system 200 Server 300 Network

Claims

1. A test scenario creation support system that includes a control unit and supports the creation of test scenarios executed by an automatic operation means of an application, wherein the control unit is configured to be able to access a definition management table in which a definition name is associated and registered with control information including a control name and its type, provides a scenario creation screen, and based on the definition management table, the scenario creation screen displays a list of definitions, displays a screen layout for the definition name selected by the scenario creator from the list of the definitions, displays a list of controllable controls in the screen layout, displays selection candidates for operations for the control selected by the scenario creator from the list of the controls, and creates a test scenario including a definition name, a control, and its operation content based on the selection of the operation by the scenario creator in the selection candidates for the operations, and registers it in a database. A test scenario creation support system characterized by comprising scenario creation means.

2. The test scenario creation support system according to claim 1, wherein the list of the controls includes controls for a common operation target.

3. In addition to the definition name and the control information in the definition management table, logic flow information including an ID, a name, and a group of flow elements connecting actions for each logic flow, and action information including an ID, a name, an action type, and settings for each action are associated and registered, The scenario creation means presents candidates for the next operation from the operation selected immediately before based on the definition management table on the scenario creation screen. The test scenario creation support system according to claim 1.

4. The test scenario creation support system according to any one of claims 1 to 3, wherein the automatic operation means includes RPA.

5. The test scenario creation support system according to any one of claims 1 to 3, wherein the test scenario creation support system includes a low-code base or a no-code base.

6. The test scenario creation support system according to claim 1, wherein the application includes a business application.

7. A test scenario creation support method for assisting in the creation of a test scenario executed by an automatic operation means of an application, which is executed by an information processing system including a control unit, wherein the control unit is configured to be able to access a definition management table in which a definition name is associated with and registered with control information including a control name and its type, executed in the control unit, provides a scenario creation screen, and based on the definition management table, the scenario creation screen displays a list of definitions, displays a screen layout for the definition name selected by the scenario creator from the list of the list, displays a list of controls operable in the screen layout, displays selection candidates for operations for the control selected by the scenario creator from the list of the controls, and based on the selection of the operation by the scenario creator among the selection candidates for the operation, creates a test scenario including a definition name, a control, and its operation content, and registers it in a database. A test scenario creation support method characterized by including a scenario creation step.

8. A test scenario creation support program for assisting in the creation of a test scenario executed by an automatic operation means of an application, which is executed by an information processing system including a control unit, wherein the control unit is configured to be able to access a definition management table in which a definition name is associated with and registered with control information including a control name and its type, in the control unit, provides a scenario creation screen, and based on the definition management table, the scenario creation screen displays a list of definitions, displays a screen layout for the definition name selected by the scenario creator from the list of the list, displays a list of controls operable in the screen layout, displays selection candidates for operations for the control selected by the scenario creator from the list of the controls, and based on the selection of the operation by the scenario creator among the selection candidates for the operation, creates a test scenario including a definition name, a control, and its operation content, and registers it in a database. A test scenario creation support program for executing a scenario creation step.

Images