Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Each query output is separated into rows, with each row split into the key part and data part. The Key part is defined by all the characteristics columns on the left side of the output while all of the other columns define the data part (see Figure 215). 


Key and Data part of query output


When the key/data part creation (images) are is 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; Validate uses the position of the rows position to compare the appropriate rows between both images. When multiple rows have the same Key part, Validate picks the corresponding row from another image. If the corresponding row does not belong to a 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 Validate you can specify the number of decimal places used for the Query results comparison. Please refer to the 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. 


Missing row in another image


All corresponding rows are compared even on the data part. If any differences are found in the data part, the appropriate data cells are colorized with a red color to mark the difference. Only cells in the After image are colorized as the Before Image values are taken as correct ones.


Incorrect data in After image

...

The logic for the ListCube comparison is similar to query comparison. Each row of the ListCube output is split into Key and Data parts. The Key part for ListCube output is also visually distinguished in the output table for better orientation. 


ListCube output Key and Data parts


To prevent any rounding differences, you can use the settings for Validate to specify the number of decimal places used for the comparison of the ListCube results. Please refer to the 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 the Settings chapter to see how this setting can be changed.
The full logic of numeric values comparison is described in the figure below. On the left side is a flow diagram of comparison logic while the right side contains an example of comparison logic.


Validate numeric value comparison flow diagram

...


For the actual data screens, if the 'Only Errors' mode is active, only the rows of output that have at least one cell colorized with red color are displayed. In the Before Image output, the correct rows are also displayed that correspond to After Image rows with wrong data.


ListCube erroneous rows and appropriate before image rows


For the Transformation testing in the before image results, only the corresponding rows in terms of row number are displayed with the erroneous rows of the after image, when the 'Only Errors' mode is active.


Erroneous display in Transformations testing scenario

...

  • No union view is available
  • There are three different formats you can review the reports report's outputs: ALV table, Text Screen, and HTML.

...

Sometimes it is required to display Before/After image outputs in full screen. You can click on the  'Full Screen' button in the application toolbar. To activate the full-screen mode, the results must be already displayed in the standard view. It is possible to navigate through the output result pages (if any) directly in full-screen mode. 


Full-screen mode of variant output

...

In the Output for ListCube, Transformation, and Drill Down test scenarios these can be displayed together in union mode. This is accessible after clicking on  'Union Screen Results Display' button in the toolbar and lets you display two different outputs on one single screen. 


Union screen mode for results display

...

In the output of InfoProviders or database tables, sometimes, when there are differences in results of Before and After Images, it is needed to compare also overall sums of Before/After Image key figures. Instead of manual check of each column, you can click on the button 'Check Sums' and get a comparison of summed key figure values. Fields with different values are highlighted with red, overflown sums are set to 0, and also highlighted with a different colors.  

Compared Table key figure sums with highlighted differences and overflown sum

...

For the Drill Down and ListCube Test Scenario, a column with the name 'Missing' is added to the output of InfoProviders. If a line is not correct in one of the Before/After images because there was no record with the same key found in the After image an icon  is added to the column. This helps you to differentiate between the erroneous and the missing records, you can also use this column for the filtering of results. This column is visible in all three types of results display.
*Important Note: Using standard ALV filtering functionality on the output tables only influences the actually displayed page records and does not influence records of other pages. 


Missing Column

Reporting Status

...


When changing the reporting status, you can choose the reporting status you want to set for variant and add a description. 


Set Reporting Status Dialog

...

4. A new window appears, in the first pop-up, where you can add the type of Test Scenario (you can press F4 for the list of all possible entries). Currently, there are 4 Test Scenarios to choose from. These scenarios are described in the chapter Backend Testing.

...

Double click on the first task in the Select Query Variants and Variants and a new screen appears with several options for adding a new variant. Here you can do the following: 

...

8. After you save the query variant, you can view this in the list of all query variants.


Set query variables

9. Once all your query variants are added, save the selection by pressing the 'Save' button (Ctrl + S), then you can return to the Test Run ID tasks. In the next step, you need to Execute (F8 or double click) Generate tasks for before image, once generated, the first two status icons should be green.

...

Double click on your test case to compare the results of your before and after image. 


Comparing Before and After results 

...