CN103914384A - Automatic request-change driven testing method - Google Patents

Abstract

The invention discloses an automatic request-change driven testing method. The automatic request-change driven testing method includes starting from a request generated after each change of an SAP (systems, applications and products in data processing) system and analyzing development objects included in the request; pegging influence scope of the objects in corresponding manners according to different types of the development objects, considering multi-hierarchy quotations of some program objects, gathering the entire influence scope of the change request, and accordingly, automatically generating a test plane so as to drive implementation of automatic testing. By the automatic request-change driven testing method, testers can quickly but accurately determine the influence scope of the change, and test efficiency can be greatly improved.

Description

A kind of demand changes the automated testing method driving

Technical field

The present invention relates to a kind of automated testing method, specifically a kind of demand providing for SAP tester changes the automated testing method driving.

Robotization type of drive, location requirement changes coverage fast and accurately, drives the execution of automatic test with this.

Background technology

Along with being on the increase of company ERP system secondary development, the complexity of software test, test period and testing cost are also more and more higher.For this reason, many enterprises adopt the means of automatic test one after another, to improving testing efficiency, reduce labour cost.

At present, automatic test is mainly driven by following three kinds of modes:

1) simple recording/replaying: by instrument, the process of operation and data are recorded by the mode of recording, carried out afterwards the process that playback can analog manual operation.Data under this pattern and script mix into together with, almost a corresponding test case of script, causes maintenance cost very high.Even if simple variation occurs at interface, script also must be recorded again, and reusable rate is low.

2) automatic test of data-driven (datadriven): by by variable parameter, import data file into test script, test data is corresponding one by one with test case.This pattern has realized the problem of test script and data, has greatly improved utilization factor and the maintainability of script, but its be subject to interface change impact still very greatly.

3) key word drives the automatic test of (keyworddriven): it is the one improvement type of data-driven test that key word drives test, and it decomposes test logic according to key word, form data file, the service logic of the corresponding encapsulation of key word.Key word mainly comprises three types: operand (Item), operation (Operation) and value (value), can show as Item.Operation (Value) by OO form.Key word has also realized on the basis of data-driven script and data separating that testing inner object separates with interface element, test description separates with specific implementation details.

The driving of above-mentioned three kinds of forms is all intended to improve the reusability of script, but for needs carry out many wheel regression tested situations, tester is after each programing change, still need the coverage of artificial determining program, then the program in coverage is tested one by one, its automaticity is still not high.On the other hand, owing to there being the multiple conventional development objects such as Domain, DataElement, Table, Class, Program in SAP system, meanwhile, certain development object may also can be quoted other development objects again, occurs repeatedly the situation that recurrence is quoted.At this moment, the mode that tester often combines by self experience and manual search is searched its coverage, last designing and write test plan by artificial mode accordingly, so not only wastes time and energy, and be easy to cause omission, make defect be difficult to timely discovery.

Summary of the invention

For the problem running in SAP system testing, the object of this invention is to provide a kind of demand and change the automated testing method driving, by the method, tester can determine the coverage changing fast and accurately, significantly improves testing efficiency.

Object of the present invention is achieved through the following technical solutions:

Demand changes the automated testing method driving, and it is characterized in that the method comprises the following steps:

1) obtain the request of change number;

2) get development object lists all under this request by the transmission number of request;

3) judge whether object is empty, and sky is jumped out end if;

4) each object of circulation fetch program list object;

5) judge object type, Domain goes to 6); Class goes to 13); Include goes to 10), other, go to 13);

6) the counter development object of looking into the development object of quoting this Domain type;

7) the counter development object of looking into the development object of quoting this field type;

8) the counter development object of looking into the development object that refers to this form types, goes to 13);

9) judge the particular type of this class object: if whole class goes to 13); If the attribute of class goes to 13); If the method for class goes to 11);

10) development object of the counter mainprogram type of looking into the development object of quoting this include type;

11) the anti-class that refers to the method for looking into;

12) obtain all methods under such;

13) the anti-development object referring to of looking into;

14) the anti-development object of finding is added in output listing;

15) judge in list, whether next development object is empty: empty if, go to 16), if non-NULL goes to 5);

16) export all affected development object inventories under this transmission request;

17) generate test plan according to the anti-list object of looking into;

18) call corresponding test script in test plan, carry out automatic test.

The present invention is from the each request producing after changing of SAP system, the development object comprising under analysis request.Then for the counter coverage of looking into this object of the corresponding mode of dissimilar employing of development object, consider the situation that some program object multi-layer is quoted simultaneously, finally gather the coverage that produces whole change request, thereby automatically generate test plan, drive the execution of automatic test with this.

By the present invention, tester can determine the coverage changing fast and accurately, significantly improves testing efficiency.

Accompanying drawing explanation

Fig. 1 is that demand changes the process schematic diagram that drives automatic test.

Embodiment

Demand changes the automated testing method driving, and the realization that demand drives has adopted two classes, transmission request class (use class ZP001CL_TRANSREQ definition in the present embodiment, but be not limited to this title); The anti-class (use class ZP001CL_WHERE_USED definition in the present embodiment, but be not limited to this title) of looking into.

The function of transmission request class ZP001CL_TRANSREQ main method is as follows:

GET_TRANS_INFOR: the transmission information that obtains request;

GET_PRO_VERSIONS: the version information that the request of obtaining is corresponding;

SET_E07T: obtain object text;

GET_AS4TEXT: obtain request text;

GET_COLLECTION: obtain object set;

GET_INCLUDE_PROGRAMS: obtain the development object comprising.

The counter function of looking into class ZP001CL_WHERE_USED main method is as follows:

GET_WHERE_USED_DOMA: obtain the development object of quoting Domain type;

GET_WHERE_USED_FIED: the development object that obtains reference field type;

GET_WHERE_USED_TABL: obtain the development object of quoting form types;

GET_WHERE_USED_INCL: obtain the development object of quoting include type;

GET_WHERE_USED_ClAS: obtain the development object of quoting include type;

GET_WHERE_USED_PROG: obtain the development object of quoting Program type;

GET_WHERE_USED_LIST: obtain the lower all affected development objects of transmission request.

As shown in Figure 1, the concrete steps of demand change driving process are as follows:

Step1: obtain the request of change number.

Step2: get development object lists all under this request by the transmission number of request.Transmission request number:

SAP is used for managing the one mechanism of transmission procedure, configuration, is similar to version number.

Step3: judge whether object is empty, and sky is jumped out end if.

Step4: each object of circulation fetch program list object.

Step5: judge object type: Domain goes to Step6; Class goes to Step13; Include goes to Step10, and other, go to Step13.

Step6: the counter development object of looking into the development object of quoting this Domain type.

Step7: the counter development object of looking into the development object of quoting this field type.

Step8: the counter development object of looking into the development object that refers to this form types, goes to Step13.

Step9: the particular type that judges this class object: if whole class goes to Step13; If class

Attribute, go to Step13; If the method for class goes to Step11.

Step10: the development object of the counter mainprogram type of looking into the development object of quoting this include type.

Step11: the anti-class that refers to the method for looking into,

Step12: obtain all methods under such.

Step13: the anti-development object referring to of looking into.

Step14: the anti-development object of finding is added in output listing.

Step15: judge in list, whether next development object is empty: empty if, go to Step16, if non-NULL goes to Step5.

Step16: export all affected development object inventories under this transmission request.

Step17: generate test plan according to the anti-list object of looking into.

Step18: call corresponding test script in test plan, carry out automatic test.

By the present invention, tester can determine the coverage changing fast and accurately, significantly improves testing efficiency.

Claims (4)

1. demand changes the automated testing method driving, and it is characterized in that the method comprises the following steps:

1)obtain the request of change number;

2)get development object lists all under this request by the transmission number of request;

3)judge whether object is empty, and sky is jumped out end if;

4)each object of circulation fetch program list object;

5)judge object type, Domain goes to 6); Class goes to 13); Include goes to 10), other, go to 13);

6)the counter development object of looking into the development object of quoting this Domain type;

7)the counter development object of looking into the development object of quoting this field type;

8)the counter development object of looking into the development object that refers to this form types, goes to 13);

9)judge the particular type of this class object: if whole class goes to 13); If the attribute of class goes to 13); If the method for class goes to 11);

10)the development object of the counter main program type of looking into the development object of quoting this include type;

11)the anti-class that refers to the method for looking into;

12)obtain all methods under such;

13)the anti-development object referring to of looking into;

14)the anti-development object of finding is added in output listing;

15)judge in list, whether next development object is empty: empty if, go to 16), if non-NULL goes to 5);

16)export all affected development object inventories under this transmission request;

17)generate test plan according to the anti-list object of looking into;

18)call corresponding test script in test plan, carry out automatic test.

2. demand according to claim 1 changes the automated testing method driving, and it is characterized in that: described class comprises, transmission request class and the anti-class of looking into.

3. demand according to claim 2 changes the automated testing method driving, and it is characterized in that: in transmission request class, use class ZP001CL_TRANSREQ definition; Counter looking in class, is used class ZP001CL_WHERE_USED definition.

4. demand according to claim 3 changes the automated testing method driving, and it is characterized in that:

Transmission request class ZP001CL_TRANSREQ comprises as follows:

GET_TRANS_INFOR: the transmission information that obtains request;

GET_PRO_VERSIONS: the version information that the request of obtaining is corresponding;

SET_E07T: obtain object text;

GET_AS4TEXT: obtain request text;

GET_COLLECTION: obtain object set;

GET_INCLUDE_PROGRAMS: obtain the development object comprising;

The anti-class ZP001CL_WHERE_USED that looks into comprises as follows:

GET_WHERE_USED_DOMA: obtain the development object of quoting Domain type;

GET_WHERE_USED_FIED: the development object that obtains reference field type;

GET_WHERE_USED_TABL: obtain the development object of quoting form types;

GET_WHERE_USED_INCL: obtain the development object of quoting include type;

GET_WHERE_USED_ClAS: obtain the development object of quoting include type;

GET_WHERE_USED_PROG: obtain the development object of quoting Program type;

GET_WHERE_USED_LIST: obtain the lower all affected development objects of transmission request.