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 to any depth.
Creating folders
- In the Test Cases view, look at the folder sidebar on the left.
- Click the Create Folder button () at the top of the sidebar.
- Enter a folder name and click Create.
- To create a nested subfolder, right-click (or use the context menu) on an existing folder and select Create Subfolder.
Moving test cases between folders
You can move test cases to a different folder in several ways:
- Single test case — Open the test case detail view and change the Folder field on the Details tab.
- Bulk move — Select multiple test cases using checkboxes in the table, then use the Move to Folder bulk action.
Renaming and deleting folders
Right-click a folder (or use the menu) to rename or delete it.
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 by title or ID
Use the search bar () at the top of the test case table to search by test case title or Test Case ID. The search is case-insensitive and matches partial text. For example, searching "login" will match "Login - Valid credentials", "User Login Flow", and "Admin Login Page". Searching "TC-42" will find the specific test case with that ID.
Filter by fields
Click the Filter button () to open the filter panel. You can filter by:
- Priority — Critical, High, Medium, Low
- Status — Draft, Active, Deprecated
- Type — Functional, Regression, Smoke, Integration, Performance, Security, Usability, Acceptance, Other
- Labels — Select one or more labels to filter by tag
- Folder — Select a folder from the sidebar to view only test cases within that folder and its subfolders
- Automation Status — Not Automated, To Be Automated, Automated
Filters can be combined. For example, you can filter for Priority = Critical + Type = Smoke + Status = Active to see only your critical smoke tests that are ready for execution.
Pagination
The test case table is paginated for performance. The default page size is 25 test cases per page. You can change the page size to 10, 25, 50, or 100 using the dropdown at the bottom of the table. Use the navigation controls 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.
See also
- Test Cases — Overview, creation, detail tabs, and field reference
- Test Steps — Define step-by-step execution procedures
- Import & Export — CSV import and export
- Bulk Operations — Clone and bulk update test cases
- History & Attachments — Execution history, change tracking, and file attachments
- Best Practices — Guidelines and FAQ