(KATE-1705) Settings

Owned by Copy Page Tree
Last updated: Sept 28, 2022 by Marian Vidra

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.



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


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

DrillDown

Listcube

Query

Report

Table

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.



Test Plan Specific Settings



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.



Test Case types in Test Plans tab


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



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")

Items per Page – is Design Studio BOBJ document property which needs to be set in KATE to ensure proper function of scroll in document table during test case execution. To get this property, you use the BusinessObjects Central Management Console > select 'Applications' > right click on the 'Design Studio Runtime' > select 'Manage Properties' > copy value of field 'Items Per Page' into parameter in KATE Front End settings.

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)


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. 



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.