Skip to content

Tosca Extractor Setup — Customer Guide

Configure analytiQa to automatically extract test automation data from your Tricentis Tosca workspace.

Prerequisites

Step 1: Provide Your Workspace Information

Tell us how to access your Tosca workspace:

Option 1: Local Workspace File

If your workspace is stored on a local or network path (recommended):

  1. Workspace Path: Full path to your .tws file (Tosca Commander is Windows-only, so this is always a Windows-style path)
    Examples:
  2. Local: C:\Workspaces\MyProject.tws

  3. Network share: \\shared-server\tosca\workspace.tws

  4. Repository User: Your Tosca Repository username

  5. Repository Password: Your Tosca Repository password

Option 2: Tosca Server

If your workspace is on a Tosca Server (shared/remote):

  1. Server Login: Enable
  2. Server URL: The Tosca Server URL
  3. Server User: Your Tosca Server account
  4. Server Password: Your Tosca Server password
  5. Workspace Name: Name or path within the Tosca Server

Step 2: Confirm Access Permissions

Your Tosca user account needs:

  • ✓ Read access to the workspace
  • ✓ Read access to test cases, test steps, execution logs
  • ✓ Read access to any managed objects your team uses

If you get "Permission Denied" errors, ask your Tosca admin to grant these permissions.

Step 3: Choose What to Extract

Extraction Type

Select what types of Tosca objects to extract:

Option Extracts Use Case
Test Cases (default) Test case definitions, test steps, parameters Most common — understand test coverage
Test Cases + Execution Logs Test cases + execution results, pass/fail, duration Best option — see automation results
All Objects Test cases, requirements, custom objects, metadata Advanced analysis

Historical Data

Set how far back to look:

  • Last 24 hours (default): Latest test executions
  • Custom: Specify start date and hours to look back (e.g., "Last 30 days", "2025-01-01 onwards")

Step 4: Choose Your Schedule

Unlike Jira and qTest, Tosca extraction runs against your workspace directly, so timing is agreed with your analytiQa contact during onboarding rather than set to a fixed default. Typical options:

  • Recurring schedule: e.g. after your nightly test runs complete
  • Manual: Trigger on-demand

Tip

If you run Tosca automation from a CI/CD pipeline, you can also push execution results straight to analytiQa as each run completes — see Publishing Test Results Directly.

Step 5: Review Your Configuration

Before confirming, check:

  • ✓ Workspace path is correct and accessible
  • ✓ Tosca Repository credentials are valid
  • ✓ Your user account has read permissions
  • ✓ Extraction type matches your needs
  • ✓ Historical date range is set correctly
  • ✓ Schedule works for your team

What Happens Next

  1. Connection test (< 1 minute): analytiQa verifies access to your workspace
  2. First extraction (5–60 minutes depending on size): All selected data is fetched
  3. Daily updates (every day at scheduled time): New and modified objects are pulled
  4. Dashboard ready: Log in to analytiQa dashboard → Tosca tab

What Gets Extracted

From your Tosca workspace, analytiQa captures:

  • Test Cases: Name, description, test steps, parameters, custom fields
  • Test Steps: Step description, data, expected results, script details
  • Execution Results: Pass/fail/skip status, execution date, duration, error messages
  • Test Data: Linked data pools, parameters, configurations
  • Managed Objects: Reusable UI elements, API endpoints, data sources
  • Organization: Folder structure, test suites, project hierarchy
  • Metadata: Creation date, modification date, owners, comments

Example Dashboards

Once data is ingested, see Common Queries & Reports for pre-built examples:

  • Total test cases and test steps breakdown
  • Execution success rate over time
  • Test cases by priority and type
  • Automation coverage trends

Network & Access FAQ

Q: My workspace is on a network share. Will analytiQa have access?
A: If the network path is accessible to analytiQa servers (e.g., on your private network), yes. Contact analytiQa support if you need a specific firewall rule or network path configuration.

Q: Can I use Tosca Server instead of a local workspace?
A: Yes! Enable "Server Login" and provide your Tosca Server URL and credentials. See Option 2: Tosca Server above.

Q: What if my workspace is too large and extraction times out?
A: Tell analytiQa to extract a subset — specify a date range, extraction type, or specific folders/test suites to reduce volume.

Troubleshooting

Issue Solution
"Workspace not found" Check the workspace file path. Ensure it's accessible and ends in .tws
"Permission denied" Verify your Repository user has read access. Ask your Tosca admin.
"Connection timeout" Workspace may be unavailable. If on network share, check network connectivity.
"Empty results" Your historical date range may not include data. Try extending backward or selecting all objects.
"Extraction takes too long" Large workspaces take time (1–60 min). You can check progress in analytiQa dashboard.

More help? See Support & Troubleshooting.

Next Steps