Starting with version 7.0, suxxesso Tool Suite checks whether the minimum requirements for the CodeMeter version are met (see “Technical Customer Documentation” in the Customer Area).

It is also essential to ensure that the server and client are running the same CodeMeter version.

In the SAP Logon, under Accessibility & Scripting / Scripting, disable the following options:

If error TS-10026 (<name> not found on process <process ID>) occurs during the recording and execution of test cases, we recommend to start the SAP logon via the suxxesso Tool Suite. This suxxesso Tool Suite Auto-Start will set all necessary environment variables correctly.

Start SAP-Logon from the suxxesso Tool Suite:

• Open “Settings / Test Case Execution”
• Select option “SAP Logon”
• Enter the file path for saplogon.exe
• Enter optional arguments

Only when automating SAP GUI transactions, screenshots are automatically inserted as soon as a server communication takes place.

For web application automation, screenshots must be inserted manually.

The display language that you have selected in the suxxesso Tool Suite under Settings / General must match the language of the word template. This is the only way to ensure that the test case steps are interpreted correctly and inserted correctly in the documentation.

The two templates DescriptionTemplate.docx and DescriptionTemplate.en.docx are delivered.
Pay attention to this also when you create individual templates.

Web applications work asynchronously, i.e. there is no defined point in time at which the entire screen is built up. As a result, it is possible that the suxxesso Tool Suite is too fast when replaying a test case and accesses a field that is not yet available.

The suxxesso Tool Suite tries as best as possible to take this asynchronous processing into account, but it is not always possible. In those few cases that cannot be caught, add a manual wait step to delay the execution.

If there are neither queries nor constant iterations in a test case, the initial values from the test case are always used for the test case execution. The mapping of any parameters is not taken into account.

The easiest way to get around this limitation is to add a constant iteration:

1. Define the desired parameter as a test case parameter.
2. Assign this parameter in the variable mapping to the relevant variable in the test case (defined in the suxxesso Test Pilot).
3. Add ${parameter name} as a constant iteration.

In the suxxesso Test Cockpit, a value can now be assigned to this test case parameter, which is then taken into account in the test case execution.

A 2nd possibility is the addition of a pseudo-query:

1. Define the desired parameter as a test case parameter.
2. Assign this parameter in the variable mapping to the relevant variable in the test case (defined in the suxxesso Test Pilot).
3. Add a pseudo-query (e.g. client query with query of the day date).

As a prerequisite for this variant, the DataManager role must be specified in the settings for the relevant connection.

To successfully supply test cases with current test data, the following preparations and settings are necessary in the system and in the Data Manager.

• The function module for the RFC call must be imported into the system.
• The relevant system must be added as a connection in the settings.
• The following information about the system (= properties in the SAP logon) is required for Data Manager access – this also applies to test cases that access the Fiori Launchpad via a URL:
  • Application Server (Host)
  • Instance number
  • System ID
• The DataManager role of the relevant connection must be filled in with a SAP user who has all the necessary authorizations.

The Data Manager generally accesses the database in a read-only manner with its queries and thus does not change the database.

However, it is possible to deliberately call SAP functions in the query that change the database.