First evaluation

Allure TestOps can help you centralize test assets, connect teams, and make quality work easier to follow. Explore the minimal setup to see how it works and whether it fits your situation.

Minimal setup checklist

1. Create your first project
2. Invite users to the instance if teammates do not yet have accounts.
3. Add collaborators to a project.
4. Choose one first execution path: run a manual test or run an automated test.
5. Review the first launch.
6. Create a combined launch if you want to review manual and automated evidence together.

Choose manual or automated execution based on what is easiest to try first. You do not need to exercise every feature — one complete end-to-end flow is enough.

What the setup gives you

Before you move on, check what this setup already gives you:

• everyone involved works in the same project;
• manual and automated tests meet in one test model naturally;
• automated test execution is transparent and available to the team;
• unresolved failures are surfaced clearly, with flexible ways to handle them;
• automated test cases appeared from test results, without manual test case creation.

What to do once this works

• Explore dashboards. Think about the goals you want to track and how the available widgets match them.
• Use Next steps to connect CI, issue tracking, and dashboards.
• Use Use Allure TestOps when your team is already working inside projects every day.
• Use Administer Allure TestOps when you need organization-wide user or governance changes.
• Use Self-Hosted when deployment-specific operations become the blocker.