Allure TestOps ecosystem

The TestOps ecosystem reduces the amount of custom glue code teams need around the product. Start here when you need to choose the right tool class.

Choose the tool by where the workflow lives

• Use allurectl when the workflow should run in CI or in a shell and you need a portable CLI for upload, launch control, or selective execution.
• Use the JetBrains IDE plugin or VS Code plugin when the work starts on a developer workstation instead of a CI server.
• Use the MCP server when another tool or agent should call TestOps through the MCP contract.

All tools and plugins

If you are between two choices

• Pick allurectl over an IDE plugin when the workflow must be reproducible in CI.
• Pick a server-side plugin over allurectl when the CI platform has a first-class plugin and you want the richer bidirectional integration path.
• Pick the JetBrains plugin over the VS Code plugin when the workflow depends on Allure ID assignment or manual-to-automated case handoff.

When to leave the ecosystem section

• Use Integrations when the job is the exact CI, issue-tracker, or TMS connection page.
• Use Reference when you need API, AQL, or release information instead of tooling choice.