(DV-2311) Introduction & Recommendations

Owned by SNP
Nov 20, 2023

When using and upgrading the SAP system, extensive 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 SNP Validate. SNP Validate 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 Web Template regression testing to ensure all basic functionalities remain functional despite the changes in the development.

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

Testing with SNP Validate offers the following functionalities:

  • Test query outputs on a large scale: Query testing is based on the idea of using a before image and an after image. These images contain the 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 by 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 by 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 others). 
  • 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 by the use of RFC functionality.
  • Test report outputs: Involves the execution of reports with/without variants, doing a snapshot of their outputs as before/after images, and finally comparing for similarity. Only reports with written list outputs without screens are supported now. Based on the layout complexity of outputs and desired precision of comparison you can choose different types of comparators.

SNP Validate Terminology

In this section, the basic terminology used in the SNP Validate tool is described to better understand the 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 (or more familiar SNP Validate's 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 the combination of Test Cases that can be executed. Test Cases (with variant/variants) assigned to Test Plan have their execution status.

Prerequisites

Each test type in SNP Validate may require specific prerequisites for its proper working. Follow the instructions as described in the section SNP Validate Prerequisites before using it.

SNP Validate transactions

The list of common SNP Validate transactions is already predefined and grouped under authorization role /DVD/VALIDATE. By assigning the role to the user, SNP Validate's user menu is displayed in the main SAP user menu. To display it click on the first icon User menu (Ctrl+F10) in the main SAP GUI window.