Manage test cases
A test case defines one scenario to test, with its preconditions, steps, and expected results. The Test Cases page lists every test case in the project, organized in folders. Each folder shows how many test cases it holds, including those in its subfolders.
For what each part of a test case’s own page shows, see Tests overview. Duplicate test cases are in Deduplication.

Folders
Section titled “Folders”The folder panel on the left starts with All test cases, then lists your folders. Archived at the bottom holds test cases archived by a deduplication merge. Use Search folders to find a folder by name.
Create a folder
Section titled “Create a folder”-
Open Test Cases in the left navigation.
-
At the top of the folder panel, click the new folder icon.
-
In Name of your Folder, enter a name and click the plus icon (+).

Change a folder
Section titled “Change a folder”Hover over a folder and click its ellipsis icon (⋮). The menu offers Create Testcase, Add Subfolder, Clone Folder, Move Folder, Rename, and Delete Folder.

Create a test case
Section titled “Create a test case”-
Open Test Cases in the left navigation.
-
Click Create, or press
C. To create the test case in a folder, click the folder’s ellipsis icon (⋮) and click Create Testcase instead. -
(Optional) Click the template chip and select Documentation or Steps. Documentation is selected by default.
-
If no folder is shown, click Select a Folder, select a folder in Add Folder Location for Test Case, and click Select Folder. A test case can’t be created without a folder. To make a folder here, click Create Folder.

-
Enter a title and, optionally, a description.
-
(Optional) Change the status, priority, test case type, owner, or reviewer with the chips at the bottom of the dialog.
-
Click Create. The test case opens.

The template sets the shape of the manual steps:
- Documentation: free-text PRECONDITIONS, STEPS, and EXPECTED RESULTS. Use it for short tests with one expected result. To reuse steps from a step group, type
/step-groupon its own line in STEPS. - Steps: a table with an expected result for every step. Use it when each action needs its own check. To reuse steps from a step group, click Add Step Group below the table.
A step group has a format too, and goes only into test cases of the same format. See Step groups.
You can change the template later in the right panel. To have Arcus write test cases for you, click Create with AI. See Generate test cases.
Open and edit a test case
Section titled “Open and edit a test case”-
Click the test case’s name in the list. The quick view opens beside the list.

-
Click the edit icon in the quick view. The test case page opens. You can also click the ellipsis icon (⋯) on the test case’s row and click Edit.
-
Make your changes. Arcus saves them automatically.
To rename a test case from the list, hover over its name and click the pencil icon.
Test case properties
Section titled “Test case properties”A test case’s properties sit in the right panel of its page: Template Type, Status, Priority, Test Case Type, Owner, Reviewer, Automation Type, labels, attachments, linked requirements, and your project’s custom fields. See Right panel.
The values offered for Status, Priority, Test Case Type, and Automation Type are set under Settings > Manage Properties, so they differ between projects.
Find test cases
Section titled “Find test cases”- Search tests (
⌘+F): find test cases by name. - Filter by (
⌘+Shift+F): filter on Folder, Status, Priority, Automation Type, Test Case Type, Label, Owner, or Created at. - Sort: order the list by Order, Title, or Priority, in Default or Reverse direction.
- View: under View properties, show or hide the Labels, Test Case Type, Test Case Status, Automation Type, and Owner columns.


Filter the list
Section titled “Filter the list”-
Click Filter by and select a property, such as Status. A chip for it appears in the toolbar.

-
Click the plus icon (+) on the chip, select the values, and click Apply filter. The list narrows, and the toolbar shows how many test cases match.
-
(Optional) Add more properties the same way.
To remove one filter, click the close icon (×) on its chip. To remove all of them, click Clear All.
Reorder test cases
Section titled “Reorder test cases”Drag a test case by its drag handle to a new position in its folder. The new order also applies in the test runs that include the test case.
Clone a test case
Section titled “Clone a test case”Cloning copies the test case as it is now. Later changes to the original don’t reach the copy.
-
Click the ellipsis icon (⋯) on the test case’s row and click Clone. The Clone Test Case dialog opens, with the title followed by “Clone”.

-
(Optional) Change the Test Case Title.
-
Select the Target Project and Target Folder.
-
Click Clone. The message “Test Case Cloned” appears.

Delete a test case
Section titled “Delete a test case”-
Click the ellipsis icon (⋯) on the test case’s row and click Delete.
-
In Delete Test Case?, click Delete Test Case. Deleting is permanent.

To delete several test cases at once, use bulk actions.
Bulk actions
Section titled “Bulk actions”-
Select the checkbox on each test case you want to change. A bar at the bottom of the page shows how many are selected.


-
Click Command, or press
⌘+K. The Bulk Update Test Cases list opens.
-
Select an action, then follow its prompt.
The actions are Change Folder, Change Priority, Change Status, Change Test Case Type, Change Automation Type, Change Labels, Change Owner, Change Reviewer, and Delete Test Cases, plus one Change action for each custom field. With Review Management on, Submit for Review is listed too. The bar also offers Export.
Comments
Section titled “Comments”Comments sit at the bottom of a test case’s page, under COMMENTS.
-
Open the test case and click in the comment box.
-
Type your comment. Type
@to mention a teammate, or/for text functions. -
Click Add Comment.
Under each comment, click the reply icon to answer it, or the emoji icon to react. The ellipsis icon (⋯) offers Copy link, Edit, and Delete.
Review steps are logged here too. See Review test cases.
Review test cases
Section titled “Review test cases”With Review Management on, a test case reaches Ready only after a reviewer approves it. The test case goes from Draft to In Review, and the reviewer either marks it Ready or sends it back as Rework. Review Management is set per project, so turn it on in each project that needs it.
Turn on Review Management
Section titled “Turn on Review Management”-
Open the project switcher at the top of the left navigation and click Project Settings.
-
On Overview, turn on Review Management. The message “Review Management has been enabled for this project” appears.


While it’s on, the Status list on a test case reads “Review Management is turned on.”, and you can’t select Ready or In Review there. A test case reaches those statuses only through review. To turn review off, turn off Review Management on the same page. Turning it off doesn’t change any test case’s status. A test case in In Review stays there, Mark as Ready and Mark as Rework no longer appear, and you change its status from the Status list.
Submit a test case for review
Section titled “Submit a test case for review”-
Open a test case you own in Draft or Rework. Submit for Review appears in the header, next to the version history icon. If the test case is in another status, set Status to Draft in the right panel first.
-
Click Submit for Review. The Submit for Review dialog opens.
-
Under Reviewer, select a teammate. You can select yourself.

-
Click Submit for Review. The status changes to In Review, and the reviewer appears in the right panel.

When you resubmit a test case after rework, the dialog is prefilled with the earlier reviewer. Change it if someone else should review this time.
To submit several test cases at once, select them in the Test Cases list, click Command, and click Submit for Review. See Bulk actions.
Review a submitted test case
Section titled “Review a submitted test case”The Dashboard lists your reviews under Test Case Review Status: Awaiting My Review holds the test cases sent to you, and Submitted for Review holds the ones you sent.
-
Open the test case and read its steps and expected results. Mark as Ready and Mark as Rework appear only to the assigned reviewer.
-
Approve it or send it back:
-
To approve it, click Mark as Ready. The status changes to Ready.
-
To send it back, click Mark as Rework, write what needs to change, and click Mark as Rework. The comment is required. The status changes to Rework.

-
Each review step is logged under COMMENTS with the status change, such as In Review → Rework, and the reviewer’s comment.
Review statuses
Section titled “Review statuses”| Status | Header action | Next status |
|---|---|---|
| Draft | Submit for Review | In Review |
| In Review | Mark as Ready or Mark as Rework | Ready or Rework |
| Rework | Submit for Review | In Review |
| Ready | None | Obsolete |
A test case in any status can be set to Obsolete from the Status list. To see where a test case can go next, open the Status list and click View Workflow at the bottom of the list. Test Case Workflow shows the current status, the statuses it can move to, and the whole workflow.

Versions
Section titled “Versions”Arcus keeps earlier versions of each test case. You can see who changed it and when, compare an earlier version with the current one, and restore it.
A new version is saved when you change the test case’s content or properties, such as its title, steps, status, priority, reviewer, folder, or labels. Arcus groups changes made close together into one version, so a new version can take a while to appear in Version History.
View version history
Section titled “View version history”Click the version history icon next to the status chip in the test case’s header. The Version History panel lists Current Version first, then the earlier versions, each with its date and time and who changed it.
Compare and restore a version
Section titled “Compare and restore a version”-
In Version History, hover over an earlier version and click its ellipsis icon (⋯).

-
Click Compare With Current. Comparison Mode opens, with the current version on the left and the earlier version on the right. Changed values are highlighted.
-
(Optional) To return the test case to the earlier version, click Restore to this Version, then click Make Current Version to confirm. “Version restored successfully” appears, Comparison Mode closes, and the restore is saved as a new version named “Restored from version” with the date and time. If the restore changes the steps, the test case’s results in open test runs are reset.
-
Click the close icon (×) to leave Comparison Mode.

You can compare an earlier version only with the current version, not with another earlier version.
Every plan can open Version History. Comparing, restoring, and naming versions need Versioning on your plan. Without it, clicking Compare With Current or Name This Version shows an upgrade prompt.
Name a version
Section titled “Name a version”-
In Version History, hover over a version, click its ellipsis icon (⋯), and click Name This Version.
-
In Version Name, enter a name for the version.
-
Click Continue.
In Version History, the name appears in bold above the version’s date and time. In Comparison Mode, the earlier version’s label reads Version - followed by the name. To change the name, open the ellipsis menu and click Rename Version.
Run history
Section titled “Run history”Every run of a test case, including Copilot sessions, is listed on the Run history tab of its page. See Run history tab.
Import and export
Section titled “Import and export”Click the more options icon (⋯) at the top right of the Test Cases page:
- Import opens Project Settings > Import. See Import from CSV.
- Export opens the Export test cases dialog. It shows how many test cases will be exported as an XLSX file, and which filters apply. Click Export; the button shows the same count.


Was this page helpful?
Thanks for the feedback.