Tricentis Tosca

DataMaker connects to Tricentis Tosca so the agent can read your existing test cases, find the gaps in their data coverage, and write new test data straight back into Tosca. There are two connection kinds, because Tosca exposes two very different APIs:

• Tosca Cloud (tosca-cloud): OAuth2 Bearer auth, JSON, organised into spaces. Used for the hosted Tosca, with the model-based-test builder design payload.
• Tosca On-Prem (tosca-onprem): HTTP Basic auth, XML, organised into workspaces, and queried with TQL (Tricentis Query Language) against the Tosca Commander REST service. This is the only Tosca surface that exposes the full test-data write model (test sheets, instances, attributes, execution lists).

The two are not interchangeable. Pick the kind that matches the Tosca you run.

Create a Tosca Cloud connection

Project → Connections → New → Tosca Cloud. Fill in:

• Name: e.g. Tosca Cloud (prod).
• Service URL: the root of your Tosca Cloud tenant.
• Auth: OAuth2. DataMaker stores the credentials encrypted and sends a Bearer token on every request.

Click Verify. DataMaker reaches the tenant’s applications endpoint to confirm the credentials and that the tenant is reachable.

Create a Tosca On-Prem (Tosca Commander) connection

On-prem connections point at the Tosca Commander REST service, not a Tosca Cloud tenant.

Project → Connections → New → Tosca On-Prem. Fill in:

• Name: e.g. Commander (demo).
• Service URL: the Tosca Commander REST base, e.g. http://tosca-host:81/rest/toscacommander.
• Auth: HTTP Basic (username and password). A blank password is allowed (the default Admin user often has none), and DataMaker still builds a valid Basic header for it.

Click Verify. DataMaker lists the server’s workspaces and probes a workspace-scoped endpoint to confirm the credentials are accepted, rather than just that the host answers.

Note

On-prem Tosca is organised into workspaces. A Tosca Commander server can hold several, and test cases differ per workspace, so most on-prem operations take a workspace name. Ask the agent to list them, or see tosca-onprem-list-workspaces.

What you can do

Reading and writing Tosca is agent-driven: describe what you want in chat and the agent uses its Tosca tools against the connection you configured.

Read test cases and analyse data gaps

List the test cases in the Commander (demo) Tosca system, then read the design of “Open Demo Web Shop” and tell me which attribute combinations aren’t covered.

The agent lists the test cases, reads a design (configuration parameters, test step folders, module and attribute references, value ranges), and reasons over which attribute and value-range combinations exist versus which are missing. This data-gap analysis is the input for generating the test data you’re actually short on.

Create a test case (Tosca Cloud)

Take that design, add rows covering the missing country and payment-method combinations, and save it back as a new test case.

On Tosca Cloud the agent submits a modified design payload as a new test case. Structural ids are cleared automatically (Tosca mints fresh ones) and module references are preserved, so the new case slots into the same modules.

Write test data (Tosca On-Prem)

On-prem is where DataMaker writes the real test-data model. The agent:

1. Locates the right parent object with a TQL query (a test sheet belongs under the TestCaseDesign section, an execution list under an execution-lists folder, and so on, so it discovers the parent at runtime rather than guessing ids that vary per server and language).
2. Creates the objects it needs (a TestSheet, then the columns as Attribute objects, then each row as an Instance), setting cell values per column.
3. Optionally assembles an execution list and adds test cases to it.

Each write is bracketed by a checkout and check-in on version-controlled workspaces, so the change is committed once and the object is never left locked.

Note

Classic Tosca Commander does not run tests over REST (a Tosca agent / DEX does). DataMaker assembles the execution list and writes the data; read the verdicts back afterwards by reading the execution entries’ result attributes.

The Tosca MCP tools

The connection powers a dedicated datamaker-tosca MCP server. Its tools are listed in the tool catalogue; in short:

• tosca-list-testcases, tosca-read-testcase-design, tosca-create-testcase (Cloud-style design read/write).
• tosca-onprem-list-workspaces, tosca-onprem-query (TQL), tosca-onprem-create-object, tosca-onprem-add-execution-entry, tosca-onprem-get-object (on-prem object model).

You don’t call these directly in the product; the agent does. They’re also available to external MCP clients (Claude, Cursor, Copilot) once the server is connected, see MCP clients.

Troubleshooting

• An on-prem query times out. Broad TQL traversals (for example =>SUBPARTS:TestCase from the project root) over a large or cold workspace can be slow. Scope the search to a sub-tree by passing a from object id, or query a smaller workspace. Connectivity is fine if tosca-onprem-list-workspaces returns quickly, it’s the traversal that’s heavy.
• Credentials rejected (403). On-prem Tosca returns a 403 both for a failed login and for a workspace that is momentarily locked by another session. If list workspaces works but a workspace operation 403s, try again shortly, the workspace may be in use.
• “No workspaces found”. The URL points at a host that answers but isn’t a Tosca Commander REST endpoint. Check the /rest/toscacommander path.

For connection basics shared across all kinds, see Connections overview.