Kiwi

Kiwi for Allure TestOps

Have the agent on a Kiwi step run tests under allurectl so the results reach an Allure TestOps launch, and return the launch link.

  • Your agent works in Allure TestOps through its own connection. Kiwi does not call Allure TestOps and never holds its credentials.
  • A workflow skill can list Allure TestOps among the tools it requires. When you supply your agent's available tools to a skill check and Allure TestOps is not among them, the check reports SK15-UNSUPPORTED-TOOL.
  • A project Admin can add links to Allure TestOps, 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 Allure TestOps connection, with report_configuration.
  • The agent submits links to its work in Allure TestOps as the step's outputs. People review them, and sign-off stays with the people your workflow names.

What your agent can do in Allure TestOps

  • Run a test command with allurectl watch so its Allure results upload to a new launch as they are written.
  • Upload an existing Allure results directory to a launch with allurectl upload.
  • Save the test plan chosen in Allure TestOps as testplan.json to run only those tests.
  • Link an issue to a launch with allurectl launch add-issue.
  • Read the current launch's URL from allurectl job-run env.

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 Allure TestOps

    Install the Allure TestOps command-line tool where your agent runs. The credentials stay with your agent.

    allurectl watch -- <your test command>
  3. Example skill

    Publish instructions like these as a workflow skill that lists Allure TestOps among its required tools.

    Start from the Allure TestOps project ID and test plan ID in the assignment.
    Save the plan with `allurectl test-case plan`, then run the tests under
    `allurectl watch` so the results reach a new launch.
    Submit the launch link and the failed test count as the step's outputs.
    If the upload fails, stop and report a blocker to the step owner; the
    assigned reviewer reads the launch in Allure TestOps.