Tricentis Tosca

Choose the Tosca system in Connections, then select the deployment variant and credentials appropriate to it:

• Tosca Cloud uses OAuth2 client credentials.
• Tosca On-Prem uses the configured server and Basic authentication, with a workspace selected for relevant operations.

Test a read before authoring or triggering changes. DataMaker permissions and the Tosca account's permissions both apply.

Read test designs

Ask the agent to list test cases and inspect one test-case design. Use its configuration parameters, steps and value ranges to identify the data the test needs. Confirm the exact test case and environment before creating a template or scenario from it.

Cloud tools can inspect playlists, playlist runs, test-case runs and run steps. These provide test execution evidence; reading them does not start a new execution.

Build native Cloud tests

DataMaker can search and read native Cloud modules, inspect standard-module packages, and create new custom modules. Name the target workspace explicitly, for example: “In SAP Demo, find the browser login module and show its controls.”

For a migration, inspect compatible modules first. DataMaker can author new modules from known control identification properties and use the returned module and attribute references to create native test cases. Keep browser and desktop SAP controls separate, and preserve frame context, input values, selected dropdown entries, assertions and waits.

Module creation adds a new artifact; it does not modify existing modules. If Tosca times out after a creation request, check the named workspace for the module before retrying. A created module or test case is not execution evidence: run and inspect the native test before treating the migration as verified.

On-premises authoring

The on-premises tool surface can list workspaces, query objects with TQL, create supported objects, add execution entries, inspect objects and check in changes. Read the announced tool schema and verify the parent object before making a change.

Checking in or adding an execution entry is a separate action from reading a design. Review the intended workspace and scope rather than inferring authorization from a successful connection test.

Share reusable setup

The Hub can provide starter assets where the catalogue is enabled. Imported scenarios remain drafts and skills disabled until reviewed. Configure the actual Tosca connection and verify the imported workflow against a small test case.