(KATE-146) Settings

Owned by Lenka Mackovicova
Last updated: Jul 18, 2017 by Jan Sliacky (Deactivated)
7 min read

In KATE setting you can manage various settings for all parts of KATE tool. You can access the Settings in KATE Dashboard by clicking on corresponding button, or by pressing Shift+F5.



Figure 258: KATE Settings 


Settings are divided into Tabs based on the area they are focusing on:

  • KATE Backend Settings
  • KATE Test Management Settings
  • KATE Web Intelligence Settings


Figure 259: Inside KATE Settings

KATE Backend Settings

In the KATE Backend settings tab, you can manage parameters for KATE Backend test scenarios separately by 'Edit' button and customize reporting statuses as described in section 8.8.5 ('Reporting Status'). Parameters are divided into folders per test scenario. Individual settings are described in next subchapter. 
KATE Backend Settings Parameters:

DTP

  • DTP Load Wait Time
    • Used in Background Testing. This is the maximum wait time (in seconds) to check if a DTP load finished. When the wait time is exceeded a warning is raised and status should be checked manually.
  • Max. disp. DTP row count
    • Maximum lines to be displayed at once in Transformation testing scenario 'Display results' step.
  • DataSource Parallel Extraction
    • If this option is set to 'X' DTPs generated in a transformation testing scenario that loads from DataSource will use parallel extraction. This option works only on releases > 7.00.
  • Generated DTP desc. Prefix
    • Prefix that is added into DTP description when generated using KATE. Maximum of 8 characters can be used here.
  • DTP With Archive Option
    • If this option is set to 'X' the DTPs generated by KATE in the transformation-testing scenario is created with an extraction option 'Active Table (With Archive)'. If this setting value is left empty DTPs that are created with an extraction option 'Active Table (Without Archive)'. This applies for DTPs created on top of transformations where the source is a DSO object. For transformations with InfoCube as source this setting is applied only on releases >=7.30.
  • Compare only first Lookup Pcg.
    • If this option is set to 'X' only data of the first package for each lookup will be saved and compared if lookup testing functionality is used.

DrillDown

  • DrillDown additional aggr.
    • If this setting is set to 'X' KATE executes - additional aggregation after each DrillDown image is created.
  • Drill Down Maximum Records
    • Maximum number of distinct characteristic values that should be selected and used as filter in next test cycle for Drill Down testing.
  • Max. disp. Drilldown row count
    • Maximum lines to be displayed in the DrillDown testing scenario 'Display results' step.

Listcube

  • ListCube additional aggreg.
    • If this setting is set to 'X' KATE executes - additional aggregation after each ListCube image is created.
  • ListCube decimal places
    • Number of decimal places to be displayed/compared in ListCube testing scenario. Possible values 0 to 14.
  • Max. disp. ListCube row count
    • Maximum lines to be displayed at once in ListCube/SLO ListCube testing scenario 'Display results' step.
  • ListCube Compare Threshold
    • Threshold value for the ListCube output comparison. If the difference between the Before and After image values is smaller than the threshold set, then the comparison is evaluated as correct. Possible values are float values greater than 0.
  • Max. ListCube image row size
    • Maximum number of rows that will be saved during the creation of a ListCube/SLO ListCube image. If this threshold is reached no more rows are saved and the image creation ends with error. This is safety check to prevent too many resources be eaten up with non-defined variants.
  • Do not use BWA for ListCube
    • If this setting is set to 'X' the KATE ListCube execution will not consider the usage of BWA when reading the data from InfoProviders.
  • ListCube Relative Threshold
    • Relative threshold value in percentage for ListCube output comparison. If a difference between the Before and After image values is smaller than the set percentage of the bigger value, the comparison is evaluated as correct. Possible values are float values greater than 0 and smaller then 100.
  • ListCube RowCnt Precise Comp.
    • If this option is set to 'X' RowCount columns in ListCube/DrillDown images will be compared without the use of acceptable threshold differences.

Query

  • Query decimal places precision
    • Number of decimal places to be displayed/compared in Query testing scenario. Possible values 0 to 14.
  • Run Queries in dialog
    • If this option is set to 'X' Query Variants are executed in dialog processes. Running Query Variant in dialog enables queries to be parallelized. Note that it is not possible to run Query Variants in dialog through RFC.
  • Max. disp. Query row count
    • Maximum lines to be displayed at one time in Query testing scenario 'Display results' steps
  • Query Relative Threshold
    • Threshold value for Query output comparison. If there is a difference between Before and After image and the value is smaller than this threshold comparison is evaluated as correct. Possible values are float values greater than 0.

Report

  • Max Displayed Report Row Count
    • Maximum lines to be displayed in the report of the testing scenario 'Display results' step.

Table

  • Table RowCount Precise Compare
    • If this option is set to 'X' RowCount columns in Table variant images will be compared without the use of acceptable threshold differences.
  • Table Decimal Places Precision
    • Number of decimal places to be displayed/compared in the Table testing scenario. Possible values 0 to 14.
  • Max. disp. Table row count
    • Maximum lines to be displayed at once in Table testing scenario 'Display results' steps
  • Max. Table image row size
    • Maximum number of rows that will be saved during the creation of a Table image. If this threshold is reached no more rows are saved and the image creation ends with error. This is safety check to prevent eating up too many resources with non-defined variants.
  • Table Compare Threshold
    • Threshold value for the Table output comparison. If a difference between the Before/After image values is smaller than this threshold then the comparison is evaluated as correct. Possible values are float values greater than 0.
  • Table Relative Threshold
    • Threshold value for Table output comparison. If there is a difference between Before the After image values is smaller than this threshold comparison is evaluated as correct. Possible values are float values greater than 0.
  • Table Own Aggregation
    • If this option is set to 'X' KATE uses own aggregation instead of DB aggregation during image creation. This option should be used when standard aggregation fails (e.g. numeric overflows).

Other

  • Mass Execute Seq. Wait Time
    • Maximum number of seconds KATE waits for the test step to finish when the mass execution of Test Cases is sequential.

For KATE Backend Test Cases you can set settings specific for a given Test Plan, which will override general settings.



Figure 260: Test Plan Specific Settings



Figure 261: Inside KATE Test Plan Specific Settings 

Test Management Settings

For more information about "Scheduling Checker Settings" see Test Plan Scheduling section, specifically Prerequisites part.
In section "MS Word Templates", MS Word templates for Manual Test Case and for Status Document can be managed.
In section "Parameter Settings", various parameters regarding Test Management can be managed. Currently, one parameter "DISPLAY_TMPL_TYPE" is present, which states whether the Test Case types should be viewed in Test Plan tab.



Figure 262: Test Case types in Test Plans tab


In section "Other Settings", Test Case statuses can be managed.



Figure 263: Test Management Settings

Front End Settings

In the KATE Front End settings tab, you can manage the parameters for KATE Front End (Web Templates, Web Intelligent, Design Studio) scenario. Individual settings are described in the next subchapter. 
General Settings Parameters:

  • Excel settings
    • Excel time out limit – represents how long excel should look for a particular html element – table, tab on screen ( needed because screens are build by java script which don't trigger any event when screen is finished with loading)
  • Execution settings
    • Repeat execution in case error – represents how many times will be test case executed when execution ends with error

Bobj server Settings Parameters:

    • In this option, you can define the server address and ports for BOBJ and provide a description. It is possible to specify multiple servers and also test connection directly from here by pressing Test connection button

Design Studio Settings Parameters:
Java bin path – when creating variants from documents that are saved on NetWeaver, java is required for file translation. Its necessary to specify path to your java on system. Sometimes keyword shortcut for this path might be created and in that case you can put in that keyword (usually "java")



Figure 264: Front End Settings

HP ALM Integration Settings

In the KATE HP ALM Integration settings tab, you can set the following values that are required for replication of KATE objects to HP ALM server: 

  • Connection settings
    • URL with port – URL path to HP ALM server together with port used for standard web browser connection to this server (usually 8080)
    • ALM domain – HP ALM domain where KATE objects will be replicated
    • ALM project – HP ALM project where KATE objects will be replicated
  • User settings
    • User name and password that exists in HP ALM server and is authorized to access ALM domain and project.
    • Password is optional and when it is entered, it is stored in a non-readable form. When no password is entered, you are prompted with a password pop-up when executing the replication.
  • Integration settings
    • Test case path – folder in HP ALM Test Plan area, where all KATE Test cases will be replicated
    • Test plan path – folder in HP ALM Test Lab area, where all KATE Test plans will be replicated
  • Status mapping
    • Table with all KATE Test case and Test plan statuses that can be mapped to HP ALM statuses (F4 help supported)


Figure 265: HP ALM Integration Settings 

Interface for Backend Variant Generation

KATE comes with the option to generate backend variants from custom ABAP programs. If you want to generate any backend variants Query/ListCube/DTP/Table/Drill Down from your own ABAP program, you can use KATE API classes available in /DVD/EQS_GEN package. Each of these classes contains one method 'Generate' that generates appropriate type of variant based on importing parameters supplied. 



Figure 266 KATE API for variants generation package


For each type of backend variant, a demo report also exists, which contains comments and example how these classes can be used to generate variants directly from ABAP.
Reports:
/DVD/EQS_GEN_DRILL_VARIANTS – demo report for generation of Drill Down variants
/DVD/EQS_GEN_DTP_VARIANTS – demo report for generation of Transformation testing variants
/DVD/EQS_GEN_LISTCUBE_VARIANTS – demo report for generation of ListCube variants
/DVD/EQS_GEN_QUERY_VARIANTS – demo report for generation of Query variants
/DVD/EQS_GEN_TABLE_VARIANTS – demo report for generation of Table variants 

KATE Backend Testing User Authorization

As in KATE Backend testing you can create snapshots of data from all the available system InfoProviders, queries and tables. For users therefore it is sometimes necessary to restrict their access to this information. 
KATE Backend testing provides three BADI Definitions that you can implement using your own logic to deny access to restricted data images. The following BADIs are available in package /DVD/EQS:

  • /DVD/EQS_BADI_AUTH_INFOPROV – BADI that restricts access to image data for ListCube, DrillDown and Transformation testing variants based on InfoProvider name.
  • /DVD/EQS_BADI_AUTH_QUERY – BADI that restricts access to image data for Query testing variants based on query technical name.
  • /DVD/EQS_BADI_AUTH_TABLE – BADI that restricts access to image data for Table testing variants based on DB table technical name.

In a BADI implementation class, the exception /DVD/CX_EQS_AUTH should be raised when a user is not allowed to review data of specific image.