A Test Case describes what to test and how to check the expected behavior. Its Test Runs record what happened when you executed it. Open a case by selecting its key or headline in the Test Case list.
Start with the key, headline, and version
Part | What it means |
Test Case key | The readable reference assigned to the case, such as DEMO-C46. Use it to find and share the case. |
Headline | A short summary of the behavior being tested. |
Version | The version of the case’s details and script you are viewing. Check it before editing or executing. |
A step number such as Step #1 identifies its position in a script or run. It is not the Test Case key.
Main: describe and organize the case
Use Main to review the description, preconditions, Activity, and case properties. Preconditions explain what must be ready before testing.
Properties include type, priority, status, assignee, owner, labels, components, and estimated time where enabled. Linked work items, Test Folders, Test Plans, and other cases show related testing context.
Use the save controls shown for the field you are editing. Some selections save immediately; rich text and other grouped edits have their own save action.
This screenshot shows the Main tab in an earlier layout.
Test Script: explain how to test
Use Test Script to write the procedure and expected behavior. Choose the script format that fits your workflow.
Format | Use |
Multi Steps | Separate actions, test data, and expected results into ordered steps. |
Plain Text | Describe the procedure in one text script. |
BDD (Gherkin) | Describe behavior with Given, When, and Then steps. |
Automation | Store an automation script for the supported integration workflow. |
This earlier screenshot illustrates a Multi Steps script. Writing a script does not itself record a test result.
Test Runs: review executions
Use Test Runs to find execution records associated with the case. Open a run to review its context, recorded results, and evidence. Check the run’s case version and Test Plan iteration where applicable.
A run has its own key, such as DEMO-TR246. Separate runs let you record different executions without treating each result as a new Test Case.
For changes to the case itself, use Activity history. For execution instructions, see execute Test Cases.