Test Cases
A test case defines one scenario to be tested, along with its steps, preconditions, and expected results. Test cases are stored in a hierarchical tree of folders and subfolders, and each folder shows a cumulative count of the test cases inside it.
This page covers organizing test cases into folders, creating and editing them, the 2 templates available, properties, reordering, cloning, deleting, versions, review, comments, filtering, run history, and bulk actions.
Folders
Section titled “Folders”Create a folder
Section titled “Create a folder”-
In the left navigation, open Test Cases.
-
Click + Create a Folder, or click the Add Folder icon.
-
In the text box that opens, enter a name and click the plus icon (+).
-
Open the folder and click + Create Test Case to add a test case to it.
Create a subfolder
Section titled “Create a subfolder”-
Click the ellipsis icon (⋯) next to the parent folder and select Add Sub Folder.
-
In the text box below the parent folder, enter a name and click the plus icon (+).
-
Open the subfolder and click + Create Test Case to add a test case to it.
Move, rename, or delete a folder
Section titled “Move, rename, or delete a folder”The ellipsis icon (⋯) next to a folder offers Move Folder, Rename Folder, and Delete Folder, along with Create Test Case and Add Subfolder.
Create a test case
Section titled “Create a test case”-
In the left navigation, open Test Cases.
-
Click + Create. Alternatively, click the ellipsis icon (⋯) next to a folder or subfolder and select Create Testcase.
-
In the dialog, enter a title. A description is optional.
-
Select a template type, either Documentation or Steps.
-
Click Folder, choose a location in the overlay, then click Select Folder.
-
Select any additional properties.
-
Click Create.
-
On the test case details page, add your test steps. Steps save automatically.
The template type you pick sets the shape of the test case. Both accept attachments up to 25 MB, including screenshots, logs, and documents.
| Aspect | Documentation | Steps |
|---|---|---|
| Use it for | Simple tests with basic preconditions, steps, and expected results | Tests needing a granular breakdown of each action |
| Expected results | Defined per step, or once for the whole test case | Defined for each individual step |
Documentation template
Section titled “Documentation template”- Test Case Title: a title reflecting the purpose of the test.
- Preconditions: conditions that must be met before the test runs.
- Test Steps: a sequential list of the actions to perform.
- Expected Results: the expected outcome of each step, or of the test case as a whole.
For example, a Login functionality test case has the precondition that the user holds a valid username and password. Its steps are navigating to the login page, entering the username and password, and clicking Login. Its expected result is that the user lands on the dashboard.
Steps template
Section titled “Steps template”- Test Case Title: a clear, descriptive title for the scenario.
- Test Steps: each step with its own specific action.
- Expected Results: the result expected after each individual step runs.
For example, a User registration flow test case enters a valid email address and password, expecting both fields to be populated. It then clicks Submit, expecting the confirmation page to open. It then verifies the confirmation message, expecting a success message to appear.
Test case properties
Section titled “Test case properties”Properties classify and organize a test case. Select them when you create it, or in the Test Case Properties section afterwards.
- Location: the folder the test case is stored in.
- Priority: the urgency and execution order of the test case, one of Critical, Major, Medium, or Minor.
- Owner: the team member responsible for the test case.
- Reviewer: the team member who reviews the test case.
- Automation Type: the automation status of the test case, one of Not Automated, Automated, Obsolete, or Automation Not Required.
- Status: the current state of the test case in the testing lifecycle. Values include Ready, Draft, Rework, and In Review.
- Test Case Type: the type based on purpose and testing approach, for example Functional, Regression, or Smoke.
- Requirements: Jira stories linked to the test case.
- Labels: labels linked from the dropdown.
- Attachments: files that support the test case.
Edit a test case
Section titled “Edit a test case”-
In the left navigation, open Test Cases.
-
In the Test Case List, click a test case to open the Quick View overlay.
-
Click the edit icon.
-
Update the Test Case Name, Test Steps, Folder, Properties, or any other field. Changes save automatically.
Reorder test cases
Section titled “Reorder test cases”-
In the left navigation, open Test Cases.
-
Open the folder holding the test cases.
-
Drag the test case by its Drag Handle to its new position. The new position takes effect immediately at the folder level, and carries into all related test runs.
Clone a test case
Section titled “Clone a test case”Cloning copies every field value as it stands at the moment you clone. Later changes to the original do not reach the copy.
-
In the left navigation, open Test Cases, then open the folder or subfolder holding the test case.
-
Click the ellipsis icon (⋯) next to the test case, then click Clone. The Clone Test Case dialog opens.
-
Enter a title.
-
Select the Target Project and Folder to clone into.
-
Click Clone.
Versions
Section titled “Versions”View version history
Section titled “View version history”-
In the left navigation, open Test Cases, then open a test case.
-
In the top right, click the history icon. The Version History overlay lists every saved version with the date of the change and the user who made it.
Compare versions
Section titled “Compare versions”-
In the Version History overlay, hover over a version.
-
Click the ellipsis icon (⋯), then click Compare with Current. The Comparison Mode page opens and shows the differences between that version and the current one.
Review management
Section titled “Review management”Review management adds a review step to test cases. A QA member submits a test case, and the reviewer either marks it ready or sends it back for rework with comments.
Enable review management
Section titled “Enable review management”-
In the left navigation, go to Project > Project Settings.
-
Turn on Review Management.
Submit a test case for review
Section titled “Submit a test case for review”-
In the left navigation, open Test Cases, then create or open a test case.
-
Click Submit for Review.
-
Select a Reviewer.
-
Click Submit for Review.
Review a submitted test case
Section titled “Review a submitted test case”-
On the Dashboard, go to Test Case Review Status.
-
Click a test case submitted for review. The test case details page opens.
-
Click Mark as Ready to approve it, or click Mark as Rework, add your comments, and submit it to send it back for changes.
Every review action is recorded in the Activity section of the test case.
Comments
Section titled “Comments”Add a comment
Section titled “Add a comment”-
In the left navigation, open Test Cases, then open a test case.
-
In the Activity section, type your message in the comment field.
-
Click Add Comment. The comment appears in the Activity section.
Reply to and manage comments
Section titled “Reply to and manage comments”- Click the reply icon to respond to a comment.
- Click the emoji icon to add a reaction.
- Click the edit icon to change a comment, then click Update Comment.
- Click the ellipsis icon (⋯) on a comment for Copy Link, which gives a direct link to that comment, or Delete, which asks you to confirm.
Find test cases
Section titled “Find test cases”Filter the list
Section titled “Filter the list”-
In the left navigation, open Test Cases, then click Filter by. Alternatively, press
Command+Shift+F. -
In the popover, select the properties to filter on.
-
Click the plus icon (+) next to a selected property, then select the values you want in its panel.
-
Review the filtered list.
-
Click Clear All to remove the filters.
You can filter on Priority, Automation Type, Test Case Type, Status, Label, Created At, which takes a date or a date range, and Folder.
Choose which columns appear
Section titled “Choose which columns appear”-
In the left navigation, open Test Cases, then click View.
-
Select the properties to show or hide. The list updates to show only what you selected.
Run history
Section titled “Run history”Run history lists every execution of a test case across the test runs it belongs to, so you can check stability and execution ownership without opening each run.
-
In the left navigation, open Test Cases, then open a test case.
-
Scroll to the Activity section.
-
Click Run History. The tab lists every test run the test case belongs to, with its execution status, executor, and timestamp.
-
Click a run to open its detailed view.
Delete a test case
Section titled “Delete a test case”-
In the left navigation, open Test Cases.
-
Click the ellipsis icon (⋯) next to the test case, then select Delete.
-
On the Delete Test Case? dialog, click Delete Test Case.
Bulk actions
Section titled “Bulk actions”-
In the left navigation, open Test Cases.
-
Press
Command+K, then select Bulk Update Test Cases from the Testsigma Command Center. -
Change properties, move test cases to a different folder, or delete several test cases at once.
Was this page helpful?
Thanks for the feedback.