Connect Automation to Allure TestOps

Your tests already run in a framework and CI pipeline. This path adds Allure-compatible reporting so results flow into Allure TestOps automatically. Follow the tutorial to do the first upload and see how results become launches.

What this path adds

What changes is the reporting layer around your existing tests:

• test runs produce Allure-compatible result files;
• results are sent to Allure TestOps and appear as launches;
• Allure TestOps generates automated test cases when the launch is closed;
• history, analytics, and review are available to the whole team.

Typical rollout path

Most teams connect automation in four steps:

1. Add an Allure adapter to the existing test project.
2. Run the tests locally and confirm that result files are created.
3. Upload the first results to Allure TestOps and review the generated launch.
4. Add allurectl to the CI pipeline so future launches arrive automatically.

Next steps

Reference for the rollout steps:

• Allure Report adapters for the full list of supported frameworks.
• allurectl for the command-line upload tool.
• Run automated tests for the full upload and launch flow.

After the first upload works:

• Test keys and Allure IDs to keep generated test documentation reliably connected to code.
• Tags, labels, layers, and custom fields when you want Allure TestOps to interpret richer metadata from results.
• Metadata update settings when some fields should stay managed in Allure TestOps instead of being overwritten by automation.
• Move reports to Allure TestOps for a broader production rollout across projects, launches, CI, and metadata.