Page Comparison

Test Scenarios

KATE Validate supports the running of tests in the backend, which are focused on the Query testing, ListCube testing, Drill Down, Transformation, Table, Report and Performance testing. Unlike the Test Scenarios in the frontend, the tests in the backend have the Test Scenarios that are predefined and contain Test Run IDs. 

 
_{KATE Validate Background Testing}

Each Test Scenario focuses on a different aspect of the testing. Currently, there are seven Test Scenarios defined to test Queries, DBtables, Reports, DTP loads/Transformations and InfoProviders using ListCube functionality.

...

_{Reset of all Test Steps of Test Run} 

...

When the key/data part creation (images) are completed for the Before and After image, the corresponding rows are searched using the Key part. 
There are cases when there is no Key part in the query output, in this situation; KATE Validate uses the rows position to compare the appropriate rows between both images. When multiple rows have the same Key part, KATE Validate picks the corresponding row from another image. If the corresponding row does not belong to group of rows with the matching Key part then the output of the row is highlighted with yellow color to indicate the need for a manual check. 
To prevent any SAP rounding differences, in the settings for KATE Validate you can specify the number of decimal places used for the Query results comparison. Please refer to Settings chapter to see how this setting can be changed. 
If a row from either image does not have a matching pair, the alternate image row is colorized with a red color; the data fields are colorized along with the row number. Missing rows can occur in both the Before and After image. 

...

To prevent any rounding differences, you can use the settings for KATE Validate to specify the number of decimal places used for the ListCube results comparison. Please refer to Settings chapter to see how this setting can be changed. 
To prevent float number differences you can set a threshold value. If the difference between the before/after image values is smaller than the threshold value, the comparison is evaluated as correct. Please refer to Settings chapter to see how this setting can be changed.
Full logic of numeric values comparison is described in Figure 219 .On the left side is a flow diagram of comparison logic is displayed while right side contains example of comparison logic.

_{KATE Validate numberic value comparison flow diagram}

...

If the lookup data testing is included in the comparison, then the following logic is applied during the data comparison. Direct Lookup data includes the lookup source data, which is coming into Lookup and the data results that are returned from Lookup. 
The data provided from the DVD Lookup Translator comes in packages because the packages are processed in the transformation. KATE Validate executes the comparison only in cases where the same number of packages is provided by DVD Lookup Translator as for the before and after image. 
Data from each package is then compared independently with the data from other packages. For each package, the lookup source data is compared first. If the source data for the before/after package is not same then the results data is not compared as you can only test the lookup correctness based on the same input. If the source data is the same as for the before/after image of package results data is compared. 
Matching the image is done by the row number of the before/after resource data, when saving the lookup source and the result data, KATE Validate sorts this by all fields to prevent sorting problems.

...

• Before Image Runtime (optional) – runtime of Query/ListCube/DTP load/ Drilldown execution in Before image.
• After Image Runtime (optional) – runtime of Query/ListCube/DTP load/Drill Down execution in After image.
• Difference (optional) – difference in seconds between After image runtime and Before image runtime.
• Result – result of data comparison.
• Reporting Result – reporting status set be KATEValidate/user.
• Before Image Creation Time (optional) – time of before image creation.
• Before Image Creation Data (optional) – date of before image creation.
• After Image Creation Time (optional) – time of after image creation.
• After Image Creation Data (optional) – date of after image creation.
• Before Image Rows (optional) – number of rows of before image.
• After Image Rows (optional) – number of rows of after image.
• Reporting Status Text (optional) – text supplied when KATEValidate/ user set reporting status.
• Variant ID (optional) – KATE Validate technical ID of variant.
• Before Image Status (optional) – Task execution status for the before image
• After Image Status (optional) – Task execution status for the after image
• Before Image Overflow Handled (optional) – notification of overflow occurrence
• After Image Overflow Handled (optional) – notification of overflow occurrence
• Conversion Runtime (optional) – runtime of conversion of Before image in SLO Listcube.

...

Sometimes the 'After Runtime [s]' cells along with the 'Difference' cells are colorized with red colour, this can happen when a there is a difference between the Before image runtime and/or the After image runtime image reaches a threshold value defined in the KATE Validate settings. You can specify these threshold values by clicking on the  button in toolbar.
These settings can have an influence on the comparisons decimal precisions are also applied in the output.
You can display each variant in detail, by right clicking on appropriate variant row and selecting the 'Display Variant' from context menu. 

...

For all scenarios the rows are paired in a way they can be compared together. This can differ based on the scenario i.e. for Transformation testing scenario row numbers are used while for ListCube and Drill Down scenarios the appropriate row keys are matched. 
*Important Note: In the current version of KATE Validate the Query testing scenario does not support Union display mode.

...

It is possible to display the reporting status column in the table with a list of the tested variants for all of the Backend scenarios by changing the layout of the result table. By default this status is always set to the same value as that of the comparison results in KATEValidate, The Reporting status is used to define the statuses of individual Test Cases for reporting. You can set the reporting status and override the compare status set by KATE Validate by clicking on the appropriate Variant result row and then selecting the 'Set Reporting Status' option. 

...

You may want to unify reporting statuses used by test users to reflect acceptable errors (e.g. 'Out Of Scope') it is possible to specify cross KATE Validate reporting statuses. You can define these reporting statuses in KATE Validate settings under 'Backend' settings tab. All customized reporting statuses can then be selected in Set Reporting Status dialog using F4 help. 

...

During the Transformation testing scenario, when KATE Validate is provided with the data from the DVD Lookup Translator, and is using the 'Display Lookup Results' this contains the data and the comparison results. The Structure of this screen is very similar to the standard 'Display Results' screen, however there are some differences:
In 'Display Lookup Results' screen there are two comparison statuses for each line of the DTP variant tested, in some cases there can be multiple lines in a run and for each variant. The number of lines depends on number of data packages that were processed during the load for each variant. The First comparison of the results defines the statuses of the lookup source data for the comparison, while the second defines the statuses of the comparison results from the returned data in the lookup. 

...

1. Run the transaction /DVD/KATE in your SAP BW system

2. In KATE Validate Dashboard screen, choose Backend Testing (last icon on the function panel).

_{Backend Testing}

3. In the KATE Validate Backend Testing screen, choose Create new Test Run ID (F5).

...

11. Once the Create before image task is complete, you can start performing your specific tasks (like archiving, migration, etc.) in your system (outside KATEValidate).

12. Afterwards, the Next step is to execute Generate tasks for after image.

...