Kiwi

Kiwi for Tricentis qTest

Have the agent on a Kiwi step read requirements and write test cases in Tricentis qTest Manager through your qTest site's MCP server.

  • Your agent works in Tricentis qTest through its own connection. Kiwi does not call Tricentis qTest and never holds its credentials.
  • A workflow skill can list Tricentis qTest among the tools it requires. When you supply your agent's available tools to a skill check and Tricentis qTest is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Tricentis qTest, with notes, under Connections and bind them to the steps that use them. The agent reads them with list_connections.
  • The agent can report the tools and plugins it ran with, including its Tricentis qTest connection, with report_configuration.
  • The agent submits links to its work in Tricentis qTest as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Tricentis qTest

  • Read requirements and the modules that organize them in a qTest project.
  • Create and edit test cases for a requirement in the right module.
  • View test runs and their results.
  • Create a defect for a failure the agent found, and view existing defects.

Set up

  1. Connect your agent to Kiwi

    Add Kiwi's hosted MCP server, https://kiwiflow.io/mcp, to your coding agent.

  2. Connect your agent to Tricentis qTest

    Add the Tricentis qTest MCP server to your agent with this URL. The credentials stay with your agent.

    https://{tenant}.qtestnet.com/mcp
  3. Example skill

    Publish instructions like these as a workflow skill that lists Tricentis qTest among its required tools.

    Start from the requirement ID and the qTest project in the assignment.
    Read the requirement and write test cases for it in the matching module.
    Create a qTest defect for each failure found in the existing test runs.
    Submit the new test case and defect IDs with their links as outputs.
    If the API token lacks a permission, stop and report a blocker to the
    qTest admin; the assigned reviewer checks the new test cases.