JP2018045404A - Screen test support apparatus and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve work efficiency and convenience of screen test.SOLUTION: A screen test support apparatus 1 supports a test of a plurality of screens included in an application system 210. The screen test support apparatus 1 includes: a first processing unit 171 which extracts one or more data items of screens and display conditions thereof, on the basis of predetermined information on the data items displayed on screens; a second processing unit 172 which classifies the extracted data items by predetermined category; a third processing unit 173 which extracts a condition for displaying a predetermined screen corresponding to a predetermined category; a fourth processing unit 174 which extracts each of patterns when the condition includes the patterns; a fifth processing unit 176 which selects data to be set on the condition, for every multiple patterns, from among data stored in a database to be used by the application system.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a screen test support apparatus and method.

  For example, when developing a business system using BMPS (Business Process management System), it is necessary to check whether each screen operates according to the specification. Usually, a business system includes a large number of screens, and the screens are switched under various conditions. Therefore, it is difficult for a system developer to manually confirm screen operations.

  Therefore, it is conceivable to automatically execute a screen test. In Patent Document 1, a test case generation target screen is acquired from screen transition definition information, a test target column is acquired from screen configuration information constituting the target screen, a constraint on the test target column is acquired from data definition information, A technique for generating a test case and test data by matching a constraint on a test target column with a test case template is disclosed.

JP 2006-260390 A

  In Patent Document 1, the test target screen is acquired from the screen transition definition information. However, in general, the screen transition definition information does not describe information related to data (input values) input to the screen. For this reason, when the configuration of the next screen changes according to the input content on a certain screen, it is difficult to cope with the technique described in Patent Document 1. That is, the condition for transition from one screen to another screen is described in the screen transition definition information, but the configuration of the transition destination screen depends on the input content to the transition source screen. However, the screen transition definition information often does not clearly indicate what input value is set for the transition source screen and how the transition destination screen configuration changes. Therefore, the conventional technique described in Patent Document 1 has a problem that it is difficult to automatically execute a screen test, which takes time and effort of a developer.

  The present invention has been made in view of the above-described problems, and an object thereof is to provide a screen test support apparatus and method with improved usability. Another object of the present invention is to automatically perform a test by acquiring data to be set to reach conditions necessary for displaying a predetermined screen from a database used by a business system. It is to provide a good screen test support apparatus and method.

  In order to solve the above problem, a screen test support device according to one aspect of the present invention is a screen test support device that supports testing of a plurality of screens included in a business system, and includes one or more screens displayed on each screen. A first processing unit that extracts each data item for each screen and its display condition based on predetermined information about the data item; a second processing unit that classifies each extracted data item by a predetermined category; A third processing unit that extracts a reaching condition for displaying a predetermined screen corresponding to the category of the first item, a fourth processing unit that extracts a plurality of patterns when there are a plurality of patterns in the reaching condition, and a reaching And a fifth processing unit that selects data to be set as conditions for each of a plurality of patterns from data stored in a database used by the business system.

  According to the present invention, even when there are a plurality of patterns in the arrival conditions for displaying a predetermined screen, data can be selected for each of the plurality of patterns from the database used by the business system, and the screen test is supported. be able to.

Explanatory drawing which shows the function structure of the screen unit test automatic execution assistance apparatus as a "screen test assistance apparatus". 1 is an overall view of an information processing system including a screen unit test automatic execution support device. The hardware block diagram of the screen unit test automatic execution support device. The hardware block diagram of a system development apparatus. The hardware block diagram of a disk array apparatus. Example of screen item definition. The schematic diagram of a screen transition. An example of a test case. Sample screen for testing. An example of reaching condition definition. Explanatory drawing which shows the dependence relationship between items. An example of condition input for each pattern. Database configuration example. The state that the data selected from the database is set as the condition input for each pattern is shown. A state in which a certain pattern is divided into sub-patterns and data is selected and set from the database for each sub-pattern is shown. The flowchart which shows a test case creation process. The flowchart which shows the detail of the step which selects the input value of a data item. The flowchart which shows a process when applicable data are not found. The flowchart which shows the process which performs a test case.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In this embodiment, as will be described later, automatic execution of a screen test is supported by the following procedure. That is, this apparatus creates a test case considering only display conditions. This device analyzes computer programs and screen transition definition information, and classifies each item by category. The category may be determined in advance in the screen item definition document.

  Next, this apparatus analyzes a computer program and screen transition definition information, and extracts display conditions (reach conditions for each item) for each category. When the arrival condition includes a condition that requires some input, the apparatus analyzes the dependency relationship such as “company name”, “affiliation department”, and “position” from the screen item definition document, and patterns it.

  And this apparatus analyzes the information stored in the database, and determines the input value of each item. For example, when the test target screen is a search screen, the apparatus selects an input value from which at least one search result appears from the database. If the corresponding input value (data) does not exist in the database, the apparatus outputs that fact as an error. The user of this apparatus that has received this error output can manually set an input value. The apparatus may automatically generate an input value instead of or together with the error output.

  Furthermore, the apparatus can select and execute a test case to check whether the screen operates correctly.

  A first embodiment will be described with reference to FIGS. FIG. 1 shows a functional configuration of a screen unit test automatic execution support apparatus 1. FIG. 2 shows the entire information processing system including the screen unit test automatic execution support device 1. Hereinafter, the screen unit test automatic execution support device 1 may be referred to as a screen test support device 1.

  The screen test support apparatus 1 implements predetermined functions 171 to 176 by executing the test execution support program 170. The predetermined functions are, for example, a test case generation unit 171, a category setting unit 172, a reaching condition extraction unit 173, a reaching condition definition pattern extraction unit 174, a test data setting unit 175, and a test case execution unit 176.

  The test case generation unit 171, which is an example of “first processing unit”, extracts data items and display conditions of each screen included in the business program 210 based on the screen item definition information 110, and generates a test case 130. It is a function to do. The screen item definition information 110 is an example of “predetermined information regarding one or more data items displayed on each screen”. By executing the business program 210, the “business system” is activated. Therefore, the business program 210 may be considered as an example of a “business system”.

  The category setting unit 172, which is an example of the “second processing unit”, is a function that classifies each extracted data item and its display condition according to a predetermined category. For example, the category setting unit 172 refers to the screen item definition information 110, the screen transition definition information 120, and the business program 210, and classifies data items that are components of the screen into a plurality of categories. A category is a display group that includes one or more data items. The category includes, for example, a “search condition” field for inputting search conditions, a “search result” field for displaying search results, and a “user registration field” for registering users.

  The arrival condition extraction unit 173, which is an example of the “third processing unit”, has a function of extracting an arrival condition that is a condition for displaying a predetermined screen corresponding to a category. The extracted arrival conditions are stored in the arrival condition definition information 140. The predetermined screen corresponding to the category may be displayed independently of other screens, or may be displayed simultaneously with the screens of other categories. Therefore, the predetermined screen corresponding to the category can also be called a predetermined screen area corresponding to the category. Examples of the reaching condition include a condition for displaying the search condition field, a condition for displaying the search result field, and a condition for displaying the user registration field. For example, the condition for reaching the search result column can include inputting the search result in the search condition column and operating the search start button to instruct a search.

  The arrival condition definition pattern extraction unit 174, which is an example of the “fourth processing unit”, has a function of extracting a plurality of patterns when there are a plurality of patterns in the arrival conditions. The arrival condition definition pattern extraction unit 174 extracts a plurality of patterns included in the arrival conditions based on the arrival condition definition information 140, the screen item definition information 110, and the dependency relationship information 150, for example.

  A case where there is a dependency relationship between a plurality of data items included in a certain category in the case of transition from a certain category to another category will be described. For example, if “corporation” is entered as the user type, “number of employees” is displayed, and if “individual” is entered as the user type, “employment” is displayed. Depending on the value set for the item, the display of the other data item and the settable value may change. In this case, there are two patterns of arrival conditions: “corporate” and “number of employees” and “individual” and “workplace”. Therefore, the reaching condition definition pattern extraction unit 174 extracts all the plurality of patterns included in the reaching condition.

  The test data setting unit 175, which is an example of the “fifth processing unit”, selects data for setting the reaching condition from the data group stored in the database 160 used by the business program 210, and selects a plurality of patterns. It is a function set for each. In other words, the test data setting unit 175 has the data (test data) to be set in the test case 130 for confirming whether the display operation of the screen is normally performed by the business program 210 having the test target screen. Select from the database 160 to be used.

  The test data setting unit 175 includes an alert output unit 1751 and a data generation unit 1752. The alert output unit 1751 is a function that outputs an alert to the user when there is no test data to be set in the reaching condition (test data to be set in the test case) in the database 160. Upon receiving the alert, the user can manually create test data and input it to the test data setting unit 175. The data generation unit 1752 is a function that automatically generates test data when the test data does not exist in the database 160.

  The test case execution unit 176, which is an example of the “sixth processing unit”, executes the arrival condition in which the test data is set by the test data setting unit 175, whereby the predetermined screen of the category corresponding to the arrival condition is displayed. This is a function to check whether it is displayed.

  The entire information processing system will be described with reference to FIG. The information processing system includes, for example, a screen unit test automatic execution support device 1 (screen test support device 1), a system development device 2, and disk array devices 3 (1) and 3 (2).

  The system development device 2 is a computer for the user U2 to develop the business program 210 (business system), and uses the disk array device 3 (2). The screen test support device 1 is a computer that supports a screen operation test included in the business program 210 developed by the system development device 2, and uses the disk array device 3 (1). The screen test support device 1 is operated by the user U1.

  In FIG. 2, the screen test support device 1 and the system development device 2 are connected by the communication network CN1, the screen test support device 1 and the disk array device 3 (1) are connected by the communication network CN2, and the system development device 2 An example in which the disk array device 3 (2) is connected by the communication network CN3 is shown. Instead of the configuration of FIG. 2, the communication networks CN1 to CN3 may be combined as one communication network, or the common disk array device 3 without dividing the disk array device 3 (1) and the disk array device 3 (2). It is good.

  The user U1 is a test administrator who performs a test for confirming the normal operation of the screen. User U2 is a system developer who develops a business system.

  FIG. 3 shows a hardware configuration of the screen test support apparatus 1. The screen test support apparatus 1 includes, for example, a microprocessor 11, a network interface 12, a disk interface 13, a user interface 14, and a memory 15. In the drawing, the microprocessor is abbreviated as CPU (Central Processing Unit), and the interface is abbreviated as IF (Interface).

  The microprocessor 11 implements the functions 171 to 176 described in FIG. 1 by executing the test execution support program 170 stored in the memory 15. The network interface 12 is a circuit for connecting and communicating with a communication network. The disk interface 13 is a circuit that inputs and outputs data by connecting to the disk array device 3 (1). The user interface 14 is a circuit that is connected to an input / output device (not shown) and exchanges information with the user U1 who is a test manager. Examples of the input / output device include a keyboard, a touch panel, a mouse, a voice input device, a display, a printer, and a voice synthesizer. The screen test support apparatus 1 may exchange information with the user U1 through an electronic message such as an e-mail.

  The memory 15 includes a storage medium such as a semiconductor memory, a flash memory device, and a hard disk. Although one memory is shown in the figure, the memory 15 may be composed of different types of storage media.

  The memory 15 stores, for example, screen item definition information 110, screen transition definition information 120, test cases 130, arrival condition definition information 140, dependency information 150 between data items, a database 160, and a test execution support program 170. Details of the stored contents 110 to 170 will be described later.

  FIG. 4 shows the hardware configuration of the system development apparatus 2. The system development device 2 includes, for example, a microprocessor 21, a network interface 22, a disk interface 23, a user interface 24, and a memory 25.

  Since the microprocessor 21 and the interfaces 22 to 24 are the same as those described with reference to FIG. 3, the description thereof is omitted here. The memory 25 stores a business program 210 for operating the business system.

  FIG. 5 shows a hardware configuration of the disk array device 3. The disk array device 3 includes, for example, a controller 31, a disk interface 32, and a disk drive 33.

  The controller 31 controls the overall operation of the disk array device 3. For example, the controller 31 groups one or more disk drives 33 to create a virtual storage device (logical volume) and manages the storage device. Further, the controller 31 reads / writes data from / to the disk drive 33 in accordance with the command received from the disk interface 32.

  For example, a file system 310 is stored in the disk drive 33. The file system 310 stores a database 160 and manages data input / output to / from the database 160.

  FIG. 6 shows an example of the screen item definition information 110. The screen item definition information 110 is information that defines data items displayed on the screen. The screen item definition information 110 includes, for example, a number 1100, a category 1101, a label name 1102, an input format 1103, a display condition 1104, and an activation condition 1105.

  A number 1100 is a number assigned to the data item. The category 1101 is information obtained by classifying data items by type. Although the case where the category 1101 is defined in advance in the screen item definition information 110 is shown here, the category 1101 does not need to be defined in the screen item definition information 110 in advance. When the category 1101 is not defined in advance in the screen item definition information 110, the screen test support apparatus 1 classifies each data item by category by analyzing the screen transition definition information 120 and the business program 210.

  The label name 1102 is the name of the data item. An input format 1103 indicates a method for inputting data items. Examples of the input method include a drop-down for selecting from values prepared in advance, and a text box for manually inputting letters or numbers.

  The display condition 1104 is a condition for displaying the data item on the screen. The data item is displayed on the screen when the display condition is satisfied. For example, a condition for displaying a data item named “Department” of “# 2” on the screen is when “Company A” or “Company B” is entered in the data item “Company name”. is there.

  The activation condition 1105 is a condition for controlling whether or not input to a data item is possible. If no activation condition is set for the data item, a value can be entered. If an activation condition is set for a data item, the value cannot be entered unless the activation condition is satisfied. For example, the data item “Name” of “# 5” can be input when “Member No.” is “1000” or more.

  FIG. 7 shows an overview of the screen transition definition information 120. The screen transition definition information 120 manages, for example, an action and a screen in association with each other. In the example of FIG. 7, when the “Next” button is operated while “Screen A” is displayed, the screen transitions to “Screen B”. If the “Done” button is operated while “Screen B” is displayed, the process ends. When the “Next” button is operated while “Screen B” is displayed, the screen transitions to “Screen C”. If the “Done” button is operated while “Screen C” is displayed, the process ends.

  FIG. 8 shows an example of the test case 130. The test case 130 is a case for confirming whether each screen included in the business program 210 operates normally. The test case 130 includes, for example, a number 1300, a test target category 1301, a test target label name 1302, a test case name 1303, an input 1304, a result 1305, and the like. The result 1305 records the test result.

  A number 1300 is a number assigned to each case. The test target category 1301 specifies a test target category. The test target label name 1302 specifies the label name (data item name) of the test target. An input 1304 indicates examination contents relating to input to the data item. For example, it is confirmed that “Age” of “# 1” is displayed when “Company A” is entered in “Company name”. It is confirmed that “Corporate Department” of “# 2” is not displayed when “Company C” is entered in “Company Name”.

  FIG. 9 shows an example of a screen to be tested. The test target screen G1 includes, for example, a search condition column GP11 that displays a search condition and a search result column GP12 that displays a search result.

  The search condition column GP11 includes, for example, data items for inputting search conditions such as “company name”, “affiliation department”, and “position”, and a search button GP13 for instructing start of search. The search result column GP12 includes, for example, data items for displaying search results such as “Member No.”, “Name”, “Gender”, “Age”, “Telephone”, “Country of Residence”, and a cancel button GP14 and an OK button GP15.

  FIG. 10 shows an example of the reaching condition definition information 140. In the upper part of FIG. 10, a “search condition” arrival condition management table 141 that stores conditions for reaching the category “search condition” is shown.

  In order to reach the category “search condition”, for example, as shown in the figure, a user ID and a password are input on a screen specified by a URL (Uniform Resource Locator), and a login button is pressed.

  The “search condition” arrival condition management table 141 includes, for example, a number 1410, a category 1411, a label name 1412, a property name 1412, an Xpath 1414, an input format 1415, and an input content 1416.

  The number 1410 is a reaching condition number. The category 1411 is information indicating the type of arrival condition. The property name 1413 is information for specifying setting information. Xpath 1414 is a description method for indicating a specific element in an XML (Extensible Markup Language) document. The input format 1415 indicates an input method to the data items constituting the reaching condition. The input content 1416 is content to be input to the data item.

  In the center of FIG. 10, a “search result” reaching condition table 142 that stores conditions for reaching the category “search result” is shown. Similar to the above-described table 141, this table 142 also includes a number 1420, a category 1421, a label name 1422, a property name 1423, an Xpath 1424, an input format 1425, and an input content 1426. Since the items 1420 to 1436 are the same as the items 1410 to 1416 described above, the description thereof is omitted.

  In order to reach the category “search result” from the category “search condition”, for example, as shown in the figure, a search condition is input on the screen of the category “search condition”, and a search button is further pressed.

  A condition input management table 143 for managing conditions to be input as search conditions is shown on the lower side of FIG. As a search condition, for example, as shown in the figure, some value is input to the data items of “company name”, “affiliation department”, and “position”. Since the items 1430 to 1436 of the table 143 are the same as the items 1410 to 1416 described above, description thereof is omitted.

  FIG. 11 is an explanatory diagram showing a dependency relationship between data items. There may be a dependency relationship between the data items displayed on the screen of a certain category, such that the other data item is displayed according to the input content to one data item.

  In the example of FIG. 11, a dependency relationship is set between the data item “company name” and the data items “affiliation department” and “position”. That is, when “Company A” is input to the data item “Company Name”, two data items “Department” and “Position” are displayed on the “Search Condition” screen. That is, when “Company name” is “Company A”, it is possible to search by specifying “Department” and “Position”.

  When “Company B” is input to the data item “Company Name”, only the data item “Department” is displayed on the screen of the category “Search Condition”. When “Company B” is entered in “Company name”, “Title” is not displayed.

  When “Company C” is input to the data item “Company Name”, only the data item “Position” is displayed on the screen of the category “Search Condition”. When “Company C” is entered in “Company name”, “Department” is not displayed.

  FIG. 12 shows tables 143A, 143B, and 143C for managing condition inputs generated based on the above-described data item can dependency.

  The table 143A shows a case where “Company A” is entered in “Company name”. In this case, data items for inputting “Department” and “Title” are displayed on the screen in a drop-down format. The table 143B shows a case where “Company B” is input to “Company name”. In this case, a data item for inputting “Department” is displayed on the screen in a drop-down format. The table 143C shows a case where “Company C” is input to “Company name”. In this case, a data item for inputting “title” is displayed in a drop-down format on the screen.

  The definition of the condition input shown in the tables 143A, 143B, and 143C indicates that there are a plurality of patterns for reaching the category “search result” from the category “search condition”. The “search result” screen can be reached through any of the patterns in the tables 143A to 143C.

  FIG. 13 shows an example of the database 160 used by the business system (business program 210). The database 160 includes, for example, a number 1600, a company name 1601, a belonging department 1602, a post 1603, a name 1604, an age 1605, a country of residence 1606, and a prefecture 1607.

  FIG. 14 shows a state in which data matching the pattern described in FIG. 12 is extracted from the database 160 and applied.

  The data specified by the number “# 1” in FIG. 13 is applied to the condition input 143A for the company name “A company”. Data specified by the number “# 3” in FIG. 13 is applied to the condition input 143B for the company name “B company”. The data specified by the number “# 5” in FIG. 13 is applied to the condition input 143C for the company name “C company”.

  FIG. 15 is a condition input management table 143A1, 143A2 showing a case where the pattern of the reaching condition has a plurality of sub-patterns.

  Here, in the screen example shown in FIG. 9, the data item “prefecture” is displayed only when “Japan” is input to the data item “resident country” included in the category “search result”. . The data item “resident country” is set to read only, and the contents cannot be rewritten. In this case, “Japan” is set for “Country of Residence” and “Prefecture” is displayed, and “State” is displayed because a country name other than “Japan” is set for “Country of Residence”. There will be sub-patterns that are not.

  Therefore, in FIG. 15, by applying the data specified by “# 1” in FIG. 13 to the condition input 143A shown in FIG. Generate. Similarly, the condition input 143A2 is generated by applying the data specified by “# 2” in FIG. 13 to the condition input 143A shown in FIG.

  FIG. 16 is a flowchart showing a process S100 for creating a test case for checking whether a screen included in the business program 210 operates normally.

  The screen test support apparatus 1 extracts the display condition 1104 for each data item from the screen item definition information 110 described with reference to FIG. 6, and creates a test case for each data item in consideration of only the display condition (S101). In step S101, a test case is generated based on only the display condition without considering the reaching condition.

  The screen test support apparatus 1 classifies each data item by category by analyzing the business program 210 and the screen transition definition information 120 (S102). In the screen item definition information 110, the category 1101 of each data item may be determined in advance.

  The screen test support apparatus 1 extracts the reaching condition for each category by analyzing the business program 210 and the screen transition definition information 120 (S103).

  The screen test support apparatus 1 determines whether there is unprocessed data input in the extracted arrival conditions (S104). Here, since the test case creation process S100 has just started, it is determined YES and the process proceeds to step S105. The screen test support device 1 selects an unprocessed data input existing in the reaching condition (S105), and extracts a dependency relationship between data items related to the reaching condition (S106).

  The screen test support apparatus 1 refers to the data stored in the database 160 and determines whether there is corresponding data to be input to each data item of the test case (S107). When the screen test support device 1 determines that there is data corresponding to the data item (S107: YES), the screen test support device 1 applies the corresponding data to the data item and selects an input value (S108). For example, as described with reference to FIGS. 12 to 14, the screen test support device 1 applies the data of the number “# 1” in the database 160 to each data item included in the arrival condition, thereby assigning the “company name”. Input value “Company A”, input value “General Affairs” to “Department”, and input value “Department Manager” to “Position” are selected and set as test cases.

  Note that a method for selecting an input value when there is a read-only data item in step S108 will be described later with reference to FIG.

  When the screen test support apparatus 1 cannot find data usable as test data in the database 160 (S107: NO), the screen test support apparatus 1 executes an abnormality process (S109). The abnormality process will be described later with reference to FIG.

  FIG. 17 shows an example of processing for determining an input value to a data item. FIG. 17 is an example of step S108 in FIG. As described above, the data item “prefecture” may be displayed only when “Japan” is set as the “resident country”. Furthermore, if the value of “Residential Country”, which is a precondition for displaying “Prefecture”, is set to read-only and cannot be changed, if “Residential Country” is “Japan”, “ It is necessary to create two test cases and check each screen display that “prefecture” is displayed and “prefecture” is not displayed when “country of residence” is a country name other than Japan. is there.

  Therefore, the screen test support apparatus 1 determines whether the read-only data item is a precondition for displaying another data item (S1081). When the read-only data item is a precondition (S1081: YES), the screen test support apparatus 1 refers to the database 160 and selects an input value that satisfies the precondition and an input value that does not satisfy the precondition (S1082). ). On the other hand, when the read-only data item is not a precondition (S1081: NO), the screen test support apparatus 1 refers to the database 160 and selects an input value corresponding to the arrival condition definition pattern ( S1083).

  FIG. 18 is a flowchart showing details of the abnormality process. FIG. 18 is an example of step S109 in FIG.

  If the test data for use in the test case is not found in the database 160, the screen test support apparatus 1 notifies the test administrator user U1 that there is no selectable data in the database 160 (S1091). ). For example, the screen test support apparatus 1 outputs a message notifying abnormality processing from a display or printer connected to the user interface 14, or transmits an email including the abnormality processing message to the mail address of the user U1.

  The screen test support apparatus 1 determines whether to automatically generate test data instead of data that does not exist in the database 160 (S1092). For example, the user U1 can set in the screen test support apparatus 1 whether or not test data can be automatically generated.

  When the screen test support apparatus 1 determines that data is automatically generated (S1092: YES), it automatically generates test data having a predetermined specification (S1093), and returns to the process of FIG. The test data having a required specification is, for example, data within a predetermined number of characters according to a predetermined character code.

  On the other hand, when the screen test support apparatus 1 determines not to automatically generate test data (S1092: NO), it determines whether test data is input from the user U1 via the user interface 14 (S1094). .

  The user U1 who has received the message in step S1091 can manually input test data using a keyboard, a touch panel, or the like. When the test data is input from the user interface 14, the screen test support apparatus 1 uses the data and returns to the process of FIG. 16 (S 1094: YES). The screen test support device 1 can stand by until data is input from the user U1 (S1094: NO).

  FIG. 19 is a flowchart illustrating a process for executing a test case. The screen test support apparatus 1 can automatically execute a test case automatically or partly manually generated by the processes of FIGS. The user U1 can appropriately set the instruction whether to automatically execute the test case and the timing for automatically executing the test case.

  The screen test support device 1 determines whether there is an unprocessed test case (S201), and if there is an unprocessed test case (S201: YES), selects the unprocessed test case (S202). Hereinafter, the selected unprocessed test case is referred to as a target test case.

  The screen test support device 1 checks whether or not a precondition exists when executing the target test case (S203). If the screen test support apparatus 1 determines that there is a precondition (S203: YES), the screen test support apparatus 1 selects a pattern of arrival condition definition that meets the precondition (S204). For example, as shown in FIG. 8, in the test case number “# 1”, it is confirmed that the data item “age” is displayed when “Company A” is input to the data item “company name”. In this case, the fact that the “company name” is “company A” is a precondition for displaying the data item “age”.

  On the other hand, when there is no precondition when executing the target test case (S203: NO), the screen test support apparatus 1 selects at least one pattern from the plurality of patterns of the arrival condition definition (S205). . All patterns may be selected.

  The screen test support device 1 executes the arrival condition definition selected in either step S204 or step S205 (S206), confirms whether or not the planned execution result has been obtained (S207), and returns to step S201.

  According to the present embodiment configured as described above, test cases can be automatically generated and executed even on screens having different arrival conditions for each category. Therefore, the work efficiency of the screen test and the usability of the user U1 are improved. Can be improved.

  In addition, this invention is not limited to the above-mentioned embodiment, Various modifications are included. The above embodiment has been described in detail for easy understanding of the present invention, and is not necessarily limited to the one having all the configurations described. A part of the configuration of one embodiment can be replaced with the configuration of another embodiment. The configuration of another embodiment can be added to the configuration of a certain embodiment. Further, with respect to a part of the configuration of each embodiment, another configuration can be added, deleted, or replaced.

  Each of the above-described configurations, functions, processing units, processing means, and the like may be realized in hardware by designing a part or all of them, for example, with an integrated circuit. Each of the above-described configurations, functions, and the like may be realized by software by interpreting and executing a program that realizes each function by the processor. Information such as programs, tables, and files for realizing each function can be stored in a recording device such as a memory, a hard disk, an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

  The technical features included in the above-described embodiments are not limited to the combinations specified in the claims, and can be combined as appropriate.

  1: Screen unit test automatic execution support device, 2: System development device, 3: Disk array device, 110: Screen item definition information, 120: Screen transition definition information, 130: Test case, 140: Arrival condition definition information, 150: Data Item can dependency information, 160: database, 170: test execution support program, 171: test case generation unit, 172: category setting unit, 173: arrival condition extraction unit, 174: arrival condition definition pattern extraction unit, 175: test Data setting unit, 176 test case execution unit, 1751: alert output unit, 1752: data generation unit

Claims (9)

A screen test support device that supports testing of a plurality of screens included in a business system,
A first processing unit for extracting each data item and its display condition for each screen based on predetermined information on one or more data items displayed on each screen;
A second processing unit for classifying the extracted data items into predetermined categories;
A third processing unit for extracting a reaching condition for displaying a predetermined screen corresponding to the predetermined category;
When there are a plurality of patterns in the reaching condition, a fourth processing unit for extracting each of the plurality of patterns;
A fifth processing unit that selects, for each of the plurality of patterns, data set in the arrival condition from data stored in a database used by the business system;
Screen test support device including In the fifth processing unit, for a pattern having a plurality of subpatterns among the plurality of patterns, data is selected from data stored in the database for each of the plurality of subpatterns.
The screen test support device according to claim 1. In the fifth processing unit, a warning is output when it is determined that the data set in the reaching condition does not exist in the database.
The screen test support device according to claim 1. The fifth processing unit receives an input of data set in the arrival condition after outputting the warning.
The screen test support device according to claim 3. In the fifth processing unit, when it is determined that the data to be set for the reaching condition does not exist in the database, data for setting the reaching condition is generated.
The screen test support device according to claim 1. Furthermore, it has a sixth processing unit for confirming whether or not the predetermined screen corresponding to the reaching condition is displayed by setting and executing data in the reaching condition.
The screen test support device according to any one of claims 1 to 5. The business system is a search-type business system that searches the database based on a search condition input from a user and outputs the search result.
The screen test support device according to claim 1. A screen test support method for supporting a plurality of screen tests included in a business system using a computer,
The calculator is
Based on predetermined information on one or more data items displayed on each screen, each data item for each screen and its display condition are extracted,
The extracted data items are classified into predetermined categories,
Extracting a reaching condition for displaying a predetermined screen corresponding to the predetermined category;
If there are a plurality of patterns in the reaching condition, each of the plurality of patterns is extracted,
Selecting the data to be set in the reaching condition for each of the plurality of patterns from the data stored in the database used by the business system;
Screen test support method. The computer outputs a warning when it is determined that the data set in the arrival condition does not exist in the database.
The screen test support method according to claim 8.

Images