QA Wolf

Bug reports flow into Jira and Linear, where QA Wolf automatically creates, syncs and closes issue tickets, and results sync to test management tools (TestRail, Xray, Zephyr, Qase and Testmo). Deployments are heard from GitHub and GitLab, notices go to Slack and Microsoft Teams, and webhooks reach any other bug tracker. Its tests can call APIs, seed databases, toggle feature flags and use email inboxes. Writes into the customer's issue trackers mean access runs both ways, and webhooks and helper libraries extend it to other tools.

SourceQA Wolf, docs.qawolf.com Jira, Linear, test management integrations and webhooksread 2026-09-21

Run Rules sequence the order of flows and their dependencies in a suite, and flows pass authentication tokens, user IDs and other values between each other in a coordinated run. Tags build custom suites, runs execute in parallel with automatic reruns of failures, and triggers choose which flows run on each deploy or schedule.

SourceQA Wolf, docs.qawolf.com Run Rules, pass data between flows, tags and triggers, and qawolf.com/pricingread 2026-09-21

Before it builds or explores, the agent reads documentation linked in a prompt, test plans, product requirements and help docs, and it applies team conventions written into custom skill files in every session. Company knowledge enters as linked pages and skill files the agent reads per session. No index, retrieval layer or refresh of the customer's sources is documented.

SourceQA Wolf, docs.qawolf.com test automation, coverage mapping and custom skillsread 2026-09-21

Tests can be created unattended from a prompt, or the agent can work with a person who guides it, and a person can take over the browser during mapping while the agent watches. The generated tests are standard code the team reviews and versions. Choosing guided or unattended working sets an autonomy mode, but no approval step that holds the agent's action for a person is documented.

SourceQA Wolf, docs.qawolf.com test automation and coverage mappingread 2026-09-21

QA Wolf states it is SOC 2 Type II compliant, verified through independent audits, with HIPAA ready infrastructure. Customers can set up single sign-on over SAML 2.0 and OpenID Connect, and credentials are stored securely for use in tests. That pairs a held attestation with sign in through the customer's identity provider.

SourceQA Wolf, docs.qawolf.com why QA Wolf (security and data protection) and single sign-onread 2026-09-21

Each run of the customer's tests is recorded with results, the verdict reached when evaluating each deployment for a trigger is kept, and a person can watch the agent open a browser and explore during mapping. A step by step record of the agent's own prompts, tool calls and decisions is not described.

SourceQA Wolf, docs.qawolf.com triggers and diagnosing a trigger, coverage mapping, and qawolf.com/pricingread 2026-09-21

The coverage map, the test code and run history persist, and skill files the team writes apply in every agent session. No session, workflow or long term memory that the agent itself writes and reuses is documented.

SourceQA Wolf, docs.qawolf.com custom skills and coverage mappingread 2026-09-21

Tests run on QA Wolf's own managed infrastructure, with a shared, allowlisted or private iOS device pool, local runs through its CLI, and Playwright tests customers can export at any time. No deployment of the platform in the customer's environment or choice of data region is documented, so where data is kept is not stated.

SourceQA Wolf, docs.qawolf.com iOS device pools, CLI local execution, and qawolf.com/pricingread 2026-09-21

QA Wolf offers solution recipes and helper libraries for testing scenarios such as emails, barcodes, video injection and web performance. No catalog of ready made agents, templates or packaged workflows a buyer adopts for its own work is documented.

SourceQA Wolf, docs.qawolf.com solutionsread 2026-09-21

Triggers run chosen flows whenever an application deploys, reported through GitHub or GitLab deployments or a webhook, or on a schedule. Smart Smoke Suites automatically select the flows affected by each pull request, and the automation agent diagnoses broken tests and refactors test code after failures. Work starts on a deploy, a schedule or a pull request without a person asking.

SourceQA Wolf, docs.qawolf.com triggers, Smart Smoke Suites, and qawolf.com/llms.txtread 2026-09-21

The judge model is the customer's choice in the non-deterministic AI assertions, with ChatGPT documented as a drop in replacement with the same signature and return shape. They are designed for apps that use different AI providers, so the customer makes the model choice in its own tests.

SourceQA Wolf, docs.qawolf.com non-deterministic AI assertionsread 2026-09-21

QA Wolf publishes a REST API giving direct HTTP access to core platform actions, a TypeScript CI SDK for triggering and reading runs, a CLI for running flows locally, flow and test libraries with API references, and deployment webhooks. An MCP server lets coding agents such as Claude Code and Codex build and run the suite. Together these give a stable API and SDK, a served MCP interface and a fit into CI/CD.

SourceQA Wolf, docs.qawolf.com REST API overview, CI SDK reference, CLI and QA Wolf MCPread 2026-09-21

An application's end to end workflows are mapped into a coverage outline, and the agent generates deterministic Playwright and Appium tests from plain language prompts and runs them in parallel on deploy, on a schedule or on pull requests. Judge model assertions return a structured verdict with hard and soft thresholds on a customer's AI generated responses, and tests validate MCP connections and tool execution. Testing happens before release, as a gate in CI and continuously after.

SourceQA Wolf, docs.qawolf.com why QA Wolf, test automation, non-deterministic AI assertions and triggersread 2026-09-21

Computer use models let the agent open a browser and explore each feature of the customer's application, documenting the workflows it finds. A person can take control of the browser while the agent watches, and tests run in real browsers and on Android emulators and real iPhones and iPads. That is documented control of a real interface.

SourceQA Wolf, docs.qawolf.com coverage mapping and why QA Wolf, and qawolf.com/pricingread 2026-09-21