(DV-1902) ERP Report Execution & Backend

ERP Report Test Case Execution

When an ERP Report Test Case is added to a Test Plan then a new backend Test Run is automatically created and a Run ID is generated. The description holds the technical name of the Test Plan and the Test Case. All of the Report Variants selected during the creation of ERP Report Test Case are automatically added into Report Variant selection for the generated Test Run.

To execute an ERP Report Test Case from the Test Management click on Execute , which will display the standard ERP Report Testing scenario.

Report based testing

The Report based testing scenarios execute and focus on the ERP standard reports, with or without variants. 

The reports are executed with background jobs and their output is saved to spool. The outputs are then read after the execution and are compared based on your preferred settings. 

Recommendations:

  • A maximum of 1000 ERP Report variants should be used for one ERP Report testing run.

Test scenario EQS_ERP (Report testing)



Report Testing Scenario

Report testing contains following steps:

  1. Selecting Report Variants
  2. Generation of before image tasks
  3. Creation of before images
  4. Performing specific task in system outside Validate (like conversion, migration, etc.)
  5. Generation of after image tasks
  6. Specifcation of  comparison settings
  7. Generation of comparison tasks
  8. Execution of comparison tasks
  9. Display of results

Select Report Variants

By double clicking on the first Test Step Select Report Variants you can define which Report variants are to be used in the specified Test Run for testing, or you can create new Report Variants. 
Once you have the variants selected for the Test Run you need to save the selection by clicking on the button Save  (Ctrl + S) in main screen of the Report variants selection.
You can add Report Variants in the following ways:
Create New Report Variant –  you can create new Report Variant by clicking on Create New Report Variant button (Shift + F4). For more information please refer to Create New Report Variant section . 
Add Existing Report Variant – you can display all of the existing Report variants in system and by clicking on the Add Existing Report Variant button (SHIFT + F5), select one or more variants to be added into the Test Run. 
Add Report Variants of Run – by clicking on the Add Report Variants of Run button (SHIFT + F6) you can select another (distinct from current) run, and add all of the Report Variants used in this Test Run also into the current Test Run. 
Copy Report Variants of Run – by clicking on the Copy Report Variants of Run button (SHIFT + F8) you can select another (distinct from current) run, and add all of the Report Variants used in this Test Run also into the current Test Run as copies. 
Add Variants of Test Case – by clicking on the Add Variants of Test Case button (SHIFT + F11) you can select existing Test Case, and add all of the Report Variants used in this Test Case into the current Test Run.
Copy Variants of Test Case – by clicking on the Copy Variants of Test Case button (SHIFT + F12) you can select existing Test Case, and add all of the Report Variants used in this Test Case into the current Test Run as copies. 
Copy Variants – please refer to Copy Variants section for function details.

Generate tasks for before image

You can execute generation of tasks by double click on generate step or selecting generate step and click on Execute  button. This will prepare the tasks for the following step Create before images.

Create before images

By double clicking on this step, you first define number of background jobs to be used to create the before image for each of the specified Report variants. Then data images of report outputs for each selected variant will be created and saved.

Generate tasks for after image

You can execute generation of tasks by double click on generate step or selecting generate step and click on Execute  button. This will prepare the tasks for the following step Create after images.

Create after images

By double clicking on this step, you first define the number of background jobs to be used in the creation of the after image of the specified Report variants. Then data images of report outputs for each selected variant will be created and saved.

Set Comparison settings

By double clicking on this step you can define some standard settings that should be used during comparison of reports output. 



Figure 214 Report comparison settings


You can define:

  1. Report comparator type – Datavard Validate comes by default with one report comparator (Simple Report Comparator) that compares output of report row by row. You can also select your own comparator implementation to be used. To create your own BADI comparator you need to create implementation of Validate /DVD/EQS_BADI_REP_COMP BADI. See (DV-1902) ERP Report - BADI comparator page for more information.
  2. Ignore TimeStamps – Datavard Validate default report comparator is capable of ignoring time stamps in number of standard formats that often cause difference in output of reports as they are executed in different times.
  3. Compare only table data – Datavard Validate default report comparator can ignore headers of standard reports and compare only actual table data saved in spool output of executed reports.

You save the specified compare setting by clicking on Enter button.

Generate tasks for comparison

You can execute generation of tasks by double click on generate step or selecting generate step and click on Execute  button. This will prepare the tasks for the following step Compare before and after images.

Compare before and after images

You define the number of background jobs to be used for tasks execution. Each of the tasks compares the before image data with the after image data for one Report Test Variant, please refer to the Comparison logic section.

Display of results

By clicking on this step you can review the output and comparison results of reports executed in steps before. There are some differences between report testing scenario and other scenarios, which are specified more in detail in section Reports Display Results.