Tosca Test Repository Integration

Architecture

LiveCompare connects to the Tosca server using a REST API. The Tosca workspace connects to a common repository.

Tosca Test Repository integration architecture.

Requirements

LiveCompare requires the following in order to connect to a Tosca Test Repository.

  • The URL of a Tosca instance.
  • A Tosca account name and password.
  • A Tosca workspace name.

Issues

The following may cause connection problems when using Tosca integration.

Common issues:

  • Bad account credentials.
  • No dedicated workspace.

Rare issues:

  • LiveCompare cannot access the Tosca Server.
  • The common repository uses Windows authentication.

Please see this Knowledge Base article for troubleshooting tips.

Searching Tosca Test Repositories

The Search Test Repository action searches Tosca Test Repositories to find matching test assets using a two-phase approach.

Phase 1 - Search Modules (ignores Search Paths)

  • Find all Classic, SapEngine and APIEngine modules that match the supplied set of tokens.
    • Each engine has a properly that is searched:
      • Classic: Systeminfo.Transaction.
      • SapEngine: Transaction.
      • APIEngine: Resource.
  • Find all associated test cases (not templates).

Phase 2 - Test Cases (Uses SearchPaths)

  • Find all test cases within the specified SearchPaths that match the supplied set of tokens.
    • Test Step Blocks and Enabled Test Steps are searched.

Due to the Phase 1 search, the results may contain test cases that are outside the specified search paths. This only applies to searching a live Test Repository. When searching a Test Repository cache, LiveCompare always limits the results to test cases within the supplied search paths.

Tosca Data Analysis

Changes to data are captured in SAP table keys (TABK( This provides an efficient way to propagate table content changes between systems without having to copy the entire table. A table key identifies the key field values of affected rows and includes the changes to non-key fields.

LiveCompare processes TABKs to identify the key field values of changed data records. For example, if the discount of a sales order type is changed, LiveCompare will identify the affected sales order type (which is a key field).

In the Smart Impact App’s results, LiveCompare filters the test hits to highlight the ones that use data affected by a particular change.

  • For each test hit, LiveCompare compares the test step values with the key field values.
  • If matched, the test is considered to “HAVE_DATA” making it a relevant test to use to validate the data change.

Notes

LiveCompare doesn’t consider the type of data. For example, ‘RO’ is just a key field value that is matched against test step values. The fact that this represents a sales order type is not considered. This level of type information is not captured in test cases.

Records may have one to many key fields. LiveCompare counts matches if at least 1 key field value is matched with a test step value.

Test Repository Integrations