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, bulk actions, and deduplication.

Folders

Create a folder

1. In the left navigation, open Test Cases.

2. Click + Create a Folder, or click the Add Folder icon.

3. In the text box that opens, enter a name and click the plus icon (+).

4. Open the folder and click + Create Test Case to add a test case to it.

Create a subfolder

1. Click the ellipsis icon (⋯) next to the parent folder and select Add Sub Folder.

2. In the text box below the parent folder, enter a name and click the plus icon (+).

3. Open the subfolder and click + Create Test Case to add a test case to it.

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.

Note

Deleting a folder is permanent.

Create a test case

1. In the left navigation, open Test Cases.

2. Click + Create. Alternatively, click the ellipsis icon (⋯) next to a folder or subfolder and select Create Testcase.

3. In the dialog, enter a title. A description is optional.

4. Select a template type, either Documentation or Steps.

5. Click Folder, choose a location in the overlay, then click Select Folder.

6. Select any additional properties.

7. Click Create.

8. 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

• 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

• 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

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.

Note

Which properties are available is configured under Settings > Manage Properties. See Test properties.

Edit a test case

1. In the left navigation, open Test Cases.

2. In the Test Case List, click a test case to open the Quick View overlay.

3. Click the edit icon.

4. Update the Test Case Name, Test Steps, Folder, Properties, or any other field. Changes save automatically.

Tip

You can also click the ellipsis icon (⋯) next to a test case and select Edit.

Reorder test cases

1. In the left navigation, open Test Cases.

2. Open the folder holding the test cases.

3. 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.

Note

You can reorder within a single folder only. Selecting multiple folders or leaving any filter active disables reordering.

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.

1. In the left navigation, open Test Cases, then open the folder or subfolder holding the test case.

2. Click the ellipsis icon (⋯) next to the test case, then click Clone. The Clone Test Case dialog opens.

3. Enter a title.

4. Select the Target Project and Folder to clone into.

5. Click Clone.

Versions

View version history

1. In the left navigation, open Test Cases, then open a test case.

2. 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

1. In the Version History overlay, hover over a version.

2. 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.

Note

An older version can be compared only against the current version, not against another older version. To go back to an older version, click Restore to this Version.

Tip

The same ellipsis icon (⋯) also renames a version.

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

1. In the left navigation, go to Project > Project Settings.

2. Turn on Review Management.

Note

This is a project-level setting. Turn it on separately in every project where you want it.

Submit a test case for review

1. In the left navigation, open Test Cases, then create or open a test case.

2. Click Submit for Review.

3. Select a Reviewer.

4. Click Submit for Review.

Tip

You can also submit from the test case list by clicking the edit icon and selecting Submit for Review. To submit several at once, select them in the list, press Command+K, select Submit for Review, and choose a reviewer.

Review a submitted test case

1. On the Dashboard, go to Test Case Review Status.

2. Click a test case submitted for review. The test case details page opens.

3. 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

Add a comment

1. In the left navigation, open Test Cases, then open a test case.

2. In the Activity section, type your message in the comment field.

3. Click Add Comment. The comment appears in the Activity section.

Tip

Type @ to tag a team member.

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

Filter the list

1. In the left navigation, open Test Cases, then click Filter by. Alternatively, press Command+Shift+F.

2. In the popover, select the properties to filter on.

3. Click the plus icon (+) next to a selected property, then select the values you want in its panel.

4. Review the filtered list.

5. 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

1. In the left navigation, open Test Cases, then click View.

2. Select the properties to show or hide. The list updates to show only what you selected.

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.

1. In the left navigation, open Test Cases, then open a test case.

2. Scroll to the Activity section.

3. Click Run History. The tab lists every test run the test case belongs to, with its execution status, executor, and timestamp.

4. Click a run to open its detailed view.

Delete a test case

1. In the left navigation, open Test Cases.

2. Click the ellipsis icon (⋯) next to the test case, then select Delete.

3. On the Delete Test Case? dialog, click Delete Test Case.

Bulk actions

1. In the left navigation, open Test Cases.

2. Press Command+K, then select Bulk Update Test Cases from the Testsigma Command Center.

3. Change properties, move test cases to a different folder, or delete several test cases at once.

Deduplication

Deduplication (Beta) scans every folder of your test case library for redundant test cases and recommends how to resolve each one. A scan compares the title, description, preconditions, steps, and expected results of every test case. Each result is a deduplication finding, with an ID such as DF-12, a match percentage, and a recommendation.

Finding type	What it finds	Recommendation
Exact	Test cases with identical title, description, preconditions, steps, and expected results	Merge
Semantic	Test cases that verify the same behavior in different words	Merge
Parameterize	Test cases that differ only in test data	Parameterize
Refactor	A step sequence that several test cases share, such as a login flow	Extract step group

An independent check verifies each finding before Arcus shows it. Findings the check can’t verify are withheld, and the Deduplication page shows how many. After a scan, test cases in a finding carry a chip in the test case list, such as Duplicate.

Run a scan

Before your first scan, the Test Cases page shows a Find duplicate test cases banner. Click Run first scan on it, or follow these steps.

1. In the left navigation, open Test Cases.

2. Click Deduplication in the toolbar. The Deduplication page opens.

3. Click Run scan. You can keep working while the scan runs. The banner on the Test Cases page shows Scanning for duplicates with the progress.

When the scan finishes, the banner shows the number of findings, how many test cases resolving them would retire, and the time of the last scan.

Note

If the status line says some checks failed, Arcus keeps the findings that include the affected test cases. Run the scan again to refresh them.

Scans can also run automatically on a schedule.

Review findings

1. On the Test Cases page, click Review findings on the banner. The Deduplication page opens.

2. (Optional) Open a tab to show one finding type: Exact, Semantic, Parameterize, or Refactor. Each tab shows how many findings it holds.

3. (Optional) Turn on My cases to show only findings that include test cases assigned to you.

4. Click Review on a finding. The finding opens with a summary of what its test cases have in common and how they differ, followed by the test cases with their folders, owners, and test runs.

Each row in the findings list shows the finding ID, the finding, its scope (such as 3 cases in 1 folder), the finding type, the match percentage, and the recommendation. The time of the last scan shows below the page title. Click Needs a closer look to show only the findings Arcus flagged for extra review.

To dismiss a finding that isn’t a real duplicate, open it and click Discard finding.

Merge duplicates

Resolve an Exact or Semantic finding by keeping one test case and archiving the rest.

Note

Merging archives every test case in the finding except the one you keep. Archived test cases move to Archived in the folder panel, where you can restore them within 90 days. Restoring one doesn’t remove the merged content from the test case you kept. Closed test runs don’t change.

1. Open the finding.

2. Under TEST CASE TO KEEP, select the test case to keep. Arcus marks one as Suggested.

3. (Optional) Click View differences to compare each other test case with the one you keep, field by field.

4. Check MERGE OUTCOME. It shows which test case stays active, how many are archived, and whether an active test run includes them.

5. Click Merge duplicates. A confirmation dialog shows which test case is kept and which are archived.

6. Click Merge test cases.

To bring content from the archived test cases into the one you keep, click Improve instead of Merge duplicates. The button names the test case you keep, such as Improve FHB-88. The Review merge panel shows the merged test case. Under Proposed carry-over, select the content to add, then click Confirm merge.

Extract a step group

Resolve a Refactor finding by turning the shared steps into one step group. Nothing is archived.

1. Open the finding. It shows the proposed step group and, for each test case, which steps it replaces.

2. (Optional) Click Edit to change the step group name or its steps.

3. Check REFACTOR OUTCOME. It shows the name of the new step group and how many test cases it changes.

4. Click Create step group. Arcus creates the step group and replaces the shared steps in every test case in the finding.

The new step group appears under Step Groups. Edit it there to update the steps in every test case that uses it. See Step Groups.