Getting started

You are one step away from trying Allure TestOps.

If you do not have access yet, request a trial or contact our team. If Allure TestOps is already available to you, choose your starting point below.

Where is your team now?

Use Continue from Allure Report if your team already uses Allure Report and now wants persistent launches, history, analytics, and team review in Allure TestOps.
Use Connect Automation to Allure TestOps if your team already has automated tests, but they do not yet produce results based on the open Allure standard.
Use Start with test management if automation is your next step after manual test management.
Use First evaluation if you are not sure which path fits your team yet or want the fastest generic first-success path.

Use these pages if you want to understand the product model, choose a deployment option, or find account and token basics before you start:

How Allure TestOps works for the mental model behind projects, launches, and shared review.
Choose default or self-hosted deployment if you still need to choose who will operate the platform.
Terms and concepts for a tighter glossary while you work through the first setup.
User menu and API tokens for account and token basics used by several onboarding tasks.

Next steps for the usual post-evaluation route: CI, issue tracking, and dashboards.
Use Allure TestOps for day-to-day project workflows after the first path works.
Administer Allure TestOps for instance-wide access, identity, and governance.
Self-Hosted for installation, configuration, and upgrade work if your team operates the platform.

If you want a broader walkthrough before diving into the individual pages, you can also watch our introductory course on YouTube: