Integrate with Curiosity Quality Modeller

TestRail integrates with Curiosity Software to enable a seamless flow between model-based test generation and test management. This integration allows teams to automatically export test cases designed in Curiosity’s Quality Modeller directly into TestRail, keeping test artifacts synchronized and up to date.

Untitled.png

 

To see a real-world example of this integration in action, check out the webinar on aligning test data and automation, where teams demonstrate how Curiosity and TestRail work together to accelerate test delivery while maintaining full traceability.

This article describes how to configure the integration and use it to push test cases from Curiosity into TestRail using the TestRail API.

Requirements

To integrate Curiosity Software with TestRail, you’ll need:

  • A TestRail instance (Cloud or Server).
  • An active Curiosity Software account with access to Quality Modeller.
  • API access enabled in your TestRail instance.
  • A valid TestRail API Key (configured under My Settings > API Keys).
  • Project access and permission to create/edit test cases in TestRail.

 


How It Works

The Curiosity Software integration with TestRail uses a dedicated connector inside the Curiosity platform to communicate with TestRail’s API. Once configured, users can map fields between platforms and export model-generated test cases directly into TestRail.

Key capabilities:

  • Export auto-generated test cases to TestRail.
  • Map fields and values between platforms.
  • Create new suites or update existing ones.
  • Authenticate using secure API tokens.

 


Configuration Steps

1. Create an API Key in TestRail

  1. Log in to your TestRail instance.
  2. Navigate to My Settings > API Keys.
  3. Click Add Key, provide a label, and click Add Key.
  4. Copy the generated API key for use in Curiosity.

💡 Note: API keys are personal and should be kept secure. You can revoke them at any time from the same settings page.

 

2. Set Up the TestRail Connector in Curiosity

Screenshot 2025-07-29 160401.png
  1. In Curiosity’s dashboard, go to Management > Connectors.
  2. Click Add Connector and select TestRail as the connector type.
  3. Enter the following details:
    • Name: A custom name for the connector.
    • Base URL: Your TestRail instance URL (e.g., https://yourcompany.testrail.io).
    • Username: Your TestRail account email.
    • API Key: Paste the API Key you generated earlier.
    • Project: Choose the TestRail project to connect.
    • Suite / Folder Name: Select where to place the test cases.
  4. Save the connector and test the connection.

You can also share the connector with your team to allow reusability across workspaces.

 

3. Map Fields (Optional)

Before exporting, map test metadata from Curiosity to TestRail fields. You can:

  • Use static values or model-based variables.
  • Map to text, dropdowns, or date fields.
  • Ensure required fields in TestRail are filled correctly.

This step ensures that exported tests meet your project structure and standards.

 

4. Export Test Cases to TestRail

  1. Open your test model in the Quality Modeller.
  2. Click the Export button and choose Test Cases.
  3. Select the previously configured TestRail connector.
  4. Choose your export options:
    • Create a new folder or update an existing one.
    • Filter which test cases to include.
  5. Confirm the export.

Curiosity will send the test cases to TestRail using the API, creating structured test cases in the designated suite or section.

 

Example Export Workflow

Step Tool Action
Design test model Curiosity Modeller Build logical test scenarios visually
Configure TestRail connector Curiosity Modeller Link to your TestRail instance via API key
Map fields (optional) Curiosity Modeller Match Curiosity fields to TestRail test case fields
Export test cases Curiosity Modeller Push tests to TestRail using the Export function
Review & run tests TestRail Test cases are now available for planning & execution

 

Troubleshooting

  • Authentication failure: Make sure your TestRail API key is valid and associated with the correct user.
  • Missing project or suite: Double-check your project name and ensure it exists in TestRail.
  • Invalid field mapping: Ensure field names and values match what’s configured in TestRail, especially for custom fields.

❗ TestRail permissions must allow the user to create or update test cases. See more here about how to manage TestRail roles and permissions.

 

Learn More

 

Was this article helpful?
3 out of 6 found this helpful