Continue from Allure Report

Allure TestOps is the server-side continuation of Allure Report. Your adapters, result files, and test framework stay the same. What changes is the operating model around those results: Allure TestOps keeps them in shared launches, adds triage and defect workflows, and makes them reusable across time.

Follow the Continue from Allure Report tutorial to do the first upload and see how reports become launches.

What changes

• Launches become shared execution records instead of isolated report artifacts.
• Results stay available for later comparison and investigation.
• Dashboards and defects help teams review trends across runs.
• Project and access models make reporting collaborative.

Moving to Allure TestOps

1. Keep developing and running the same tests.
2. Update pipelines to send results to Allure TestOps using allurectl or a CI system plugin.
3. Close launches so Allure TestOps creates and updates automated test cases.
4. Add metadata like tags, links, environments to launches where the team needs them for filtering and review.

Next steps

• Launches and Test results for the basic review workflow.
• Defects and Compare launches for cross-run analysis.
• Connect CI for repeatable ingestion from pipelines.
• Connect issue tracker to tie failures to work items.