JP2019525373A - How to generate test cases - Google Patents

Abstract

The present invention relates to a test case generation method relating to the technical field of software testing, in which a plurality of base test cases are set in advance, and a normal value in a normal value list or an error in an error value list for one base test case. Based on the value, each of the base test behaviors can be modified to form different derived test behaviors, respectively, and based on the different derived test behaviors, multiple different derivations associated with the base test case Form a test case. All base test cases and all derived test cases are used as test cases, and all base test operations and all derived test operations are used as test operations, and the system is automatically tested based on the test cases and test operations. The beneficial effects of the present invention are that test cases are automatically created, test time is shortened, test efficiency is improved, and labor costs are saved.

Description

  The present invention relates to the technical field of software testing, and more particularly to a test case generation method.

  In conventional software testing technology, there is a human intervention stage. A person manually sets a test case and various test actions included in the test case, and performs the test manually. The results must be compared to determine whether the test was successful based on the comparison results. In other words, there are an excessive number of human intervention procedures in conventional software testing techniques. This occupies a large amount of human resources, and software testing takes a long time, reducing test efficiency.

  Further, in the conventional software test technology, generally, unless a large number of test samples are generated using a large number of test cases, the function and stability of the system cannot be determined from the test results. However, in the prior art, it is usually required that a tester manually creates or sets each test case and each test operation for each test case. Therefore, it takes a great deal of time to create a test case, resulting in a significant increase in test time, resulting in a decrease in test efficiency. A lot of labor costs are also spent.

  Based on the above-mentioned problems existing in the prior art, a test method for generating test cases that reduces test time and improves test efficiency by realizing automatic test case creation and saves labor costs. provide.

  The above technical plan specifically includes the following.

  A test case automatic generation method, in which a plurality of base test cases are set in advance. Each base test case includes a plurality of base test operations, and each base test operation corresponds to a normal value list including 0 to multiple normal values and an error value list including 0 to multiple error values. doing.

  For one base test case, a plurality of different derived test operations are performed by changing the numerical value of each of the base test operations based on the normal value of the normal value list or the error value of the error value list. Respectively. A plurality of different derived test cases associated with the base test case are configured based on the plurality of different derived test operations.

  All the base test cases and all the derived test cases are used as test cases, and all the base test operations and all the derived test operations are used as test cases, and the system is based on the test cases and the test operations. Perform an automated test.

Preferably, in the test case automatic generation method, the following steps are executed for the base test case.
Step A1: One base test operation in the base test case is selected as an extended test operation.
Step A2: One normal value is selected from the normal value list associated with the extended test operation.
Step A3: It is determined whether or not the selected normal value is the same as the value of the extended test operation, and if it is the same, the process returns to Step A2.
Step A4: Assigning a value to the extended test operation based on the selected normal value to form the derived test operation.
Step A5: The derived test case is formed by combining the derived test operation and all the base test operations other than the extended test operation in the base test case.
Step A6: It is determined whether or not the unselected base test operation exists in the base test case. If it exists, the process returns to Step A1, and if not, exits.

Preferably, in the test case automatic generation method, the following steps are executed for the base test case.
Step B1: One base test operation in the base test case is selected as an extended test operation.
Step B2: One error value is selected from the error value list associated with the extended test operation.
Step B3: It is determined whether or not the selected error value is the same as the value of the extended test operation. If the error value is the same, the process returns to Step B2.
Step B4: Assigning a value to the extended test operation based on the selected error value to form the derived test operation.
Step B5: The derived test case is formed by combining the derived test operation and all the base test operations other than the extended test operation in the base test case.
Step B6: It is determined whether or not the unselected base test operation exists in the base test case, and if it exists, the process returns to Step B1, and if not, exits.

  Preferably, in the automatic test case generation method, for each base test operation in the base test case, a value is given to the base test operation using one error value in the corresponding error value list one by one. Thus, the corresponding derived test operations are generated one by one and all the derived test operations are combined to form the derived test case.

Preferably, in the test case automatic generation method, the following steps are executed for the base test case.
Step C1: One base test operation in the base test case is selected as an extended test operation.
Step C2: Forming the derived test operation by assigning an empty value to the extended test operation.
Step C3: The derived test case is formed by combining the derived test operation and all the base test operations other than the extended test operation in the base test case.
Step C4: It is determined whether or not the unselected base test operation exists in the base test case. If it exists, the process returns to Step C1, and if not, the process exits.

  Preferably, in the automatic generation method of the test case, for each base test operation in the base test case, the corresponding test operation is generated one by one by assigning an empty value to the base test operation. All of the derived test operations are combined to form the derived test case.

  Preferably, in the test case automatic generation method, a plurality of the test cases are arranged in order. Each of the test cases corresponds to a plurality of the test operations that are sequentially executed. In addition, one test control corresponds to each test operation, one operation method corresponds to each test operation, one test screen corresponds to each test control, A plurality of prediction results correspond to each test operation.

  A test operation list is formed by arranging all the test operations corresponding to all the test cases to be executed this time in the execution order of the test cases.

A method for performing an automatic test of a system based on the test case and the test operation specifically includes the following.
Step S1: One test operation is selected as the current operation from the operation list, and the test is performed using the test case corresponding to the current operation as the current case.
Step S2: The number of the display screen of the system browser in the test process is compared with the number of the test screen corresponding to the current operation to identify the display screen.
Step S3: Obtain the test control that matches the current operation as the current control from the identified display screen.
Step S4: After operating according to the operation method corresponding to the acquired current control based on the operation attribute of the current operation, an operation result corresponding to the current operation is output.
Step S5: The operation result is compared with the prediction result corresponding to the current operation to determine whether or not the current operation has been successfully executed, and the corresponding comparison result is used as the test result of the current operation. Save as.

  Preferably, in the automatic test case generation method, when the first test operation associated with the current case is executed in step S1, the first test control of the current case is performed. The test screen corresponding to is extracted as a start screen. The current case test is started by opening the start screen at an address associated with the start screen.

  Preferably, in the test case automatic generation method, before executing each test operation associated with the current case in step S1, the test operation is handled based on an operation attribute of the test operation. It is determined whether or not it is necessary to open the test screen of the test control, and an address associated with the test screen is extracted as necessary, and the test screen is opened.

  Preferably, in the test case automatic generation method, in step S1, initialization data of the current case is extracted after the test case is regarded as the current case, and the test of the current case is started. For this purpose, an initialization operation is performed on the data in the database associated with the current case.

  The address of the test screen corresponding to the first test control of the current case is extracted as the start address of the start screen, and the start parameter associated with the current case is used based on the start address Then, the start screen is opened and the test of the start screen is executed.

  Preferably, in the test case automatic generation method, the step S2 specifically acquires the number of the test screen corresponding to the test operation subsequent to the current operation, and monitors the number of the display screen. Then, if the number of the display screen matches the number of the test screen, it is considered that the display screen has been successfully switched, and the display screen is specified.

  Preferably, in the test case automatic generation method, the step S2 specifically acquires a number corresponding to the test screen subsequent to the current operation, and monitors the number of the display screen, If the number of the display screen matches the number of the test screen, it is considered that the display screen has been successfully switched, and the display screen is specified.

  Preferably, in the test case automatic generation method, in step S3, after acquiring one test control in the display screen, the control attribute of the test control and the test control corresponding to the current operation are acquired. A matching result is obtained by matching control attributes. If the matching result indicates successful matching, the acquired test control is specified as the current control.

Preferably, in the test case automatic generation method, in step S4, the operation attribute of the current operation is first determined before the operation of the control, and the operation for the current control is performed based on the operation attribute. To decide.
When the operation attribute of the current operation is a value setting, an operation performed on the current control is to give a value to the control.
When the operation attribute of the current operation is execution of an operation command, an operation performed on the current control is execution of the operation command for operating the control.
When the operation attribute of the current operation is transmission of a character string message, the current control is operated to transmit the corresponding character string message.
If the operation attribute of the current operation is a memory copy, the value of the current control is stored in system memory.
If the operation attribute of the current operation is a value assignment of the memory, the value of the current control is changed to a value stored in the system memory.
When the operation attribute of the current operation is a logical determination, a determination is made as to an expression for indicating a given value stored in the system memory, and a preset value associated with the current operation is determined based on the determination result Skip the subsequent test operation.
When the operation attribute of the current operation is execution of an operation using a function key combination, the current control is operated by transmitting a corresponding function key combination command to the input device of the system.

Preferably, in the test case automatic generation method, in step S5, the operation result and the prediction result are compared according to the type of the operation result.
When the operation result is a result of operating the control included in the display screen, the system reads information on the control corresponding to the display screen in the browser and compares the read information with the prediction result. .
When the operation result is a result corresponding to the in-column data of the browser, the system reads the corresponding in-column data in the browser and compares the read information with the prediction result.
When the operation result is data in the database of the system, the system reads the data in the database and compares the read information with the prediction result.

  Preferably, in the test case automatic generation method, in step S5, it is determined whether or not the current operation has been successfully executed. If the operation is successful, the operation result associated with the current operation is saved, and then the execution of step S5 is continued. On the other hand, if the test is not successful, the test for the current case is terminated, the process proceeds to the next test case, and the process returns to step S1.

  Preferably, in the test case automatic generation method, in step S5, the corresponding comparison result is stored as the test result of the current operation, and then proceeds to the next test operation. When the next test operation that has proceeded indicates an operation for the entire control, the process returns to step S4.

  The beneficial effects of the above technical scheme are as follows. That is, by providing a test case generation method capable of automatically creating a test case, the time required for testing is shortened, test efficiency is improved, and labor costs are saved.

FIG. 1 is a flowchart of a test case automatic generation method according to a preferred embodiment of the present invention. FIG. 2 is a flowchart of a test case automatic generation method according to a preferred embodiment of the present invention. FIG. 3 is a flowchart of a test case automatic generation method in a preferred embodiment of the present invention. FIG. 4 is an overall flow in the case where an automatic test is performed using a test case generated by the test case generation method and a test operation according to a preferred embodiment of the present invention. FIG. 5 is a diagram illustrating test case presetting in a preferred embodiment of the present invention. FIG. 6 is a diagram illustrating test case presetting in a preferred embodiment of the present invention. FIG. 7 is a diagram illustrating screen presetting in a preferred embodiment of the present invention. FIG. 8 is a diagram illustrating the presetting of the test operation in the preferred embodiment of the present invention. FIG. 9 is a diagram showing control presetting in a preferred embodiment of the present invention. FIG. 10 is a diagram showing a prediction result in a preferred embodiment of the present invention. FIG. 11 is a diagram showing a prediction result in a preferred embodiment of the present invention. FIG. 12 is a diagram showing a prediction result in a preferred embodiment of the present invention.

  Hereinafter, the technical solutions of the embodiments of the present invention will be described clearly and completely by combining the drawings according to the embodiments of the present invention. Needless to say, the embodiments described here are only a part of the embodiments of the present invention and are not all the embodiments. Any other embodiment obtained by a person skilled in the art based on the embodiment of the present invention without requiring creative labor falls within the scope of protection according to the present invention.

  In addition, you may combine on the assumption that the characteristic in the Example and Example of this invention does not contradict each other.

  Hereinafter, the present invention will be further described in combination with the drawings and specific examples, but this is not intended to limit the present invention.

  In a preferred embodiment of the present invention, a test case generation method is provided based on the above problems existing in the prior art. In the test case generation method, a plurality of base test cases are set in advance. Each base test case includes a plurality of base test operations. For each base test operation, a normal value list including 0 to multiple normal values and an error value list including 0 to multiple error values correspond to each other. Yes.

  For one base test case, a plurality of different derived test operations are formed by changing the numerical value of each base test operation based on the normal value of the normal value list or the error value of the error value list. In addition, a plurality of different derived test cases associated with the base test case are configured based on the plurality of different derived test operations.

  All base test cases and all derived test cases are used as test cases, and all base test operations and all derived test operations are used as test operations, and the system is automatically tested based on the test cases and test operations.

  Specifically, in the above embodiment, first, one base test case and a plurality of base test operations included in the base test case are set. That is, by setting corresponding parameters and other initialization data for the base test case and a plurality of corresponding base test operations, a complete executable base test case and base test operation are formed.

  Subsequently, in the above embodiment, one normal value list and one error value list are preset for each base test operation in the base test case. All the numerical values included in the normal value list are normal values, that is, values that enable the base test operation. The numerical values included in the error value list are all error values, that is, values that invalidate the base test operation.

  Therefore, in the above embodiment, finally, based on the normal value list and the error value list corresponding to each base test operation, a plurality of different derived test operations are randomly generated (for example, normal value list / error value list). Any normal value / error value is applied to the base test operation to form a derived test operation), and a plurality of different derived test operations are combined to form a plurality of different derived test cases. Both the base test case and the derived test case are regarded as test cases, and accordingly, both the base test operation and the derived test operation are regarded as test operations. Finally, it is possible to test the stability of the system function and the system operation by performing an automatic test of the entire system by the test case and the test operation.

  In the above embodiment, “0 to multiple normal values” and “0 to multiple error values” may be that the normal value list / error value list may be empty, or a plurality of normal values / error values. It may be included. If the normal value list is empty, it is not necessary to extend the normal value of the corresponding base test operation. Similarly, when the error value list is empty, it is not necessary to execute the expansion of the corresponding error value of the base test operation. In the following, this point will not be described in further detail.

In the preferred embodiment of the present invention, as shown in FIG. 1, a derivative test case including a derivative test operation, all of which are normal values, can be generated by executing the following steps on the base test case.
Step A1: One base test operation in the base test case is selected as an extended test operation.
Step A2: One normal value is selected from the normal value list associated with the extended test operation.
Step A3: It is determined whether or not the selected normal value is the same as the value of the extended test operation. If it is the same, the process returns to Step A2.
Step A4: Assign a value to the extended test operation based on the selected normal value to form a derived test operation.
Step A5: A derived test case is formed by combining the derived test operation and all base test operations other than the extended test operation in the base test case.
Step A6: It is determined whether or not an unselected base test operation exists in the base test case. If it exists, the process returns to Step A1, and if not, exits.

Specifically, in a preferred embodiment of the present invention, the base test case may be a test case for airline ticket purchase. In this case, the following may be considered as the base test operation included in the test case.
A. Enter departure date: 20140412 Return date: Enter 20160418 C.I. From: Enter Beijing. Destination: Enter Shanghai and E. Number of departures: Enter 2 Search

The normal value list and error value list corresponding to each base test operation can be set as follows.
A. Departure date: Normal value list (20160412, 20160228, 201660229, 201660418), Error value list (00, 11000203, 20160230, 21061255, 2016/16/10)
B. Return date: normal value list (20160412, 20160228, 201660229, 201660418), error value list (00, 11000203, 20160230, 21061255, 2016/16/01)
C. Origin: Normal value list (Beijing, Tianjin, Shijiazhuang), Error value list (00, AA, Tohoku, Beijing 11, 22 Beijing, Asia, Hokkaido)
D. Destination: Normal value list (Beijing, Tianjin, Shijiazhuang), Error value list (00, AA, Tohoku, Beijing 11, 22 Beijing, Asia, Hokkaido)
E. Number of departures: normal value list (1, 2, 9, 99), error value list (0, A, -1, 100, 101).

  The first operation in the base test operation is selected as an extended test operation (ie, test operation A), and one normal value in the corresponding normal value list is selected, and the normal value is the initial value of the base test operation. What is necessary is just to judge whether it is the same as a value (for example, 20140412 in the said normal value list is the same as the initial value of a base test operation). In the same case, one normal value is acquired from the normal value list again.

  In the above embodiment, after obtaining a normal value different from the initial value, a value is given to the extended test operation using the normal value, thereby forming a derived test operation different from the extended test operation.

  Finally, in this embodiment, the derived test operation is combined with other base test operations other than the extended test operation in the original base test case to obtain a derived test case different from the base test case. For example, A ′ (derived test operation acquired by filling the base test operation A with a normal value), B, C, D, E, and F are combined to form a derived test case.

  In the above embodiment, by assigning each normal value in the normal value list once for each base test operation, it is possible to finally form a plurality of different derived test cases. For example, in the above embodiment, 14 derived test cases, all of which are normal values, can be formed.

In the preferred embodiment of the present invention, as shown in FIG. 2, a derived test case including an error value derivation test operation can be generated by executing the following steps on the base test case.
Step B1: One base test operation in the base test case is selected as an extended test operation.
Step B2: One error value is selected from the error value list associated with the extended test operation.
Step B3: It is determined whether or not the selected error value is the same as the value of the extended test operation, and if it is the same, the process returns to Step B2.
Step B4: Assign a value to the extended test operation based on the selected error value to form a derived test operation.
Step B5: A derived test case is formed by combining the derived test operation and all base test operations other than the extended test operation in the base test case.
Step B6: It is determined whether or not an unselected base test operation exists in the base test case. If it exists, the process returns to Step B1, and if not, exits.

  Specifically, in the preferred embodiment of the present invention, similarly to steps A1 to A6 described above, in steps B1 to B6, first, an extended test operation is determined, and an error is listed from the error value list associated with the extended test operation. While selecting one value, it is determined whether or not the error value is the same as the initial value of the extended test operation (if it is the same, it is selected again). Subsequently, a value is assigned to the extended test operation based on the selected error value to form a completely new derived test operation. The derived test operation is an error test operation.

  Finally, in the above embodiment, the newly generated derived test operation is combined with the remaining base test operation excluding the extended test operation in the base test case to form a new derived test case.

  Finally, for example, in the case of the above-described base test case, 31 different derived test cases can be acquired by sequentially assigning values based on each error value list for each base test operation. Each of these derived test cases includes a derived test operation to which an error value is assigned.

  In a preferred embodiment of the present invention, for each base test operation in the base test case, a value is assigned to the base test operation using one error value in the corresponding error value list, so that the corresponding derived test operation is 1 Each is generated one by one and all derived test operations are combined to form a derived test case. That is, in the above embodiment, by selecting one error value for each base test operation, a derived test operation with different error values is formed, and a derived test including only an error derived test operation. Form a case.

  In other words, in the case of the above-described base test case, there is only one derived test case including only a derived error derived test operation.

In the preferred embodiment of the present invention, as shown in FIG. 3, an empty derived test case can be generated by performing the following steps on the base test case.
Step C1: One base test operation in the base test case is selected as an extended test operation.
Step C2: A derived test operation is formed by assigning an empty value to the extended test operation.
Step C3: A derived test case is formed by combining the derived test operation and all base test operations other than the extended test operation in the base test case.
Step C4: It is determined whether or not an unselected base test operation exists in the base test case. If it exists, the process returns to Step C1, and if not, the process exits.

  Specifically, in a preferred embodiment of the present invention, it is possible to form a derived test case including a derived test operation with an empty value by assigning an empty value to each base test operation in the base test case. In the case of the above-described base test case, finally, five derived test cases including a derived test operation with an empty value can be formed.

  In a preferred embodiment of the present invention, it is possible to form a derived test case including only a derived test operation having an empty value by assigning an empty value to each base test operation in the base test case. In the case of the above-described base test case, finally, one derived test case including only a derived test operation whose value is empty can be formed.

  Therefore, as described above, it is possible to finally generate up to 51 derived test cases using one base test case. Further, if the number of values included in the normal value list / error value list is corrected before the generation of the derived test cases, more derived test cases can be generated to meet different automatic test needs.

  In the preferred embodiment of the present invention, in the case of the normal value list including 0 normal values, the step corresponding to the generation of the derived test case (that is, generation of the derived test case including the normal value) can be skipped. However, steps C1 to C4 may be executed in order to generate a derived test case that is all empty. Similarly, in the case of an error value list including zero error values, the step of generating a derived test case including an error value can be skipped, but in order to generate an all derived test case, step C1 Steps C4 to C4 may be executed.

  As described above, in the technical solution of the present invention, a normal value list and an error value list are provided for each base test operation, and a value is assigned to each base test operation based on the values of the normal value list and the error value list and empty values. A plurality of different derivation test cases are formed by combining the different derivation test operations formed by giving values and adding values. Thus, one base test case is extended to a plurality of different derived test cases, and the test case automatic extension operation is completed.

In a preferred embodiment of the present invention, after completing the test case automatic extension, a plurality of test cases are arranged in order. Each test case corresponds to a plurality of test operations executed in sequence. Moreover, one test control corresponds to each test operation, one operation method corresponds to each test operation, one test screen corresponds to each test control, and each test operation corresponds to each test operation. A plurality of prediction results correspond to.

  The test operation list is formed by arranging all the test operations corresponding to all the test cases to be executed this time in the execution order of the test cases.

As shown in FIG. 4, a method for executing an automatic test of a system based on a test case and a test operation specifically includes the following.
Step S1: One test operation is selected as the current operation from the operation list, and the test is performed using the test case corresponding to the current operation as the current case.
Step S2: The display screen is identified by comparing the number of the display screen of the system browser in the test process with the number of the test screen corresponding to the current operation.
Step S3: A test control that matches the current operation is acquired as the current control from the identified display screen.
Step S4: After operating according to the operation method corresponding to the acquired current control based on the operation attribute of the current operation, an operation result corresponding to the current operation is output.
Step S5: The operation result is compared with the prediction result corresponding to the current action to determine whether or not the execution of the current action is successful, and the corresponding comparison result is stored as the test result of the current action.

  In a specific embodiment, first, a plurality of test cases are preset. Each test case includes a plurality of test operations, and one test control corresponds to each test operation. In addition, since one test screen corresponds to each test control, a plurality of test screens are associated with each test case.

  Specifically, the test cases are preset in order. That is, a plurality of test cases are set in advance according to a certain execution order, and when execution of one test case is completed, the process proceeds to execution of the next test case. Similarly, different test operations are arranged in order in the same test case. One test control corresponds to each test operation, and one test screen corresponds to each test control. The test screen is divided into a start screen and a subsequent screen. Although there is only one start screen for one test case, a plurality of subsequent screens may exist. The start screen may be a first screen for executing a test case, and the subsequent screen may be a display screen arranged in order after the start screen. Each test screen (including a start screen and a subsequent screen) is a screen corresponding to one test control operation. For example, when a user logs in to the test case, a test operation for inputting a user name and a password and a test operation for clicking a login control can be included. The test screen corresponding to the login control may be a login screen provided so that the user can input a user name and a password, and the screen may be a test case start screen. The plurality of subsequent screens in the test case may be other screens of the system browser displayed after successful login, or may be screens displaying login failure. The screens are arranged according to test logic.

  In the above embodiment, the test case setting interface is as shown in FIGS. The name of the start screen of the test case is “account information”, the name of the test case is “transfer to the account / password correction interface”, and the related test case of the previous test case is “transfer to the account information interface”. Correspondingly, related test cases in the first half of the test case further include “login”, “shift to system management”, and “transfer to account information interface”. The related test cases in the previous period are arranged in order. Since the test case setting interface shown in FIG. 2 is a visualization interface and not a code level setting interface in the prior art, the test case setting process can be simplified. FIG. 3 shows a list of the test cases set in advance.

  In the above embodiment, the setting interface of the test screen (including the start screen and the subsequent screen) associated with the test case is as shown in FIG. The screen information in FIG. 7 includes a screen number (ID), a screen name, and a screen access address. The access address is a URL (Uniform Resource Locator) address. The screen setting interface is also a visualized interface.

  In the above embodiment, the test operation setting interface is as shown in FIG. In FIG. 8, the test operation can be set as “search condition input”, and a plurality of display screen names, a plurality of control names, a plurality of operation attributes (methods), values given to the plurality of test operations, and the like are associated with each other. ing. Since the setting interface for the test operation is also visualized, the operation is easy.

  In the above embodiment, the operation method corresponding to each test operation can be acquired from the operation attribute through a series of operations. The operation attribute can be expressed by a corresponding expression.

  In the above embodiment, an operation list is formed from test operations associated with different test cases for which setting has been completed. Specifically, for example, it is assumed that the test cases A, B, and C are set so as to be arranged in order. The test case A is set so that the test operations A1, A2, and A3 are sequentially arranged, and the test case B is set so that the test operations B1 and B2 are sequentially arranged. C is set such that test operations C1, C2, C3, and C4 are sequentially arranged. In this case, the operation list may be arranged in the order of A1, A2, A3, B1, B2, C1, C2, C3, and C4.

  In the above embodiment, the control setting interface associated with each test operation is as shown in FIG. In FIG. 6, the control information of each control includes a control number (ID), a control title, a control type, a control front-end technology, an attribute name for specifying the control, an attribute value for specifying the control, and a maximum / minimum value of the control. Value / maximum length / minimum length, control default value, control normal value list / error value list, etc. are included. The control setting screen is also a visualization screen.

  In the above embodiment, the test case, test operation, screen, control and the like are set by 1) the system in advance, or 2) the test elements are set in the system in advance, and the visualization interface corresponding to the user It is possible to use two types of methods in which different test elements are selected and combined to form setting information such as test cases, test operations, screens and controls.

  The prediction result setting interface described in the above embodiment will be described in detail later.

  In the above embodiment, for all test cases to be executed this time, all the test operations included in the test cases are arranged in one operation list according to the arrangement order of the test cases.

  In step S1, first, one test operation is selected and execution of the test is started. Specifically, a test case corresponding to the test operation may be determined, and the test may be started with the determined test case as the current case.

  In the above embodiment, after identifying the current operation and the current case, the browser display screen switching status is monitored to find the screen number of the display screen loaded in the browser at the current time, and the test in the current operation The screen number is compared with the display screen number. That is, based on the screen number on the current display screen, matching with the test screen corresponding to the current operation is performed, and the current browser display screen is specified as the test screen corresponding to the current operation in the current case.

  In the above embodiment, after specifying the display screen, the display content of the display screen is analyzed, and real-time information of all controls on the display screen is acquired. Based on the control related information acquired from the display screen, matching with control information corresponding to the test operation (for example, an attribute for identification) identifies the exact control, and the position of the identified control Information can be recorded. Specifically, after obtaining one control on the display screen, the control result of the control and the control attribute of the test control corresponding to the current operation are matched to obtain a matching result. When the matching result indicates that the matching is successful, the acquired control is specified as the current control. For example, after acquiring one control, the control is compared with the test control corresponding to the test operation, and if it is different, it means that it is not the control of the current operation. Means control. The control that succeeds in matching is regarded as the current control. Accordingly, as a method for specifying the control, first, a test screen corresponding to a test operation is used to specify a test screen which is a currently displayed display screen. The number of controls included in the display screen is not necessarily one. Therefore, the control attribute corresponding to the test operation is specified by further comparing the control attributes on the display screen, and the test control specification is completed.

  In the above embodiment, after the test control is specified, a corresponding operation can be executed on the test control based on the operation attribute of the current operation. When the execution of the current operation is completed, the operation result corresponding to the current operation is recorded.

  In the above-described embodiment, after the operation result is acquired, the operation result is compared with a prediction result corresponding to the current action, thereby determining whether or not the operation of the current action is successful and recording the comparison result.

  When it is determined that the current operation has been completed after the completion of the execution of the process, the process proceeds to the next test operation and returns to step S1.

  As described above, the technical solution of the present invention makes the process of setting test parameters such as test cases, test operations, test controls, test screens, and prediction results in advance simple and clear by using a visualized operation method. In addition, since the visualized software test can be executed speedily and automatically based on the set test parameters, it is possible to meet the needs of the software test and improve the efficiency of the software test.

  In the preferred embodiment of the present invention, before executing each test operation associated with the current case in step S1, the test screen of the test control corresponding to the test operation is opened based on the operation attribute of the test operation. It is determined whether or not it is necessary, and an address associated with the test screen is extracted as necessary, and the test screen is opened. Specifically, in the above embodiment, before executing each test operation, it is determined whether or not it is necessary to load a test control test screen corresponding to the test operation. If you don't need it, don't change the screen at all. In the above embodiment, the test screen is extracted and loaded by extracting the URL address of the corresponding screen of the corresponding control. Specifically, the URL address associated with the corresponding screen of the corresponding control is extracted, the activation parameter specified by the current case is used, and the corresponding URL address is opened in the browser to test the current case. To do. If the browser specified at that time is already open, it is only necessary to extract the URL address associated with the screen and update the browser display screen. In addition, the operation attribute of the test operation referred to in the above embodiment includes the relationship between the test operation and the operation before and after the test operation. After determining the relevance between the test operation and the operation before and after that, the system determines whether it is necessary to extract the corresponding URL address and open the corresponding test screen.

  In another preferred embodiment of the present invention, when the first test operation associated with the current case is executed in step S1, the test screen of the first test control corresponding to the current case is displayed. Extract as start screen. The current case test is then started by opening the start screen at the address associated with the start screen. Specifically, in the above embodiment, only when the first test operation in the test case is executed, the test screen of the test control corresponding to the test operation is loaded as the start screen. Specifically, when the test is started for the first time, the test may be started by selecting the first test operation in the operation list. After selecting the test operation, the test operation is set as the current operation, a corresponding test case is specified based on the current operation, and the test case is set as the current case. Subsequently, the test screen corresponding to the test operation corresponding to the current operation is extracted, and the test is started. In the above embodiment, since the first test operation is the test operation at the start of the test, the screen extracted above should be the start screen of the corresponding current case. The method for loading and extracting the start screen is the same as in the above embodiment. That is, it is realized by extracting the URL address of the start screen and opening it with a predetermined system browser using the start parameters specified by the current case.

  In a preferred embodiment of the present invention, before starting execution of each test case, first, initialization data of the test case is set. That is, the initialization operation is performed on the test case data. For the data initialization operation, by performing initialization processing for the corresponding data in the database, it is possible to avoid the effect on the current test due to the remaining test data remaining in the database, and to support in the database This includes adding initialization data to form an initialization test environment for the test, ensuring uniformity of the test start environment, and the like.

  Therefore, in the preferred embodiment of the present invention, when executing a new test operation, it is necessary to first determine whether the test operation is the first test operation in any test case. In the first case, the test operation is executed after performing the data initialization operation for the test case, while in the other case, the test operation is executed as it is.

  Alternatively, in another preferred embodiment of the present invention, the start screen of each test case is labeled. When the process proceeds to the start screen during the test process, the data initialization operation is performed for the corresponding test case, and then the test operation corresponding to the start screen is executed.

  In the preferred embodiment of the present invention, after the test case is regarded as the current case in step S1, initialization data of the current case is extracted in order to start the test of the current case.

  After extracting the address of the test screen corresponding to the first test control of the current case as the start screen, the start screen is opened using the start parameters specified by the current case, and the test is executed.

  The startup parameters referred to in the above embodiments are reference network parameters when the test screen as the start screen is opened.

  In the preferred embodiment of the present invention, the above step S2 specifically obtains the number of the test screen corresponding to the test operation subsequent to the current operation, monitors the number of the display screen, and determines the number of the display screen. If it matches the test screen number, it is considered that the display screen has been successfully switched, and the display screen is specified. Specifically, in step S2, if the number of the current display screen matches the number of the test screen corresponding to the subsequent operation of the current operation, the current display screen is considered to have been successfully switched. Thus, the display screen is specified as a test screen in the subsequent operation of the current operation.

  In another preferred embodiment of the present invention, the step S2 specifically obtains a number corresponding to a subsequent test screen of the current operation and monitors the number of the display screen so that the number of the display screen is tested. If it matches the screen number, it is considered that the display screen has been successfully switched, and the display screen is specified. Specifically, in step S2, if the number of the current display screen matches the number of the subsequent screen of the current operation, it is assumed that the current display screen has been successfully switched, and the display screen Is identified as the subsequent screen of the current action.

  In the preferred embodiment of the present invention, in step S4, the operation attribute of the current operation is first determined before operating the control, and the operation for the current control is determined based on the operation attribute.

  When the operation attribute of the current operation is a value setting, an operation performed on the current control is to assign a value to the control. For example, a preset numerical value is given to the control.

  When the operation attribute of the current operation is execution of an operation command, the operation performed on the current control is execution of the operation command for operating the control. For example, when the operation command is “click”, a control click operation may be executed on the current control.

  When the operation attribute of the current operation is execution of an operation using a function key combination, the current control is operated by transmitting a corresponding function key combination command to the input device of the system. For example, if the combination of function keys is a combination of “Shift” key, “Alt” key, and “Enter” key on the input keyboard, the system notifies the keyboard to output the combination command of the three keys. Therefore, a corresponding function key combination command may be transmitted to the keyboard.

  When the operation attribute of the current operation is transmission of a character string message, the corresponding character string message is transmitted by operating the current control. Specifically, a corresponding character string message may be transmitted through a browser.

  If the operation attribute of the current operation is memory copy, the value assigned to the current control is stored in the system memory. Specifically, a value assigned to the current control or other specific value is stored in the system memory, that is, the “clipboard” function of the system memory is realized.

  When the operation attribute of the current operation is value addition from the memory, a value stored in the system memory is assigned to the current control based on the operation attribute of the current operation.

  When the operation attribute of the current operation is logic determination, the value stored in the memory is determined, and the subsequent test operation set in advance based on the determination result is skipped. Specifically, logical judgment means judgment on an expression indicating a given value in the system memory. For example, it is determined whether or not the expression is larger / smaller than some preset value, or whether or not the value stored in the system memory is true / false. The skip plan indicating the above skip operation may be set in advance in the test attribute of each test operation. As a specific determination process, an expression indicating a numerical value stored in the system memory is determined. Then, based on the determination result, it is determined whether or not to execute the preset skip plan, and one or a plurality of subsequent test operations are skipped. In the above embodiment, the skip plan may not include any subsequent operation. That is, regardless of the determination result, it is not necessary to skip any subsequent operation.

  In the preferred embodiment of the present invention, as described above, when the current screen progresses, the display content of the browser is monitored to identify a new screen number and to identify a new test control.

  In a preferred embodiment of the present invention, in step S5, the operation result is compared with the prediction result according to the type of operation result.

  When the operation result is a result of operating the control on the display screen, the system reads information on the corresponding control included in the display screen in the browser and compares the read information with the prediction result. Specifically, when comparing the control information and the prediction result, the grouped controls are compared together. For example, information corresponding to all controls on the current display screen is acquired and compared with prediction results.

  When the operation result is a result corresponding to the in-column data of the browser, the system reads the corresponding in-column data in the browser and compares the read information with the prediction result.

  If the operation result is data in the database of the system, the system reads the data in the database and compares the read information with the predicted result.

Specifically, in a preferred embodiment of the present invention, an interface in which the prediction result is preset is as shown in FIGS.
FIG. 10 shows the prediction result of the control in the screen. The prediction result may include a control ID, a control title, a prediction result type, and a prediction result value.
FIG. 11 shows the prediction results of the tables. The prediction result may include attributes such as control ID, control title, number of predictions, number of comparisons, and table data.
FIG. 12 shows the prediction results of the databases. The prediction result may include attributes such as a search condition, a sort condition, a limited number of rows, and data.

  In the preferred embodiment of the present invention, for control comparison, the system reads the corresponding control information in the browser and compares the read information with the prediction result.

  In the case of comparison of column data, the system reads the corresponding column data in the browser and compares the read information with the prediction result.

  In the case of database comparison, the system reads data in a predetermined database and compares the read information with a prediction result.

  In the preferred embodiment of the present invention, in step S5, it is determined whether or not the current operation has been successfully executed. If the operation is successful, the operation result associated with the current operation is saved, and then the execution of step S5 is continued. On the other hand, if the test is not successful, the test for the current case is terminated, the process proceeds to the next test case, and the process returns to step S1.

  Specifically, in the preferred embodiment of the present invention, if execution of the current operation is successful, it automatically proceeds to the next test operation in the same current case and executes (continues execution of step S5). And the operation result that has been successfully executed is saved.

  If execution of the current operation fails, the test for the current case is terminated, and the test proceeds to the next test case (returns to step S1). That is, the subsequent test operation corresponding to the current case in the operation list proceeds, and the test is started again from the first test operation in the next test case.

  In a preferred embodiment of the present invention, when an operation result in one current operation is completed, a browser display page (that is, a page representing the operation result) is saved as a screenshot, and the current operation is supported in the screenshot. Indicates the position of the control to be performed (based on the previous control specified).

  In the preferred embodiment of the present invention, in step S5, the corresponding comparison result is stored as the test result of the current operation, and then proceeds to the next test operation. If the next test operation that has proceeded indicates an operation for the entire control, the process returns to step S4.

  In the preferred embodiment of the present invention, in step S5, the corresponding comparison result is stored as the test result of the current operation, and then proceeds to the next test operation.

  In a preferred embodiment of the present invention, the test case generation method is applicable to any mainstream software system. This is an implementation form of the driving method that the mainstream software system needs to use in the database of test cases, test operations, test controls, test screens, etc. that are set in advance so as to guarantee the driving of the operation method of the mainstream software system. This is because it is guaranteed in advance.

The above are only preferred examples of the present invention, and do not limit the scope of the embodiment and protection of the present invention. A person skilled in the art is aware that any method obtained by equivalent replacement or obvious change implemented using the contents of the specification and drawings of the present invention is included in the scope of protection of the present invention. obtain.

Claims (17)

A test case automatic generation method, wherein a plurality of base test cases are set in advance, each base test case includes a plurality of base test operations, and each base test operation includes a normal value including 0 to a plurality of normal values. There is one value list and one error value list containing 0 to multiple error values,
For one base test case, a plurality of different derived test operations are performed by changing the numerical value of each of the base test operations based on the normal value of the normal value list or the error value of the error value list. And forming a plurality of different derived test cases associated with the base test case based on a plurality of different derived test operations,
All the base test cases and all the derived test cases are used as test cases, and all the base test operations and all the derived test operations are used as test cases, and the system is based on the test cases and the test operations. An automatic test case generation method characterized by performing an automatic test. In the test case automatic generation method, for the base test case,
Selecting one of the base test operations in the base test case as an extended test operation; and
Selecting one of the normal values from the normal value list associated with the extended test operation; and
Determining whether the selected normal value is the same as the value of the extended test operation, and if it is the same, step A3 returning to step A2;
Assigning a value to the extended test operation based on the selected normal value to form the derived test operation; and
Step A5 combining the derived test operation and all the base test operations other than the extended test operation in the base test case to combine them to form one derived test case;
It is determined whether or not the unselected base test operation exists in the base test case, and if it exists, the process returns to step A1, and if not, step A6 is executed. The test case automatic generation method according to claim 1. In the test case automatic generation method, for the base test case,
Step B1 of selecting one of the base test operations in the base test case as an extended test operation;
Selecting one of the error values from the error value list associated with the extended test operation; and
Determining whether or not the selected error value is the same as the value of the extended test operation, and if so, step B3 returning to step B2;
Assigning a value to the extended test operation based on the selected error value to form one of the derived test operations;
Step B5 combining the derived test operation and all the base test operations other than the extended test operation in the base test case to combine them to form one derived test case;
It is determined whether or not there is an unselected base test operation in the base test case, and if it exists, the process returns to step B1, and if not, step B6 is executed. The test case automatic generation method according to claim 1.   For each of the base test operations in the base test case, by assigning a value to the base test operation using the error values of the corresponding error value list one by one, the corresponding derived test operation is performed one by one The test case automatic generation method according to claim 1, wherein all the derived test operations are combined to form one derived test case. In the test case automatic generation method, for the base test case,
Selecting one of the base test operations in the base test case as an extended test operation; and
Forming one of the derived test operations by assigning an empty value to the extended test operation; and
Based on all of the base test operations other than the extended test operation in the base test case and the derived test operation, and combining them to form one derived test case; and
It is determined whether or not the unselected base test operation exists in the base test case, and if it exists, the process returns to step C1, and if not, step C4 is executed. The test case automatic generation method according to claim 1.   For each base test operation in the base test case, the corresponding test test operation is generated one by one by assigning an empty value to the base test operation, and all the derived test operations are combined into one The test case automatic generation method according to claim 1, wherein the derived test case is formed. A plurality of the test cases are arranged in order, each of the test cases corresponds to a plurality of the test operations to be executed in order, one test control corresponds to each test operation, and each test operation One operation method corresponds to each, one test screen corresponds to each test control, a plurality of prediction results correspond to each test operation,
A test operation list is formed by arranging all the test operations corresponding to all the test cases to be executed this time in the execution order of the test cases,
A method for performing an automatic test of a system based on the test case and the test operation is as follows:
Selecting one test operation as the current operation from the operation list, and performing a test with the test case corresponding to the current operation as the current case;
A step of identifying the display screen by comparing the number of the display screen of the system browser in the test process with the number of the test screen corresponding to the current operation;
Obtaining from the identified display screen the test control matching the current action as a current control; S3;
Step S4 of outputting an operation result corresponding to the current operation after operating according to the operation method corresponding to the acquired current control based on the operation attribute of the current operation;
The operation result is compared with the prediction result corresponding to the current operation to determine whether the current operation has been successfully executed, and the corresponding comparison result is stored as the test result of the current operation. The test case automatic generation method according to claim 1, further comprising step S <b> 5.   In the step S1, when the first test operation associated with the current case is executed, the test screen corresponding to the first test control of the current case is extracted as a start screen. 8. The test case automatic generation method according to claim 7, wherein the test of the current case is started by opening the start screen at an address associated with the start screen.   In step S1, before executing each test operation associated with the current case, it is necessary to open the test screen of the test control corresponding to the test operation based on the operation attribute of the test operation. 8. The method for automatically generating a test case according to claim 7, further comprising: determining whether or not there is an address, extracting an address associated with the test screen as necessary, and opening the test screen. In step S1, the database associated with the current case is used to extract initialization data of the current case after considering the test case as the current case and to start testing the current case. Initialize the data of
The address of the test screen corresponding to the first test control of the current case is extracted as the start address of the start screen, and the start parameter associated with the current case is used based on the start address 8. The test case automatic generation method according to claim 7, wherein the start screen is opened and the test of the start screen is executed.   Specifically, the step S2 acquires the number of the test screen corresponding to the test operation subsequent to the current operation, and monitors the number of the display screen, so that the number of the display screen is the test screen. 8. The test case automatic generation method according to claim 7, wherein the display screen is specified by determining that the display screen has been successfully switched when the number matches the number of the display screen.   Specifically, the step S2 obtains a number corresponding to the test screen subsequent to the current operation and monitors the number of the display screen so that the number of the display screen matches the number of the test screen. The test case automatic generation method according to claim 7, wherein if it is, the display screen is identified as being successful in switching the display screen.   In step S3, after obtaining one test control in the display screen, a matching result is obtained by matching the control attribute of the test control with the control attribute of the test control corresponding to the current operation. The test case automatic generation method according to claim 7, wherein when the matching result indicates successful matching, the acquired test control is specified as the current control. In the step S4, before operating the control, the operation attribute of the current operation is first determined, and an operation for the current control is determined based on the operation attribute.
When the operation attribute of the current operation is a value setting, an operation performed on the current control is to give a value to the control,
When the operation attribute of the current operation is execution of an operation command, an operation performed on the current control is execution of the operation command for operating the control,
If the action attribute of the current action is sending a string message, operate the current control to send the corresponding string message;
If the operation attribute of the current operation is a memory copy, store the value of the current control in system memory;
If the operation attribute of the current operation is a memory value assignment, change the value of the current control to a value stored in the system memory;
When the operation attribute of the current operation is a logical determination, a determination is made as to an expression for indicating a given value stored in the system memory, and a preset value associated with the current operation is determined based on the determination result Skip the subsequent test operation,
When the operation attribute of the current operation is execution of an operation by a combination of function keys, the current control is operated by transmitting a corresponding function key combination command to an input device of the system. The test case automatic generation method according to claim 7. In the step S5, the operation result and the prediction result are compared according to the type of the operation result,
When the operation result is a result of operating the control included in the display screen, the system reads information on the control corresponding to the display screen in the browser and compares the read information with the prediction result. ,
When the operation result is a result corresponding to the browser column data, the system reads the corresponding column data in the browser, compares the read information with the prediction result,
8. The test case automatic according to claim 7, wherein when the operation result is data in a database of the system, the system reads the data in the database and compares the read information with the prediction result. Generation method.   In step S5, it is determined whether or not the execution of the current operation has been successful. If successful, the operation result associated with the current operation is saved, and then the execution of step S5 is continued. 8. If not successful, the test of the current case is terminated, the process proceeds to the next test case, and the process returns to step S1. .   In the step S5, after the corresponding comparison result is stored as the test result of the current operation, the process proceeds to the next test operation, and the next test operation that has progressed indicates an operation for the entire control. 8. The method of claim 7, wherein the method returns to step S4.