qTest

​

Introduction

• Test Case Management: Create, organize, and manage test cases in a centralized repository
• Test Execution Tracking: Monitor test runs and track execution status in real-time
• Requirements Traceability: Link test cases to requirements and defects for complete audit trails
• Reporting & Analytics: Generate comprehensive reports on test coverage and quality metrics
• Agile Integration: Support for iterative testing and CI/CD pipeline integration

​

Account Setup and Configuration in qTest

1. Visit Tricentis Website: Open your web browser and navigate to the official Tricentis qTest website: https://www.tricentis.com/.
2. Sign Up for qTest: Navigate to “Trials & demos” and click on “Try qTest free” to start a free 14-day trial.
3. Create an Account: Follow the prompts to create your qTest account. Complete the registration form with your business details.
4. Create Workspace: During the signup process, you will be asked to create your qTest web address and account credentials.
5. Verify Email: Check your inbox for a verification email from qTest. Click the verification link in the email to activate your account.
6. Access qTest: Once your email is verified, log in to qTest using your newly created credentials and access your qTest instance.

​

Generate an API Token

1. Log in to qTest: Access your qTest workspace by navigating to your qTest URL (e.g., your-subdomain.qtestnet.com) and logging in with your credentials.
2. Navigate to API Settings: Go to “Manager” → “API & SDK” from the main navigation menu.
3. Copy Your API Token: Find and copy your Bearer Token from the API settings page. This is your API token that will be used for authentication.
4. Securely Store Your API Token: Immediately copy the generated API token. Store it securely in a password manager or, preferably, ELITEA’s built-in Secrets feature for enhanced security within ELITEA. You will need this API token to configure the qTest toolkit in ELITEA.

​

System Integration with ELITEA

​

Step 1: Create qTest Credentials

1. Navigate to Credentials Menu: Open the sidebar and select Credentials.
2. Create New Credential: Click the + Create button.
3. Select qTest: Choose qTest as the credential type.
4. Configure Credential Details:
   • Display Name: Enter a descriptive name (e.g., “qTest - Test Management”)
   • Base URL: Enter your qTest instance URL (e.g., https://your-subdomain.qtestnet.com)
   • qTest API Token: Enter your Bearer token from qTest
5. Test Connection: Click Test Connection to verify that your credentials are valid and ELITEA can successfully connect to qTest
6. Save Credential: Click Save to create the credential. After saving, your qTest credential will be added to the credentials dashboard and will be ready to use in toolkit configurations. You can view, edit, or delete it from the Credentials menu at any time.

​

Step 2: Create qTest Toolkit

1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
2. Create New Toolkit: Click the + Create button.
3. Select qTest: Choose qTest from the list of available toolkit types.
4. Configure Basic Information:
   • Toolkit Name: Enter a descriptive name for your toolkit (required). Example: “qTest - Project Testing”
   • Description: Provide an optional description to explain the toolkit’s purpose. Example: “Toolkit for managing test cases and test execution in qTest for Project Alpha”
5. Configure Credentials:
   • In the Configuration section, select your previously created qTest credential from the Credentials dropdown
6. Configure Advanced Options:
   • PgVector Configuration: Select a PgVector connection for vector database integration
   • Embedding Model: Select an embedding model for text processing and semantic search capabilities
7. Configure qTest Settings:
   • qTest Project ID: Enter the numerical Project ID of your qTest project
   • No Of Tests Shown In DQL Search: [Required Field] Set the maximum number of test cases to retrieve in DQL queries (recommended: 100-200) !!! warning “Required Field” The “No Of Tests Shown In DQL Search” field is mandatory and must be filled in. This setting controls the maximum number of test cases returned from DQL queries to prevent context overflow and improve performance.
8. Enable Desired Tools: In the “Tools” section, select the checkboxes next to the specific qTest tools you want to enable. Enable only the tools your agents will actually use to follow the principle of least privilege
   • Make Tools Available by MCP - (optional checkbox) Enable this option to make the selected tools accessible through the external MCP clients to use the toolkit’s capabilities
9. Save Toolkit: Click Save to create the toolkit

​

DQL Search Limit Configuration: “No Of Tests Shown In DQL Search”

• Context Management: Prevents LLM context limits from being exceeded when retrieving large datasets
• Performance Optimization: Smaller result sets improve query response times and Agent processing speed
• Resource Control: Manages the amount of data transferred and processed during DQL operations
• Image Handling: Especially important when “Extract Images” is enabled, as images significantly increase context size

​

Available Tools:

​

Testing Toolkit Tools

1. Select LLM Model: Choose a Large Language Model from the model dropdown in the Test Settings panel
2. Configure Model Settings: Adjust model parameters like Creativity, Max Completion Tokens, and other settings as needed
3. Select a Tool: Choose the specific qTest tool you want to test from the available tools
4. Provide Input: Enter any required parameters or test queries for the selected tool
5. Run the Test: Execute the tool and wait for the response
6. Review the Response: Analyze the output to verify the tool is working correctly and returning expected results

​

Step 3: Add qTest Toolkit to Your Workflows

​

In Agents:

1. Navigate to Agents: Open the sidebar and select Agents.
2. Create or Edit Agent: Either create a new agent or select an existing agent to edit.
3. Add qTest Toolkit:
   • In the “TOOLKITS” section of the agent configuration, click the “+Toolkit” icon
   • Select your configured qTest toolkit from the dropdown list
   • The toolkit will be added to your agent with the previously configured tools enabled

​

In Pipelines:

1. Navigate to Pipelines: Open the sidebar and select Pipelines.
2. Create or Edit Pipeline: Either create a new pipeline or select an existing pipeline to edit.
3. Add qTest Toolkit:
   • In the “TOOLKITS” section of the pipeline configuration, click the “+Toolkit” icon
   • Select your configured qTest toolkit from the dropdown list
   • The toolkit will be added to your pipeline with the previously configured tools enabled

​

In Chat:

1. Navigate to Chat: Open the sidebar and select Chat.
2. Start New Conversation: Click +Create or open an existing conversation.
3. Add Toolkit to Conversation:
   • In the chat Participants section, look for the Toolkits element
   • Click the “Add Tools” Icon to open the tools selection dropdown
   • Select your configured qTest toolkit from the dropdown list
   • The toolkit will be added to your conversation with all previously configured tools enabled
4. Use Toolkit in Chat: You can now directly interact with your qTest projects and test cases by asking questions or requesting actions that will trigger the qTest toolkit tools.

​

Instructions and Prompts for Using the qTest Toolkit

​

Instruction Creation for Agents

• Direct and Action-Oriented: Employ strong action verbs and clear commands to initiate actions. For example, “Use the ‘search_by_dql’ tool…”, “Create a test case with…”, “Find test case by ID…”.
• Parameter-Centric: Clearly enumerate each parameter required by the tool. For each parameter, specify:
  • Its name (exactly as expected by the tool)
  • The format or type of value expected
  • How the Agent should obtain the value – whether from user input, derived from previous steps in the conversation, retrieved from an external source, or a predefined static value
• Contextually Rich: Provide sufficient context so the Agent understands the overarching objective and the specific scenario in which each qTest tool should be applied within the broader workflow. Explain the desired outcome or goal for each tool invocation.
• Step-by-Step Structure: Organize instructions into a numbered or bulleted list of steps for complex workflows. This helps the Agent follow a logical sequence of actions.
• Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality.

1. State the Goal: Begin by clearly stating the objective you want to achieve with this step.
2. Specify the Tool: Clearly indicate the specific qTest tool to be used for this step.
3. Define Parameters: Provide a detailed list of all parameters required by the selected tool.
4. Describe Expected Outcome: Briefly describe the expected result or outcome after the tool is successfully executed.
5. Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality.

1. Goal: Search for qTest test cases using DQL to find specific test cases based on user criteria.
2. Tool: Use the "search_by_dql" tool.
3. Parameters:
    - DQL Query: "Ask the user for search criteria or use predefined DQL like 'Module = \"MD-1 MD-6 Company page\" AND Status = \"Ready for Testing\"'"
4. Outcome: The Agent will provide a list of test cases matching the DQL criteria.
5. Conversation Starters: 'Show me test cases ready for testing', 'Find all test cases in Partners module', 'Search for automated test cases'

1. Goal: Create a new test case in qTest based on user requirements.
2. Tool: Use the "create_test_cases" tool.
3. Parameters:
    - Project ID: "Use the configured Project ID from toolkit settings"
    - Folder Path: "Ask user for target folder or use 'MD-3 MD-11 Partners pages' format"
    - Test Case Data: "Collect test case name, description, steps, and expected results from user and format as JSON"
4. Outcome: The Agent will create a new test case and provide the test case ID and details.
5. Conversation Starters: 'Create a new test case', 'Add a test for login functionality', 'Generate test case for feature X'

​

Chat Usage Examples by Tool Category

User: "Find all test cases in the 'Partners pages' module that are ready for testing."

Agent Response: [Agent uses search_by_dql tool]

🔍 **DQL Search Results**:

**📋 Found 5 test cases ready for testing**:

1. **TC-101** - "Verify partner login functionality"
   - **Status**: Ready for Testing
   - **Module**: MD-3 MD-11 Partners pages
   - **Priority**: High
   - **URL**: https://yourcompany.qtestnet.com/p/12345/portal/project#id=12345&object=0&tab=testcase&id=101

2. **TC-102** - "Test partner profile update"
   - **Status**: Ready for Testing
   - **Module**: MD-3 MD-11 Partners pages
   - **Priority**: Medium
   - **URL**: https://yourcompany.qtestnet.com/p/12345/portal/project#id=12345&object=0&tab=testcase&id=102

Would you like me to get more details about any specific test case?

User: "Create a new test case for verifying the password reset functionality."

Agent Response: [Agent uses create_test_cases tool]

✅ **Test Case Created Successfully!**

**📝 New Test Case Details**:
- **Test Case ID**: TC-456
- **Name**: "Verify password reset functionality"
- **Module**: MD-1 MD-6 Company page
- **Status**: Draft
- **URL**: https://yourcompany.qtestnet.com/p/12345/portal/project#id=12345&object=0&tab=testcase&id=456

**Test Steps**:
1. Navigate to login page
2. Click "Forgot Password" link
3. Enter valid email address
4. Click "Reset Password" button
5. Check email for reset link
6. Click reset link and enter new password
7. Submit new password

**Expected Result**: User successfully resets password and can log in with new credentials.

The test case is now ready for review and execution!

User: "Link test cases TC-101 and TC-102 to Jira requirement PROJ-789."

Agent Response: [Agent uses link_tests_to_jira_requirement tool]

🔗 **Test Cases Linked Successfully!**

**Traceability Created**:
- **qTest Test Cases**: TC-101, TC-102
- **Jira Requirement**: PROJ-789
- **Link Type**: Tests requirement

**Linked Test Cases**:
1. **TC-101** - "Verify partner login functionality"
2. **TC-102** - "Test partner profile update"

Both test cases are now linked to the Jira requirement, ensuring full traceability between requirements and test coverage.

User: "Show me all defects found during test run TR-550."

Agent Response: [Agent uses find_defects_by_test_run_id tool]

🐛 **Defects Found in Test Run TR-550**:

**📋 Found 3 defects**:

1. **DEF-201** - "Login button misaligned on mobile"
   - **Severity**: Medium
   - **Status**: Open
   - **Detected**: 2026-01-20
   - **URL**: https://yourcompany.qtestnet.com/p/12345/portal/project#id=12345&object=3&id=201

2. **DEF-202** - "Password validation error message unclear"
   - **Severity**: Low
   - **Status**: In Progress
   - **Detected**: 2026-01-20
   - **URL**: https://yourcompany.qtestnet.com/p/12345/portal/project#id=12345&object=3&id=202

3. **DEF-203** - "Session timeout causes data loss"
   - **Severity**: Critical
   - **Status**: Open
   - **Detected**: 2026-01-21
   - **URL**: https://yourcompany.qtestnet.com/p/12345/portal/project#id=12345&object=3&id=203

Would you like more details about any specific defect?

User: "Find all test cases related to authentication using semantic search."

Agent Response: [Agent uses search_index tool]

🔎 **Semantic Search Results**:

**📋 Found 8 test cases related to authentication**:

1. **TC-301** - "Verify user login with valid credentials" (Relevance: 95%)
2. **TC-302** - "Test SSO authentication flow" (Relevance: 92%)
3. **TC-303** - "Validate two-factor authentication" (Relevance: 90%)
4. **TC-304** - "Check password complexity requirements" (Relevance: 87%)
5. **TC-305** - "Test account lockout after failed attempts" (Relevance: 85%)

These results are ranked by semantic similarity to your search query. Would you like to see the full details of any test case?

​

Best Practices and Use Cases for qTest Integration

Use the 'find_test_case_by_id' tool to retrieve the test case with ID 'TC-12345'. 
Display the 'Name', 'Description', 'Steps', and 'Expected Result' fields to the tester.

Use the 'create_test_cases' tool to create new test cases in qTest Project 'Project Alpha' 
and folder 'MD-3 MD-11 New Features' based on the following data extracted from the new user story: 
[{
  "Name": "Test User Story [User Story ID] - Scenario 1", 
  "Description": "Test scenario 1 for user story [User Story ID]"
}]

Use the 'update_test_case' tool to update test case with ID 'TC-56789'. 
Update the 'Steps' field with the following new steps: 
'1. Open application
2. Navigate to updated UI element
3. Verify new functionality' 
and set the 'Status' field to 'Draft' for review.

Use the 'search_by_dql' tool to search for test cases in qTest using the DQL query: 
'Project = 'Project Alpha' AND Status IN ('Passed', 'Failed')'. 
Generate a report summarizing the number of passed and failed test cases and calculate the test pass rate.

​

Troubleshooting

DQL Query Syntax and Module Issues

Problem: DQL queries fail or return unexpected results.Troubleshooting Steps:

1. Use Full Module Names: Always use complete module paths (e.g., 'MD-1 MD-6 Company page' not just 'Company page')
2. Get Modules First: Use the “Get Modules” tool to retrieve exact module names for your queries
3. Verify DQL Syntax: Ensure proper DQL syntax following qTest documentation standards

​

Support Contact

​

FAQ