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.

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 Workspace File + Repository User Your Tosca environment Credentials encrypted; workspace accessed via your network

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. Provide this token to analytiQa (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 your qTest instance
  2. Click your profile icon (top-right) → API & SDK
  3. Click Generate Token
  4. Copy the token and provide to analytiQa

For Tosca

You need:

  1. Workspace File Path: The location of your Tosca workspace (.tws file). Tosca Commander is Windows-only, so this is always a Windows-style path
    Example: C:\MyWorkspaces\MyProject.tws or \\shared-server\tosca\workspace.tws
  2. Tosca Repository Username: Your Tosca user account
  3. Tosca Repository Password: Your Tosca account password

Optionally: - Server Login: If your workspace is on a Tosca Server (not local) - Start Date: How far back to look (default: 24 hours)

Step 2: Choose What to Extract

Jira

You can configure:

  • JQL Queries: Which issues to extract
    Example: created >= -5d OR updated >= -5d (Issues created or updated in the last 5 days)
  • Include Details: Comments, worklogs, links, watchers, custom fields
  • Polling Interval: Every 15 minutes (default), or a custom interval

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)

Step 3: What Happens Next

Once you provide credentials and configuration:

  1. First run: analytiQa connects and extracts your historical data (may take 5–60 minutes depending on volume)
  2. Daily updates: On your configured schedule, new data is automatically ingested
  3. Dashboard access: Your data appears in the analytiQa dashboard under Jira Issues, qTest, or Tosca 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 accessible from analytiQa servers (contact support for network paths)
  • Permission denied? Your Jira/qTest account may need additional permissions — see Support & Troubleshooting

Next step: Configure your first data source!