Skip to content

Getting Started

This guide walks you through the information analytiQa needs to connect to your data sources and start ingesting test data.

How you send us this information

Work with your Qualtiva technical contact. If you don't know who that is, email support@qualtiva.solutions. Credentials and configuration are entered through a short-lived secure credential intake link, never by email or chat. See Providing Configuration & Credentials Securely.


What You'll Need

Account Credentials

For each data source you want to use, we need credentials to connect:

Data Source Credential Type Where to Find It Security
Jira Email + API Token Your Jira account settings We never store your password—only an API token
qTest Base URL + Access Token Your qTest instance API token stored encrypted
Tosca Tosca Server Client ID + Secret (recommended), a Personal Access Token, or a repository username + password Your Tosca Server or Tosca workspace Entered on your own machine; never sent to analytiQa
Tosca Cloud Tenant URL, Token URL + API client ID and secret Your Tosca Cloud tenant (an administrator reads the client ID and secret) Client secret stored encrypted

Configuration Information

For each extractor, you may specify:

  • What to extract: Which projects, test suites, or issue types
  • When to extract: Daily, weekly, or on-demand
  • Date ranges: How far back to look for historical data

Step 1: Gather Your Credentials

For Jira

You need two things:

  1. Your Jira URL: https://your-company.atlassian.net
  2. Your Email: The email address of your Jira account
  3. API Token: A secure token (not your password)

How to get an API Token:

  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token
  3. Give it a name (e.g., "analytiQa Data Extractor")
  4. Copy the token — you'll only see it once
  5. Enter it in the Jira section of your secure credential intake link (we store it encrypted)

For qTest

You need:

  1. Base URL: https://your-instance.qtestnet.com/
  2. Access Token: A bearer token for API access

How to get an Access Token:

  1. Log in to qTest and select the Download qTest Resources icon in the toolbar
  2. Expand the API & SDK section
  3. Copy the Bearer Token with the copy icon (tokens are masked by default)
  4. Enter it in the qTest section of your secure credential intake link

See Tricentis's guide: Download qTest Resources.

For Tosca

The Tosca extractor runs on a Windows machine in your network, so you install it rather than send us credentials. You need:

  1. A Windows machine with Tosca Commander installed, and Administrator rights on it
  2. Workspace File Path: The location of your Tosca workspace (.tws file) on that machine
    Example: C:\Tosca_Projects\Tosca_Workspaces\MyProject\MyProject.tws
  3. A Tosca login, one of:
    • Tosca Server Client ID + Client Secret (recommended, for workspaces created with the Tosca Server connection type). The Client ID is not a user's email address.
    • Tosca Server Personal Access Token (for workspaces created with the Tosca Server connection type)
    • Repository username + password (for a workspace with a direct repository connection, without Tosca Server)
  4. The extractor package, downloaded from the Tosca section of your environment's checklist page (https://<your-instance>.analytiqa.cloud/credentials/checklist)

Optionally: - Search window: How far back each run looks (the default configuration uses 72 hours)

See Tosca Extractor Setup for the full install, including the Fluentd log shipper.

For Tosca Cloud

You need:

  1. Tenant URL: https://yourcompany.my.tricentis.com
  2. Token URL: open https://<tenant>/_identity/apiDocs/swagger, click Authorize and copy the Token URL
  3. API client ID and secret of the Tricentis_Cloud_API application. Only a Tosca Cloud administrator can read them
  4. Enter them in the Tosca Cloud section of your secure credential intake link

See Tosca Cloud Extractor Setup for the step-by-step instructions.


Step 2: Choose What to Extract

Jira

You can configure:

  • Filters: One or more named JQL queries or saved Jira filters that select the issues to extract, for example one filter per team or board
    Example: project = WEB AND "Squad" = Falcon
  • Custom fields: Team, Sprint and Fix Version by default, plus any others you name
  • History: How far back the first extraction should go
  • Polling Interval: Every 15 minutes (default), or a custom interval

See Jira Extractor Setup for filter examples and rules of thumb.

qTest

You can configure:

  • Projects: Which projects to include (by name pattern, e.g., Regression.*)
  • Date Range: Start and end dates for historical data
  • Polling Interval: Hourly (default), or a custom interval

Tosca

You can configure:

  • Search Pattern: What objects to extract (test cases, execution logs, etc.)
  • Search Range: How far back to look
  • Schedule: Agreed with your analytiQa contact during onboarding (Tosca extraction runs against your workspace, so timing is set up with you directly)

Tosca Cloud

You can configure:

  • Workspaces: All workspaces (default), or only some
  • History: How far back the first extraction should go
  • Polling Interval: Every 15 minutes (default), or a custom interval

Step 3: What Happens Next

Once you've submitted credentials and configuration through your secure link and we've applied them:

  1. First run: analytiQa connects and extracts your historical data (may take 5–60 minutes depending on volume)
  2. Ongoing updates: On your configured schedule, new data is automatically ingested
  3. Dashboard access: Your data appears in the analytiQa dashboard under Jira Issues, qTest, Tosca or Tosca Cloud views
  4. Monitoring: You can check ingestion status in the platform

Need Help?

  • Lost your API token? Create a new one — old tokens can be revoked
  • Workspace file not found? Ensure the path is correct on the machine running the Tosca extractor
  • Permission denied? Your Jira/qTest account may need additional permissions — see Support & Troubleshooting

Next step: Configure your first data source!