# Tricentis qTest AI employee Viktor works in Tricentis qTest for you. Ask in Slack or Microsoft Teams. Viktor is an AI employee that connects to Tricentis qTest and helps you build, test, and deploy code through CI/CD pipelines, running 12 Tricentis qTest actions for you like Get Defect, List Defects, and List Modules. Ask in plain English from your workspace; Viktor does the work in Tricentis qTest and reports back. Viktor connects in one click via OAuth. - Tool: Tricentis qTest - Category: Analytics - Connection: One-click OAuth - Actions available: 12 - Currently available in: Slack, Microsoft Teams, and Discord - Page: https://viktor.com/integrations/tricentis-qtest ## What can your AI employee do in Tricentis qTest? Viktor connects to your Tricentis qTest account and completes work in it. He doesn't just answer questions about Tricentis qTest, he takes the actions on your behalf and delivers the finished result to your workspace. Unlike workflow builders such as Zapier or Make, there is nothing to configure - no triggers to map, no workflows to maintain. You describe the outcome in plain English, and Viktor picks the right Tricentis qTest actions, chains them with the other 9,800+ tools he connects to, and asks for approval before anything sensitive runs. ### About Tricentis qTest Scalable test management, operations, and analytics to centralize testing and orchestrate quality at speed, with visibility throughout the software development lifecycle. ### How a run works 1. **You ask in your workspace** - Describe what you need in plain English 2. **Viktor picks the actions** - Selects from 12 Tricentis qTest actions, chains them together 3. **Runs in Tricentis qTest** - Helps you build, test, and deploy code through CI/CD pipelines - your real data. 4. **Reports back** - Delivers the finished result to your workspace ## Use Tricentis qTest from Slack and Microsoft Teams Message Viktor in a Slack channel, a Microsoft Teams chat or a direct message. He opens Tricentis qTest, does the work and posts the result in the same thread, so nobody has to switch tabs. He can also run Tricentis qTest work on a schedule, like a weekly Tricentis qTest summary posted to your team's channel. Anything sensitive waits for your approval before it runs. ## Security and permissions - One-click OAuth - Viktor never sees your password, and you can revoke access at any time. - Review-first approvals: sensitive Tricentis qTest actions wait for your sign-off before they run. - Isolated compute per team, encrypted in transit and at rest - and your data is never used to train models. - SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ## What can you ask Viktor to do in Tricentis qTest? - "Check Tricentis qTest for the latest failed build and summarize the likely cause." - "Trigger a deploy in Tricentis qTest for the latest release and report when it's done." - "Watch Tricentis qTest for failed pipelines and post a summary here with the likely cause." - "Summarize what shipped through Tricentis qTest this week for the changelog." ## How does Viktor work with Tricentis qTest? 1. Open Viktor in a supported workspace. 2. Connect Tricentis qTest with one-click OAuth - Viktor handles authentication. 3. Ask in plain English. Viktor runs the Tricentis qTest actions, chains them with your other tools when needed, and reports back. Sensitive actions wait for your approval. ## What can Viktor do in Tricentis qTest? (12 actions) - **Create Requirement** - Create a new requirement under a parent module in a qTest project. Use List Project ID Options for the project ID, List Modules for the parent module ID, and List Requirement Fields to discover field IDs for the Properties parameter. - **Get Defect** - Get full details of a specific defect by ID. Use List Defects to find the defect ID and List Defect Fields to interpret field IDs in the response. - **Get Requirement** - Get full details of a specific requirement by ID. Use List Requirements to find the requirement ID. - **List Defect Fields** - List all available fields for defects in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before submitting or updating defects. Pass fields (e.g. [\"id\", \"label\", \"required\"]) to keep only those attributes per field — some fields' allowedvalues lists are long, so omitting them when you only need the field ID/label keeps the response small. - **List Defects** - List defects in a qTest project updated after a given start time. Use this to find defect IDs to use when getting or updating a specific defect. If the response contains a full page of results, increment the Page parameter and call again for more. Defaults to defects updated in the last 30 days, and includes only the Summary property per defect to keep the response small — projects with long-running defect logs can return large payloads otherwise, since some properties (like Description) may contain lengthy text. Pass fields (e.g. [\"Summary\", \"Status\"]) to include different or additional named properties instead. Use Get Defect for a defect's full property set. - **List Modules** - List all modules in a qTest project, including nested submodules. Use List Project ID Options for the project ID. Use this to find module IDs to use as the Parent ID in Create Requirement. - **List Project ID Options** - List all qTest projects accessible to the connected account. Use this to find the Project ID required by all other actions. - **List Requirement Fields** - List all available fields for requirements in a qTest project, including field IDs, types, and allowed values. Use this to discover field IDs before creating or updating requirements. Pass fields (e.g. [\"id\", \"label\", \"required\"]) to keep only those attributes per field — some fields' allowedvalues lists are long, so omitting them when you only need the field ID/label keeps the response small. - **List Requirements** - List requirements in a qTest project. Use this to find requirement IDs to use when getting or updating a specific requirement. If the response contains a full page of results, increment the Page parameter and call again to retrieve the next page. - **Submit Defect** - Submit a new defect in a qTest project. Use List Project ID Options for the project ID and List Defect Fields to discover field IDs and required fields for the Properties parameter. - **Update Defect** - Update an existing defect in a qTest project. Use List Defects to find the defect ID and List Defect Fields to discover field IDs for the Properties parameter. - **Update Requirement** - Update ONE existing requirement in a qTest project. Use List Requirements to find the requirement ID and List Requirement Fields to discover field IDs for the Properties parameter. Name is required by the API on every update — resupply the requirement's current name (from Get Requirement) if you only want to change Properties. This tool has no bulk/mass-update mode — before calling it repeatedly to apply the same change across many requirements, confirm the full scope (which requirements, what change) with the user first; do not sweep an entire project's requirements on a single broad instruction. If you ask for that confirmation and don't receive an explicit yes, STOP — do not call this tool anyway. Proceeding without an actual confirmation is exactly the behavior this warning exists to prevent, even if the original instruction sounded broad enough to imply it. This warning is about scope (which/how many requirements), not about calling this tool at all — a single, already-specific instruction (a named requirement ID and field change) needs no extra confirmation. ## Viktor uses Tricentis qTest together with - [Slack](https://viktor.com/integrations/slack) - [Gmail](https://viktor.com/integrations/gmail) - [Google Sheets](https://viktor.com/integrations/google-sheets) - [HubSpot](https://viktor.com/integrations/hubspot) - [Notion](https://viktor.com/integrations/notion) - [Salesforce](https://viktor.com/integrations/salesforce) ## More Analytics integrations - [PostHog](https://viktor.com/integrations/posthog) - [PostHog (EU)](https://viktor.com/integrations/posthog-eu) - [OpenAI (ChatGPT)](https://viktor.com/integrations/openai-chatgpt) - [Sentry](https://viktor.com/integrations/sentry) - [Mixpanel](https://viktor.com/integrations/mixpanel) - [Akeneo](https://viktor.com/integrations/akeneo) - [IPGeolocation](https://viktor.com/integrations/ipgeolocation) - [Amplitude](https://viktor.com/integrations/amplitude) ## FAQ ### Does Viktor integrate with Tricentis qTest? Yes. Tricentis qTest is one of the 9,800+ tools Viktor connects to, via a managed connector. Once connected, anyone on your team can put Viktor to work in Tricentis qTest from their workspace - no workflow builder, no code. ### How do I connect Tricentis qTest to Viktor? Ask Viktor in your workspace to connect Tricentis qTest, then approve the one-click OAuth prompt. Viktor never sees your password, handles authentication itself, and starts working right away. Setup takes about two minutes, and you can revoke access at any time. ### What can Viktor do in Tricentis qTest? Viktor can run 12 Tricentis qTest actions, including Get Defect, List Defects, and List Modules - and chain them with other tools in a single request. In practice that means Viktor helps you build, test, and deploy code through CI/CD pipelines. If a task spans several actions, Viktor plans the sequence itself and reports back when the work is done. ### Do I need to build workflows for Tricentis qTest? No. Viktor isn't a workflow builder - there are no triggers to map and nothing to maintain. You ask for the outcome in plain English in your workspace, and Viktor decides which Tricentis qTest actions to take, runs them, and reports back. ### Is my Tricentis qTest data secure with Viktor? Yes. Viktor connects to Tricentis qTest in one click via OAuth, runs in an isolated environment per team, and never trains models on your data. Sensitive actions wait for your approval, and you can revoke access at any time. Viktor is SOC 2 Type 1 compliant, with Type 2 and ISO 27001 in progress. ### How much does the Tricentis qTest integration cost? Nothing extra - every integration, including Tricentis qTest, is available on every plan. You can start free with up to $100 in credits, no credit card required; the Team plan is $100 a month. ### Can Viktor use Tricentis qTest together with my other tools? Yes - that's the point. Viktor connects to 9,800+ tools and works across them in a single run: he can pull data from Tricentis qTest, cross-reference it with another tool - for example Slack or Gmail, and deliver the finished result in your workspace. ## Get started Viktor is free to start - up to $100 in credits, no credit card required. All 9,800+ integrations are included on every plan. Sign up at https://viktor.com or browse all integrations at https://viktor.com/integrations.