Connect Automation to TestOps

Already have automated tests? Nice. This tutorial shows how to make them produce Allure-compatible results and send those results to TestOps from your computer or from a CI/CD pipeline.

Preconditions

Before you start, make sure you have a TestOps project where you can upload results.

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. Add Allure reporting to your tests.

2. Upload local test results.

3. Connect the CI/CD pipeline.

Add Allure Reporting to Your Tests

Add the Allure adapter library to your test project and run the tests locally.

For framework-specific setup, see Allure Report adapters.

No adapter for your stack? Still not a dead end: send results from an unsupported technology.

You do not need to generate the Allure report to complete this tutorial. But if you want to see what free, framework-agnostic reporting looks like, go for it: how to generate Allure Report.

Result

Your existing automation now produces Allure-compatible result files and a standardized reporting layer.

Open the results directory and check that files were created after the test run. The directory is named allure-results by default.

This means TestOps can read your automated test output without adding proprietary dependencies to the test code.

Bonus: you also get clear, informative, technology-agnostic reports, which is especially useful for teams with several technology stacks.

At this point, the report may still be minimal. To add more information and metadata, use Allure annotations; for the basics, see Improve readability.

Upload Local Test Results

1. 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.

2. Close the launch

Click Close launch.

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

Result

TestOps has uploaded your first Allure-compatible results and 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: your automation output is 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.

Commit the Allure adapter changes, so CI runs the same Allure-aware tests you checked locally.

In the pipeline step that runs tests, add the values allurectl needs and replace your current test command and report 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. Commit the Allure adapter changes.
2. Change the pipeline.
3. Run it.
4. 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 a separate reporting step for regular automation runs.

Congratulations, Your Automation Is in TestOps

You have added Allure-compatible reporting to existing automated tests 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 pipeline run is finished.
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.