Test cases and folders
The tree on the left of Automate holds every test case of the project. This page covers creating test cases and templates, folders and modules, finding cases, and archiving and restoring them.
In short
On this page you can
- Create a test case with New Test Case and name it in the editor header.
- Turn a test case into a reusable template with the kind chip.
- Group test cases in folders; top-level folders become modules.
- Filter the tree by name, ID, tags or last-run status.
- Archive a test case or folder and restore it later.
How to use it
- Select the folder the test case belongs in.
- Click New Test Case, type the name at the top of the editor and click Save.
- Drag test cases between folders to reorganise them.
- Use the filter icon to find cases by name,
#ID, tag or status. - Delete what you no longer need: it moves to the Archive and can be restored.
Create a test case#
Choose where it goes
Click a folder in the tree. If you click a test case instead, the new one is created next to it, in the same folder. With nothing selected it goes directly under the project root.
Click New Test Case
Click New Test Case at the top of the tree. The test case is created at once (“Test Case added successfully”) and opens in the editor, unnamed, with the name field focused.
Name it
Type the name in the header of the editor. Name it after the user goal:
Login with an expired password shows an error. Pressing Enter leaves the field; pasted line breaks become spaces. While the name is empty the field has a red border and Save stays disabled.Check environment and start page (web)
In Test Case Detail on the right, check the environment chip and the start page URL. A new test case starts on the environment you used last in this browser, otherwise TEST. See Environment and start page.
Add steps and save
Record or add steps, then click Save.
The test case shows in the tree under its name, with a Never run icon until a pipeline runs it.
Until you name it, the tree shows the case as “Unnamed test case #id”. You do not write the description yourself: the AI writes it from the steps (see AI descriptions).
Each new test case counts against your licence
Your company’s licence can limit how many test cases you create. Creating a test case with New Test Case adds one to your company’s automated test case counter, and archiving or deleting it does not take it back. An Admin sees the licence in Company Settings › Billing. When the limit is reached you see “Company license limit has been reached. The maximum allowed usage for this operation has been exceeded.”
Copying a test case#
There is no copy or duplicate for test cases. To reuse steps, put them in a template and add the template to the new test case, or use Expand Scenarios to create variations. An AI assistant connected through MCP can also write a new case from an existing one.
Test case or template#
The chip at the left of the editor header says what the case is. Click it to change.
| Kind | Tooltip | Use it for |
|---|---|---|
| Test case | “Runs on its own and produces a report” | A test of one user goal. Pipelines run it. |
| Template | “A reusable block of steps added inside other test cases” | Login, opening a customer, accepting cookies: steps many tests need. |
Open the case
Open the test case whose steps you want to reuse, for example
Login as standard user.Switch the chip
Click the kind chip (“Test case or template — click to change”) and choose Template.
Save
Click Save.
The tree shows a usage badge next to the case: unused until another test case adds it. It now appears in the Template Test Cases list of every other test case.
- A template is a live reference. Editing its steps changes every test case that uses it, from their next run.
- Folder summaries do not count templates as test cases; they list them separately.
- Loops are blocked. A template cannot add itself or a test case that already calls it.
How to add a template to a test case, and what the caller shows: Add a template. What the badge counts: Template badge.
Folders and modules#
The tree has one root, the project (marked P). Everything else is a folder or a test case.
- Create a folder: select where it goes, then MoreCreate Folder. It is called
new_folder_Nuntil you rename it (“Folder added successfully”). - Rename a folder: double-click its name, type, and press Enter or click away (“Folder 'name' updated successfully”). Esc cancels; an empty name reverts. Up to 255 characters.
- Rename a test case: change the name in the editor header and click Save.
Top-level folders are modules#
Every folder directly under the project root is a module (marked M). A module is one business area, for example Orders. It exists in three places at once: a folder in Automate, a twin folder in Analyze, and a module in the Discover App Map. Renaming it in one place renames it everywhere.
- Module names must be unique in the project and cannot be empty (“A module with this name already exists”).
- When you create a folder at the root, or drag a folder to the root, it becomes a module: ““name” is now a module: its folder in Analyze and its App Map module were created.”
- Folders inside a module are ordinary folders.
Why modules matter
AI test generation can be limited to one module’s pages, and the App Map groups pages and coverage by module. Plan your top-level folders as the business areas of your app, not by sprint or by tester.
Move test cases and folders#
Drag and drop is the only way to move items.
- Drop a test case on a folder to move it there. Drop it on another test case to move it into that case’s folder.
- Drop a folder on the root to make it a module.
- Dropping a module into another folder asks “Make “name” a sub folder?”: it stops being a module, its Analyze twin moves too, and in the App Map its pages join the target module. Only an Admin can do this (“Only an admin can move a module folder under another module, because it removes the module.”).
- The root cannot be moved.
Folders keep their own order. Test cases are always sorted alphabetically inside their folder; there is no manual reordering, so use names to control the order you see.
Find test cases#
Click the filter icon at the right of the tree toolbar. A dot on the icon means a filter is active.
| Filter | How it matches |
|---|---|
| Search... | Part of the name, ignoring case. A number or #123 finds the test case with that ID. |
| Filter By Tags | Include and Exclude tags. |
| Filter By Status (Last Run) | Success, Failed, Running, Disconnected. Test cases that never ran are hidden while a status filter is on. |
A folder stays visible when any test case inside it matches. The tree remembers which folders you had open, per project.
What the tree shows#
- Status icon before each test case: its last pipeline run (Success, Failed, Running, Disconnected, Skipped, Passed with warnings, or Never run). Hover for the date. Dry runs do not change it. See Status icon.
- ×n or unused after a template: how many test cases use it. Hover to see up to 8 of them.
- M in bold blue before a manual test case.
- Options (the ⋮ menu) on a test case or folder: Delete.
Folder summary#
Click a folder and the editor shows “name — Folder summary”; with nothing selected it shows “Project summary”. It answers: are these tests passing, what do they cover, and can they be trusted?
| Part | What it shows |
|---|---|
| Counts | “n test cases”, “n passed”, “n failing”, “n never run”, and “+n templates (not counted)”. |
| Condition coverage | How much of what can be done on the pages these tests touch is covered. Needs an App Map update. See the formula. |
| What it tests | The pages the folder’s test cases use, with their condition coverage, and pages not on map. |
| Gaps and Transitions never tested | Uncovered conditions per page and page-to-page links no test uses. |
| Trust warnings | No proof step, Weak assertion, Broken step, Contains AI steps, Not in any pipeline, Not linked to a requirement, and groups of test cases with the same name (likely duplicates). |
| Copy MCP prompt | Turns the gaps into a ready-made request for an AI assistant connected through MCP. |
A folder that holds only templates shows the templates instead, with “Used in n test cases” or “Not used yet” for each.

Archive and restore#
Deleting a test case or folder in Automate does not delete it for good. It moves to the Archive at the bottom of the tree.
Delete
Open Options (⋮) on the test case or folder and click Delete.
Read the preview
The dialog “Archive "name"?” lists what moves: folders, test cases, manual cases, the pipelines it is removed from (“removed from n pipeline(s); restoring does not put it back”) and who created the items.
Confirm
Click Move to Archive.
“"name" moved to the Archive.” The item disappears from the tree, from pipelines and from test suites. Its requirement links are kept.
| Who can | Rule |
|---|---|
| Archive | You, if you created everything in it; otherwise an Admin (“You can only archive what you created, and this contains items created by other people. An admin can archive it.”). A module: Admins only. |
| Restore | The person who archived it, or an Admin. It goes back to its original folder, or to the root if that folder is gone; a module is re-created. It is not put back into pipelines. |
| Delete for good and Empty archive | Admins only. “This cannot be undone.” |
A template in use cannot be archived
If other test cases use the item as a template step, archiving stops with “Used as a template step in other test cases. Remove those steps first:” and the list of those test cases. Remove the template step from each of them, save, then delete again.
Restoring does not undo pipeline changes: add the test case to its pipelines again in Schedule. There is no other undo in Automate.
Manual test cases#
Manual test cases describe a test for a person to perform: header, severity, category, type, preconditions, description, expected result and steps. Creating new ones is not available yet: MoreNew Manuel Case is disabled with Coming soon. Existing manual cases show with a bold blue M and open in Manual Test Case Detail. They count against the manual test case limit of your licence, which is separate from automated test cases.
If something goes wrong#
Didn’t find your answer?Write to support with your project name and what you see on screen.
info@smartestqa.ai