...

These settings are advanced and should be changes only after a consultation with Datavard.

• Wait time in logon dialog load

Time in seconds after every change of a window, which is used to detect correct logon dialogs and fill the required fields. This setting is currently relevant for BEx testing.

...

Turns on/off technical logs, which provide more detailed information about the test case execution. This setting is currently relevant for Web Intelligence and available only as a specific setting of a test plan (see 1637844467Test plan specific settings)

• HTML docs load timeout

How long (in seconds)  excel Excel should look for a particular HTML document. This setting is currently relevant for Web Intelligence and available only as a specific setting of a test plan (see 1637844467Test plan specific settings)

• WEBI table load wait limit 

How long (in seconds)  excel Excel should wait to load a particular table in a HTML document. This setting is currently relevant for Web Intelligence and available only as a specific setting of a test plan (see 1637844467Test plan specific settings)

• Log error if table not found

If a table isnwasn't found in the output of the Web Intelligence report and this setting is switched to true, the variant execution ends with an error instead of a warning. This setting is currently relevant for Web Intelligence.

...

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

• Connection settings
  • URL with port – URL path to HP ALM server together with a port used for standard web browser connection to this server (usually 8080)
  • ALM domain – HP ALM domain where Datavard Validate objects will be replicated
  • ALM project – HP ALM project where Datavard Validate objects will be replicated
• User settings
  • User name Username and password that exists in HP ALM server and is authorized to access ALM domain and the 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 Datavard Validate Test cases will be replicated
  • Test plan path – folder in HP ALM Test Lab area, where all Datavard Validate Test plans will be replicated
• Status mapping
  • Table with all Datavard Validate Test case and Test plan statuses that can be mapped to HP ALM statuses (F4 help supported).

Connection settings, user settings and integration settings are saved as a template with unique template name. Initially HP ALM Integration contains default template 'GLOBAL'. User can save another sets of settings as templates. Template can be user specific, which means it is available only to logged user who created it. Status mapping is independent from templates.

...

• Backend 
  • all of backend settings are also available as test plan specific settings
• Front End
  • User input allowed –  time for user input (in seconds)
  • HTML docs load timeout – time for load of an HTML document (in seconds) – Web Intelligence exclusive setting
  • WEBI table load wait limit – time for load of a table in HTML document (in seconds) – Web Intelligence exclusive setting
  • Technical log – turn on/off technical logs – Web Intelligence exclusive setting

Image RemovedImage Added_{Test Plan Specific Settings}

Image RemovedImage Added
_{Inside Datavard Validate Test Plan Specific Settings - backend settings}

_{Image RemovedImage Added
Front End Test Plan Specific Settings}

...

'Transport settings' button allows to prepare a transport with necessary table content to transport settings of Datavard Validate so they can be automatically reapplied when the system is refreshed. Checkbox The checkbox 'Include test case dependent settings' gives an option to include Test Case dependent settings. Test Case dependent settings contain object IDs which are necessary as an internal number range for distinct identification of Test Cases and Test Variants. It is recommended to include test case dependent settings when system is going to be refreshed and previous Test Cases are going to be imported again to prevent object IDs overwriting. Transport  A transport request is created as a transport of copies.

Image RemovedImage Added

^{Transport settings preparation} 

How to handle transport of test cases and settings:

1. Create a transport of Test Cases which will be imported to the system after refresh. Release the transport.

2. Create a transport of settings. Mark Check the checkbox to include Test Case dependent settings. Release the transport.

3. Refresh the system and install Datavard Validate (KATE) again.

4. Import the transport with settings.

5. Import the transport with Test Cases.

...

INTERFACE FOR BACKEND VARIANT GENERATION

Datavard Validate 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 Datavard Validate API classes available in /DVD/EQS_GEN package. Each of these classes contains one method 'Generate' that generates the appropriate type of variant based on importing parameters supplied. 

Image RemovedImage Added
_{Datavard Validate API for variants generation package}

...

As in Datavard Validate 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. 
Datavard Validate Backend testing provides three BADI Definitions that you can implement by using your own logic to deny an access to restricted data images. The following BADIs are available in package /DVD/EQS:

• /DVD/EQS_BADI_AUTH_INFOPROV – BADI that restricts an access to image data for ListCube, DrillDown and Transformation testing variants based on InfoProvider name.
• /DVD/EQS_BADI_AUTH_QUERY – BADI that restricts an access to image data for Query testing variants based on query technical name.
• /DVD/EQS_BADI_AUTH_TABLE – BADI that restricts an 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. Per As per customer needs, a transport request with default authorization implementation can be delivered togather together with release transports (see (DV-2002) Appendix A - DVD Authorization concept for more information). 

...