(KATE-1705) Introduction & Recommendations

When using and upgrading a SAP system, an extensive amount of manual testing is required, which consumes time, resources and manpower. The main advantages of automated testing are:

1. Reduction in time to perform the necessary tests
2. Time saved can be reinvested into higher priority projects
3. Extensive and complete testing

One solution that can provide the automation of testing is our tool KATE (abbr. of Kit for Automated Testing). KATE by DataVard is a tool for automated tests in frontend testing based on WebTemplate testing and backend testing for various scenarios.

Frontend Testing can be used for the Web Template regression testing to ensure all basic functionalities remain functional despite the changes in the development. Backend Testing offers following functionalities:

• Test query outputs on a large scale – Query testing is based on an idea of using a before image and an after image. These images contain results of all the selected queries/bookmarks, which are then stored for later comparison. The after images and before images are then compared to check if both results are the same. The testing of the same queries between two different systems is also supported with the use of RFC functionality.
• Test InfoProviders content – Involves the Execution of ListCubes with specified characteristics selections. All key figures are always returned while settings for the DB aggregation, Read NLS, MAX Rows and Number of Hits can also be applied. Results of ListCube execution are stored as before/after images and are compared for similarity. Testing the same queries between two different systems is also supported with the use of RFC functionality.
• Test of transformations – is for the Generation of Data Transfer Processes (DTP) and their execution. From the loaded data, the before and after images are created for comparison. By executing the same load two times you can verify if these were performed correctly or if there were any changes made in the transformation logic (changes in lookups, runtimes and other). 
• Test table content – Involves the creation of data images for Database Tables with specified fields. These fields are used either as characteristics or aggregated key figures columns; the images created are stored and compared for similarity. The testing of the same tables between different systems is also supported with use of RFC functionality.
• Test report outputs – Involves the execution of reports with/without variants and the gathering of their outputs that are saved in the spool.

Backend Testing can be used to ensure that after changes in the systems (i.e. system upgrade, migration) were made the data remains unchanged.

Prerequisites and installation

The KATE tool is supplied to the customers in the form of a transport requests with all available functionalities included. DataVard’s Reuse Library is also provided together with KATE and is necessary for the customers that did not receive it yet with other DataVard tools.

All users working with KATE should have authorization “DVD_KATE” assigned, that is included in KATE installation transports.

KATE Restrictions

KATE Terminology

In this section, basic terminology used in KATE tool is described for better understanding of following chapters.

Test Case – is a basic testing scenario, and the Test Case is a reusable component used in Test Plans, where the Test Cases are executed. See the chapter about Test case types for further information. Each Test Case is a schema of steps, while steps are defined by variant/variants. Example Test Case 1:

• Type: ABAP Test Case
• Schema: Execute program CONVERSION_CHECK

Example Test Case 2:

• Type: ListCube Test Case
• Schema: Create Images for InfoProviders and compare them

Test Case Variant – is the definition of a Test Case step with values that enable the Test Case execution in a Test Plan.  The Test Case can be defined by one variant or by multiple. 

Example Test Variant 1:

• Variant: Execute program CONVERSION_CHECK with standard program variant ‘ALL’ (selection screen options)

Example Test Variants 2:

• Variants: InfoProvider ZDC_CUBE1, InfoProvider ZDC_DSO1

Test Plan – specifies combination of Test Cases that can be executed. Test Cases (with variant/variants) assigned to Test Plan have their execution status.

Initial KATE Setup

KATE supports several Test Case types, not all of which may be relevant for you. Therefore, the customization transaction /DVD/KATE_SETUP provides options to only display the Test Cases that are relevant.

_{Kate setup}