Continue from Allure Report

Already have Allure Report? Good news: you are almost in TestOps. This tutorial shows how to upload your report from your computer or from a CI/CD pipeline.

Preconditions

Before you start, make sure you have a TestOps project for the team, product, or service whose results you want in TestOps.

For the clearest first result, use an empty project. This makes the first launch, generated test cases, and analytics easier to see.

For the detailed setup, see Create your first project.

The Plan

1. Upload local test results.

2. Connect the CI/CD pipeline.

Upload Local Test Results

1. Run tests locally

Use a folder with existing test results, or run your tests as if you were going to generate an Allure Report. You need the Allure results directory, not the generated report.

The directory is usually named allure-results, unless your project uses a custom path.

2. Send them to TestOps

In your TestOps project:

1. Go to Launches.
2. Drag and drop the Allure results directory onto the launch list. You can upload a ZIP archive with the same results instead.
3. Keep or adjust the launch name.
4. Click Upload files.

After the upload finishes, open the new launch. Voila: your results are already in TestOps.

Note that the launch contains test results with execution status and context. The detail you see depends on the granularity of the annotations in your code.

3. Close the launch

Click Close launch.

Closed launches update project history, automated test cases, and analytics.

Result

TestOps has uploaded the same results you would use for Allure Report, without changes to test code or pipeline configuration. It has also generated automated test cases from them.

Open the launch and spend a minute with the new view before you close it:

1. Check the launch statistics.
2. Open Test results to inspect statuses, steps, attachments, and errors.
3. Open Timeline to see how the run unfolded.
4. Open Test cases to see the automated cases created from the upload.

This is the first TestOps difference: the report did not change, but the results are now stored, searchable, and connected to test documentation generated from code.

Connect the CI/CD Pipeline

Now local upload works, and you are ready to connect your pipeline.

In the pipeline step that runs tests, add the values allurectl needs and replace your current test command and Allure publishing step with:

ALLURE_ENDPOINT=<TestOps URL> \
ALLURE_TOKEN=<API token> \
ALLURE_PROJECT_ID=<project ID> \
allurectl watch -- <test command>

allurectl is a binary that sends results to TestOps in real time. This usually makes the pipeline simpler: the command runs the tests and uploads the results in one step.

1. Change the pipeline.
2. Run it.
3. Open TestOps and watch the test results flow into the launch.

For the allurectl setup, see Command-line tool - allurectl. For CI-specific examples, see Integrations with CI systems.

Result

TestOps receives automated results from CI/CD.

Open Launches after the pipeline finishes and check that the new launch is created from the CI run.

This means the team no longer needs to upload reports manually for regular automation runs.

Congratulations, You Are in TestOps

You have uploaded an existing Allure Report run and connected your pipeline so new launches can arrive in TestOps automatically.

Check that:

1. The expected tests and statuses are present.
2. Steps, attachments, and metadata appear where your team expects them.
3. Failed and broken results are visible enough to triage.
4. The launch remains available after the local report would normally be gone.
5. Teammates can open the same launch and understand what needs attention.

Next Steps

Review the first launch in more detail: Review the first launch.

Keep generated test documentation reliably connected to code: Test keys and Allure IDs.

Review Tags, labels, layers, and custom fields if you want TestOps to interpret more labels from your Allure results.

Configure Jobs if you want to start CI runs, reruns, or selected test scopes from TestOps.