Build, run & execute tests
An end-to-end walkthrough — author a test case with steps, plan a run, execute it, and record results and defects.
This guide takes one test from blank to executed. It uses the universal item actions from Working with items for the parts that are the same everywhere, and focuses on what’s specific to verification. For the concepts behind each piece, see Test cases & steps, Test plans, and Runs & execution.
Build a test case
A test case is an item, so you create it the standard way — what’s specific is the steps.
Before you start Open the Tests module in your project. Know which requirement this test will verify.
- Create a test case the usual way — + Add, or right-click in the tree and choose Add Item.
- Give it a name and complete its fields.
- In the test case's steps, add a step and fill in the Action (what the tester does) and the Expected result. Add a step for each action to verify.
- For behavior-driven tests, switch a step to BDD to express it as Given / When / Then.
- Save, then link the test case to the requirement it verifies (see Links).
Result A test case with ordered steps, linked to its requirement so coverage updates automatically.
Plan the work
A test plan gathers the cases you’ll execute together.
- Create a test plan for the scope you're verifying — a release, a feature, a regression pass.
- Add the test cases that belong in it.
Result A plan you can run against. See Test plans for organizing larger efforts.
Create a test run
A run is one execution of a plan, assigned to people, on a deadline.
- Start a new test run and give it a Run Name.
- Choose the Test Plan to run, or Include all test cases.
- Add a Description, set a Due Date, and attach it to a Milestone if you're tracking against one.
- Add References (such as a requirement or external ticket) and assign the people who'll execute it.
- Choose Create Test Run.
Result A run is created and assigned, ready to execute, and visible on the milestone you tied it to.
Execute the run
Before you start Open the run assigned to you.
- Work through each test case step by step.
- For each step, record the result — Pass, Fail, or Blocked — and note the actual result.
- Attach Evidence (a screenshot, log, or file) where it's needed to prove the outcome.
- On a failure, raise a Defect from the step so the problem is captured and linked.
- Complete the run when every case has a result.
Result Results are recorded against each step with evidence attached, defects are linked back to the steps that found them, and verification status rolls up to the requirement and your dashboards.
Note Re-running a test creates a fresh result while keeping the execution history, so you can see how a test fared across runs. See Defects for tracking failures to closure.
Where to go next
To prove every requirement is covered by a passing test, see Coverage.