TestOps logo
Try TestOps

Start with test management

This tutorial covers a manual-first path in Allure TestOps for teams moving from a legacy TMS. You will explore test case structure, write a scenario-rich test case, plan a run, execute it, and see how the same test case connects to automation when the team is ready.

Explore the tree view

If you are coming from another TMS, start with trees.

Trees group test cases by metadata such as Epic, Feature, Story, and Suite. In Allure TestOps, structure comes from metadata rather than from a fixed folder hierarchy.

Go to Test cases and open the tree selector in the top left corner.

For the full setup, see Project trees.

Create a manual test case

Open your project and go to Test cases.

Create the test case inside a tree group. This shows how Allure TestOps applies structure from metadata.

If no tree group is available, create it from the root using the bottom floating panel.

Click + Test Case, enter a name, and press Enter.

The field used by the tree is filled in automatically based on where you created the case.

Note the Allure ID in the test case details — this is how the same test case can connect to automated code later without creating a duplicate.

Explore test case capabilities in Test cases.

Shape the scenario

In the test case details, fill in the Scenario section.

Enter the steps directly, then use keyboard navigation and hotkeys to move through them and create nesting. For experienced users, this makes manual test authoring fast without switching between forms.

Keep the first version readable:

  1. Add the main user actions as steps.
  2. Add expected results where the tester needs a clear check.
  3. Use sub-steps only when a step is too large to execute safely as one line.
  4. Add shared steps for repeated setup, navigation, or verification blocks.
  5. Add a tag or owner if your team uses them to organize scope.

For deeper authoring options, see Manual test scenario and Shared steps.

Add it to a test plan

Go to Test cases, select the test case, click ⋯ in the bottom panel, and select Test plan.

Enter a plan name, then click Submit.

For this first pass, keep the plan small. You are checking the approach, not rebuilding the full regression suite.

A plan can combine manual and automated execution, so the release scope does not have to split into separate manual and CI runs.

Explore planning capabilities in Test plans.

Run the plan

In Test plans, run the plan and keep the suggested launch name.

Open the created launch, execute the manual test, set the step statuses, then finish the test result with Passed or Failed.

When the run is complete, click Close launch.

Open the closed launch and review the status, scenario steps, and execution context. The team can now see planned manual work, execution evidence, and review data from the same launch.

Explore manual execution in Run manual tests.

Check the automation path

Return to the Allure ID you noted earlier.

Open the test case menu and check Generate code. Allure TestOps can pre-generate a code template with the test case metadata for your language and framework.

When the team automates this scenario, the automated test can emit that ID. After upload, Allure TestOps updates the existing test case instead of creating a disconnected automated duplicate.

Manual tests need manual maintenance, while automated test cases can be created and updated from uploaded results — that is the boundary the Allure ID manages.

For the exact automation workflow, see How to automate a manual test. For code templates, see Generating code for test case automation.

Next steps

You have created a manual test case, made it executable, planned it, run it, and checked how it connects to automation. That is enough to compare Allure TestOps with a legacy TMS using a real path, not a feature checklist.

© Qameta Software Inc. All rights reserved.