Folders & Organization

Organize test cases into hierarchical folders and use search and filtering to find what you need.

Folder Organization

Folders let you organize test cases into a hierarchical tree structure that mirrors your application's architecture, feature areas, or any logical grouping that makes sense for your team. You can nest folders up to 3 levels deep.

Creating folders

In the Test Cases view, look at the folder sidebar on the left.
Open the menu () on the root workspace row at the top of the sidebar and choose Create Folder. A project with no folders yet shows a Create New Folder button instead.
Enter a folder name and confirm.
To create a nested subfolder, click the menu button on an existing folder row and choose Add Folder. The item is disabled at the third level, since folders cannot nest deeper than 3.

Folders nest three levels deep, and no further. Creating a folder under a third-level folder is rejected with Maximum folder hierarchy depth is 3. The same limit applies when you drag or Move to… a folder: if the folder you are moving has subfolders of its own, the whole subtree must still fit within 3 levels at the destination, otherwise the move is rejected with Maximum folder hierarchy depth exceeded. A deeper Folder path in a CSV or Excel import fails that row with Folder depth exceeds maximum of 3 levels.

Moving test cases between folders

There is no Move to Folder bulk action in the toolbar, and Folder cannot be changed through Bulk Edit. Test cases are moved in one of two ways:

Drag and drop — the way to move many at once. Tick the test cases you want in the table, then drag any one of the selected rows onto the target folder in the left sidebar. Dragging an unselected row moves just that row.
Single test case — Open the test case detail view and change the Folder field on the Details tab.

Folders themselves can also be reorganised: drag a folder onto another folder, or use Move to… in the folder's menu.

Renaming and deleting folders

Click the menu button on a folder row to open its menu: Rename Folder, Move to…, Add Folder, a create-test-case item, and Delete.

Deleting a folder does not delete the test cases inside it. The test cases are moved to the root level (no folder). However, any subfolders within the deleted folder are also removed.

Recommended folder structures

Here are some common patterns teams use to organize their test suites:

Strategy	Example structure	Best for
By feature area	`Authentication / Login`, `Authentication / Registration`, `Payments / Checkout`, `Payments / Refunds`	Product-oriented teams; maps directly to product features
By module / service	`API / Users`, `API / Orders`, `Frontend / Dashboard`, `Frontend / Settings`	Engineering-oriented teams; maps to codebase modules
By test type	`Smoke Tests`, `Regression / Core`, `Regression / Edge Cases`, `Performance`	Teams that run different test suites at different stages of the pipeline
Hybrid	`Authentication / Smoke`, `Authentication / Regression`, `Payments / Smoke`	Large teams that need both feature-level and type-level organization

Search & Filter

As your test suite grows, finding specific test cases quickly becomes essential. TestKase provides powerful search and filtering capabilities to help you locate exactly what you need.

Search

Use the search bar () at the top of the test case table. The search is case-insensitive, matches partial text, and looks across more than the title:

Test Case ID — e.g. TEST-42
Title
Summary
Labels, Features and Environment — any one value in the list matches
Custom field values — the stored value of any custom field
Created date — matches the date written as YYYY-MM-DD

A test case is returned if any of these match, so searching "login" will match "Login - Valid credentials", a case whose summary mentions logging in, and a case labelled login.

Search only runs at 3 characters or more. Typing one or two characters leaves the table showing the unfiltered list — nothing is sent to the server and no "no results" message appears. Type a third character to see results.

Filter by fields

Click the Filter button () to open the filter panel. The panel is built from your project's field configuration, so it lists far more than a fixed set — every visible list field in the project is filterable, including your custom fields:

Filter group	What appears
List fields	Every visible single-select and multi-select field that has options configured — Priority, Status, Automated, Environment, Features, Labels, Platform, and any `SINGLE_LIST` / `MULTI_LIST` custom field.
People	Owner, Created By, Updated By — pick one or more project members.
Automation ID	Type one or more 5-digit Automation IDs as chips.
Linked issues	Requirement Issues and Defect Issues — filter by Linked / Not Linked, or search a specific issue ID.
Date ranges	Created In-between and Updated In-between, plus an in-between range for every visible `CALENDAR` custom field.

Title, Folder and the Custom Fields container itself are excluded from the filter panel. Hiding a field on Field Configuration also removes it from this panel, and Archive is hidden from the Status filter unless you are on the Archive view.

A list field appears in the filter panel only once it has at least one option configured on Field Value. Platform, Labels and any new list-type custom field start with an empty option list, so they are missing from the filter panel until you add values there.

Filters can be combined. For example, you can filter for Priority = Blocker + Status = Approved to see only your top-priority test cases that are ready for execution.

Folder is not a filter in this panel — selecting a folder in the sidebar filters the table to that folder and its subfolders instead.

Pagination

The test case table shows 20 test cases per page. The page size is fixed — there is no page-size selector. Use the arrows and the page controls at the bottom of the table to move between pages.

Selecting a folder in the sidebar automatically filters the table to show only test cases in that folder (and its subfolders). Combine this with search and field filters for precise results.