Test cases

Write manual test cases with steps, link automated test cases to tests in your Orchestrator packages, and follow versions and results.

A test case describes how to check one behaviour. Its Type decides how it runs: Manual: a person follows its steps and records the outcome. Automated: it is linked to an automated test. A test from the Orchestrator catalog runs as a job on a Robot; a test from another framework gets its result from a report. Hybrid: partly manual, partly automated. With an automation link it runs like an automated test case; without one, like a manual one. Every saved change to a test case creates a new version. An execution records the version that ran. Create a test case# Open Testing ▸ Test cases and select New test case. Enter a Title and a Description. Choose the Type, Status (Draft, In review, Approved, Deprecated), Priority and Owner. Pick one or more Categories (from the project's test case categories), and optionally fill in Preconditions, Expected outcome, Postconditions and Labels. Select Create test case. The list shows each test case's steps and version, categories and labels, type, automation provider, priority, status, Last result and the number of requirements it verifies. Select several rows to set their status, add a label or archive them together. Write the steps of a manual test case# Open the test case and select the Steps tab. Select Add step and fill in the Action, the Expected result and, if needed, the Test data. Under each step, use the arrows to move it, or Insert below, Duplicate, Paste below and Delete. To add many steps at once, select Paste steps and paste one step per line, with the action, expected result and test data separated by |. Select Insert steps. Optionally enter a Change description, then select Save steps. Discard returns to the saved steps. Link a test case to an automated test# Before you start, connect the project to Orchestrator so the catalog lists your tests. Open the test case and select the Automation tab. Under Link an automated test (or Change the link), choose the Framework: Orchestrator for a test in your Orchestrator packages, or another framework whose results you report from CI. For Orchestrator, use Search the catalog and pick the test. For another framework, enter its Test id (the id your framework reports, for example tests/test_refund.py::test_ok) and, optionally, Repository, Branch, Path and Framework version. Select Save link. Remove link turns the test case back into one that is run by hand. Link from StudioIn Studio, the ribbon's QA Hub menu can create and link QA Hub test cases for your Studio test cases. See Run tests. Link requirements# On the test case's Requirements tab, link the requirements the test case verifies. See Releases and requirements. Follow results and versions# Results lists every result of the test case: the execution, the result, the version executed, the source, who or which Robot ran it, when it finished and how long it took. Versions lists each version with its change description, author and date. Open an older version to compare it, and Restore it to make its content current again (as a new version). Other actions# Use ⋮ on a test case to Run it on its own (an ad-hoc execution), Clone, Archive or Restore, or Delete it. A test case with results cannot be deleted; archive it instead. Archived test cases are not run. Next steps# Test sets Run tests

Create a test case

Write the steps of a manual test case

Link a test case to an automated test

Link requirements

Follow results and versions

Other actions

Next steps