JP2006260390A - Test case generating program and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To automatically generate a test case and test data in relation to Web application. <P>SOLUTION: A computer functions as an object screen acquiring means for acquiring object screen for generating a test case from screen transition definition information, a column in screen acquiring means for acquiring a column for test from screen constituting information constituting an object screen, a column check information acquiring means for acquiring restrictions for the column for test from data definition information, and a test case data generating means for generating a test case and test data, by making the restrictions for the column for test match with a test case template, to generate the test case and the test data. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a program and a method capable of automatically generating a test case using various definition information necessary for a Web application.

  Prior art relating to automatic testing of software programs can be roughly classified into the following six areas. 1. 1. Automatic test item generation technology 2. Automatic test procedure generation technology 3. Automatic test data generation technology 4. Test script automatic generation technology Automatic test execution technology, 6. Automatic output of test results. And the above 4. There is a publicly known document related to the test script automatic generation technology (see, for example, Patent Document 1).

  In addition, the Web application is divided into three parts: Model (logic), View (presentation), and Controller (control), and each is created separately to clarify the function separation and ensure the independence of each function. Thus, the division of programming can be carried out efficiently. Also, by minimizing the dependency between components, it is possible to make it less susceptible to the effects of other parts being changed. This increases the reusability of the component. In addition, maintenance due to changes in other components can be minimized, and maintainability is improved.

  These MVC models are widely used for the purpose of improving development productivity of Web application construction, such as payment services on Web sites, integrated authentication, back-end connection, and session management.

Specifically, a part that describes business logic in Java (registered trademark) language, COBOL language or C language (Model), HTML (HyperText Markup Language) or JSP (Java (registered trademark) Server Pages) Web screen Divide it into a part that describes the configuration (View) and a part that describes the cooperative control of business processing and Web screen display by Servlet (Controller), and create each separately.
Japanese Patent Laid-Open No. 2002-14845

  However, in order to generate a test case related to a Web application using the conventional technology, definition information (screen transition arrangement information unnecessary in the process of developing an application) that is not general in the MVC model is used to generate a test case. It is necessary to create it separately.

  In addition, it is difficult to independently create “screen definition information” for creating test cases for screen configuration information described in HTML or the like for the following reasons.

  Reason 1: The expressive power of HTML is very high, and there are various creation tools. Therefore, the method of generating an HTML file from unique screen definition information is inefficient.

  Reason 2: The description content of the HTML file is often changed by the designer, and it is unrealistic for the designer to create unique screen definition information.

  Furthermore, it is difficult to narrow down test cases automatically, and there is a problem that the number of cases becomes very large.

  Therefore, the present invention provides a program capable of generating a test case using only screen transition definition information, data definition information, and screen configuration information described in HTML, JSP, etc., which are generally created in Web application development. It aims to provide a method.

  The first feature of the present invention is that the computer is used to generate the test case and test data, the target screen acquisition means for acquiring the target screen for test case generation from the screen transition definition information, and the screen configuration information constituting the target screen. In-screen column acquisition means for acquiring test target columns, column check information acquisition means for acquiring constraints on test target columns from data definition information, matching constraints on test target columns with test case templates, and test cases and test data It is intended to function as test case data generation means for generating.

  It is preferable that the screen transition definition information and the data definition information are described in XML (eXtensible Markup Language), and the screen configuration information is described only in HTML or a Java (registered trademark) code is embedded in the HTML description.

  According to the first feature of the present invention, a test case is obtained using only screen transition definition information, data definition information, and screen configuration information described in HTML, JSP, etc., which are generally created in Web application development. Can be generated.

  The screen configuration information is changed frequently. In addition, the screen configuration information is generally performed by a designer other than the person in charge of developing the entire Web application, but the designer generally creates definition information for generating test cases in addition to the screen configuration information. I am not good at doing it. Therefore, the effect of being able to automatically incorporate changes in the description content of the screen configuration information into the test case is significant.

  In addition, since test cases are generated based on executable design information, the number of cases can be reduced.

  The best mode for carrying out the present invention will be described below with reference to the drawings. The following description is merely an example, and the technical scope of the present invention is not limited to the following description.

  FIG. 1 shows a schematic configuration of a Web application server 20 in the first embodiment. As shown in FIG. 1, the server 20 receives a request from the Web browser of the client 10 and returns a response. Specifically, the server 20 receives the processing request from the controller, the screen transition definition XML file 21a, the data definition XML file 21b, the controller 22 that operates by reading these definition files, and returns predetermined data. (Registered trademark) BL (Java (registered trademark) application for building business logic) 23 and JSP 24 that receives a page display request from the controller and returns the page display to the client as a response are stored in a storage unit (not shown).

  FIG. 2 is a block diagram illustrating a configuration of the test case generation device according to the first embodiment. As shown in FIG. 2, the test case generation device 30 includes a central processing unit (CPU) 31, a main memory 32, an input device 33, a file device 34, and an output device 36, each of which is a bus. Data can be exchanged via 37.

  The central processing unit (CPU) 31 is a target screen acquisition means for acquiring a test case generation target screen from the screen transition definition information in order to generate a test case and test data, and a test target from the screen configuration information constituting the target screen. In-screen column acquisition means for acquiring columns, column check information acquisition means for acquiring constraints on test target columns from data definition information, matching test case templates with constraints on test target columns, and generating test cases and test data It functions as a test case data generation means.

  The main memory 32 is used as a work area for the test case generation program 40. The output device 36 includes a liquid crystal display, a CRT display, and the like. The contents of the generated test case are output to the output device 36.

  The input device 33 includes a keyboard, an FD drive, a network interface card, and the like. Various files are created or read using this input device.

  The file device 34 includes a hard disk drive. A screen transition definition XML file 21a, a data definition XML file 21b, a Java (registered trademark) BL source file 23, a JSP source file 24, and the like created or read using the input device 33 are stored in the file device 34a to generate a test case. It is assumed that the target screen acquisition module 42, the in-screen column acquisition module 43, the column check information acquisition module 44, the test case data generation module 45, the JSP information acquisition module 46, and the like constituting the program 40 are stored in the file device 34b.

  The target screen acquisition module 42 reads the screen transition definition XML file 21a and acquires a screen to be a test case generation target. The screen transition definition XML file 21a defines which Java (registered trademark) BL is executed when a certain action is requested on a certain page, and which page is transitioned according to the return value.

  The JSP source file 24 is parsed by a JSP parser. In the parsing method, the structure definition of the Java (registered trademark) language is roughly divided into, for example, three parts. The first part is the overall structure of the program, the file, and the program expressed by a declaration statement such as a function declaration or global variable declaration in the file. The second part is the basic structure of the program such as control statements, blocks or expressions. The third part is the basic elements of the program such as the names and types of variables and functions, constants, operators and their declarations.

  The parsing result is stored as an XML file in a JSP repository (not shown). Then, JSP information is acquired from the JSP repository via a low-level API, and the acquired JSP information is output to the in-screen column acquisition module 43.

  As a low-level API for JSP parsers and JSP repositories, Wapid developed by the Graduate School of Information Science at Nagoya University (Aso Lab) can be used.

  The in-screen column acquisition module 43 acquires a test case generation target column from the test case generation target screen.

  The column check information acquisition module 44 reads the data definition XML file 21b and acquires check information of the test case generation target column. The data definition XML file 21b defines a column ID, a column Japanese name corresponding to the column ID, data check information, and the like.

  The test case data generation module 45 matches the constraint on the test case generation target column with the test case template 25 to generate a test case and test data.

FIG. 3 is a flowchart illustrating the flow of the test case generation process in the first embodiment. As shown in FIG. 3, in step S11, the screen transition definition XML file 21a is read,
In step S12, a screen for test case generation is acquired,
In step S21, the JSP source file is read,
In step S22, the syntax of the JSP source file is analyzed,
In step S23, the JSP parsing result is registered in the JSP repository.
In step S41, a column for test case generation is acquired from the JSP repository,
In step S42, the data definition XML file 21b is read,
In step S43, column check information is acquired,
In step S44, the test case template is read,
In step S45, a test case and test data are generated.

  4 shows an example of a screen transition definition XML file, FIG. 5 shows an example of a JSP source file, FIG. 6 shows an example of a data definition XML file, FIG. 7 shows an example of a test case template, and FIGS. An example of each test case is shown. The embodiment will be described more specifically based on these specific files.

  As shown in FIG. 4, in the screen transition definition XML file 21a, as a transition destination, query.jsp is described in the ninth line, SysError.jsp in the 18th line, searchOk.jsp in the 29th line, and the like. .

  In step S11, the target screen acquisition module 42 extracts these query.jsp and the like as transition destinations.

  As shown in FIG. 5, “kaiin_no” is described in the 15th line, “kounyuu_bu” and the like in the 22nd line as columns into which data is input in the JSP source file 24.

  In step S41, the in-screen column acquisition module 43 extracts “kaiin_no” and the like as columns (data items) to be checked.

As shown in FIG. 6, the data definition XML file 21b describes restrictions on the columns. Specifically, the 3rd to 21st lines relate to the column whose ID is “kaiin_no”, of which the 6th line is of type String and the 9th line
<chkTyp> IS_NOT_NULL </ chkTyp>
Is a required data item (Null is not allowed), <chkTyp> IS_ALNUM </ chkTyp> on line 13
Means that all input data must be numeric values, lines 17-18
<chkTyp> IS_IN_MAX_SIZE </ chkTyp>
<opt> 8 </ opt>
Indicates that the input data is a maximum of 8 digits. Lines 22-35 relate to the column whose ID is “kounyuu_bi”, of which line 25 is type String, line 28 is a mandatory data item (Null is not allowed), line 32 Ocular
<chkTyp> IS_DATE </ chkTyp>
Indicates that the check type is a date type.

  In step S43, the column check information acquisition module 44 extracts constraints on each column such as the data type and the essential data item.

  As shown in FIG. 7, in the test case template 25, the check type of the column to be tested is described in the 5th to 8th lines, and the specification of the test case generation class is described in the 12th to 15th lines. As shown in the 32nd line of FIG. 6, the check type of the “kounyuu_bi” column is “IS_DATE”, and as shown in the 7th line of FIG. 7, the column whose check type is “IS_DATE” is shown in FIG. A test case is generated by the test case generation class shown in the 14th line. That is, in step S45, a test case and test data are generated by the test case generation class shown in the 14th line of FIG. 7 for the “kounyuu_bi” column.

  As shown in FIG. 8, the generated first test case is named the date normal system check as described in the third line, and the test target column as described in the tenth line. Is “kounyuu_bi” and the test data is “20040430” as described in the thirteenth line.

Also, as shown in FIG. 9, the generated second test case is named “Date Abnormality Check” as described in the third line, and the test as described in the ninth line. The target column is “kounyuu_bi”, the test data is “20040431” as described in the 12th line, and the test execution script is described as described in the 15th to 22nd lines.
P: \ home \ webapps \ shopping \ test \ script \ SHOPPING00003.rsp
Or
P: \ home \ webapps \ shopping \ test \ script \ SHOPPING00004.rsp
The screen image displaying the test result as described in the 28th to 29th lines is output as a bitmap file.

  As described above, according to the first embodiment, testing is performed using only screen transition definition information (XML), data definition information (XML), and screen configuration information (HTML, JSP) that are generally created in Web application development. Cases can be generated.

It is a figure which shows schematic structure of the Web application server 20 in Example 1. FIG. It is a block diagram which shows the structure of the test case production | generation apparatus in Example 1. FIG. 6 is a flowchart illustrating a flow of test case generation processing in the first embodiment. 6 is a diagram illustrating an example of a screen transition definition XML file according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a JSP source file according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a data definition XML file in Embodiment 1. FIG. 6 is a diagram illustrating an example of a test case template according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a first test case generated in the first embodiment. FIG. It is a figure which shows an example of the 2nd test case produced | generated in Example 1. FIG.

Explanation of symbols

21a ... Screen transition definition XML file, 21b ... Data definition XML file,
23 ... Java (registered trademark) BL source file, 24 ... JSP source file,
25 ... Test case template,
30 ... Test case generator 31 ... Central processing unit,
32 ... main memory, 33 ... input device,
34 ... File device, 36 ... Output device,
37 ... bus, 40 ... test case generation program,
42 ... Target screen acquisition module, 43 ... In-screen column acquisition module,
44 ... Column check information acquisition module,
45 ... Test case data generation module,
46 ... JSP information acquisition module

Claims (4)

A computer to generate test cases and test data,
Target screen acquisition means for acquiring the target screen for test case generation from the screen transition definition information,
In-screen column acquisition means for acquiring a test target column from the screen configuration information constituting the target screen,
Column check information acquisition means for acquiring constraints on the test target column from data definition information;
A test case generation program that functions as test case data generation means for generating a test case and test data by matching the constraint on the test target column with a test case template.   The test case generation program according to claim 1, wherein the screen transition definition information and the data definition information are XML files, and the screen configuration information is a JSP file or an HTML file. A computer for generating test cases and test data;
Procedure to obtain the test case generation target screen from the screen transition definition information,
A procedure for acquiring a test target column from the screen configuration information constituting the target screen;
A procedure for obtaining constraints on the test target column from the data definition information,
A test case generation method comprising: executing a procedure for generating a test case and test data by matching the constraint on the test target column with a test case template. The test case generation method according to claim 3, wherein the screen transition definition information and the data definition information are XML files, and the screen configuration information is a JSP file or an HTML file.

Images