Test Cases
The complete guide to creating, organizing, and managing test cases in TestKase.
Overview
A test case is the foundational building block of your testing process. It represents a single, verifiable scenario that validates whether a specific piece of functionality works as expected. Each test case captures what to test, how to test it (via ordered steps), and what the expected outcome should be — giving your team a repeatable, auditable blueprint for quality assurance.
In TestKase, test cases live inside projects and can be organized into folders for logical grouping. They are referenced by test cycles during execution, linked to defects when issues are discovered, and included in test plans for broader release-level coverage. Every change to a test case is tracked in a full audit trail, and execution results are preserved across cycles so you can monitor quality trends over time.
Rich detail fields
Priority, type, status, labels, preconditions, automation info, and custom fields
Structured test steps
Ordered steps with expected results, drag-and-drop reordering
Folder organization
Unlimited nested folders to mirror your product architecture
Full traceability
Execution history, change audit trail, defect links, and attachments
Create a Test Case
There are two ways to create a new test case in TestKase. Regardless of which method you use, you will be redirected to the test case detail view immediately after creation so you can fill in additional fields, add test steps, and upload attachments.
From the toolbar
- Navigate to the Test Cases section from the project sidebar.
- Click the Create Test Case button () in the top toolbar above the test case table.
- In the creation dialog, enter a title for your test case. The title is the only required field. Optionally, you can also set the priority, type, and select a folder to place the test case in.
- Click Create. TestKase assigns an auto-generated Test Case ID (e.g.,
TC-123) and redirects you to the detail view.
From within a folder
- In the folder sidebar on the left, navigate to (or create) the folder where you want the test case to live.
- Select the folder so it is highlighted, then click the Create Test Case button in the toolbar.
- The creation dialog will pre-select the current folder. Enter the title and any optional fields, then click Create.
The auto-generated Test Case ID (e.g., TC-1, TC-2, ...) is unique within the project and
cannot be changed. Use it as a stable reference when discussing test cases in pull requests, Jira tickets, or team conversations.
After creation, your test case starts with a Draft status. Update it to Active once you have finished writing steps and filling in all relevant fields. This signals to your team that the test case is ready for execution.
Test Case Detail Tabs
When you open a test case, the detail view presents six tabs that organize all information about that test case. Each tab focuses on a different aspect of the test case lifecycle.
| Tab | Purpose | Key actions |
|---|---|---|
| Details | View and edit all test case fields — title, description, priority, status, type, preconditions, labels, environment, automation ID, automation status, and any custom fields. | Click any field to edit inline. Changes are saved automatically or via a Save button depending on the field. |
| Steps | Manage the ordered list of test steps. Each step has a description of the action to perform and an expected result. | Add, edit, reorder (drag-and-drop), or delete individual steps. |
| Execution Status | Shows the execution history of this test case across all test cycles it has been included in. Each row shows the cycle name, executor, result (Passed, Failed, Blocked, Skipped, Not Run), and timestamp. | Click a cycle name to navigate to the cycle detail view. Use this tab to spot flaky tests or regressions. |
| Defect History | Lists all defects that have been linked to this test case — either created directly from a failed execution or manually linked. | View defect severity, status, and click through to the defect detail page. |
| History | A complete audit trail of every change made to the test case — field updates, step additions/removals, folder moves, and more. Each entry shows what changed, who changed it, and when. | Review the timeline to understand how a test case evolved over time. |
| Attachments | Upload and manage files associated with the test case — screenshots, design specs, test data files, logs, and more. | Upload new files, download existing ones, or delete attachments you no longer need. |
The Execution Status tab is read-only on the test case detail view. To actually execute a test case, add it to a test cycle and run it from there.
Test Case Fields
Every test case has a set of built-in fields that capture its metadata. These fields help you categorize, search, filter, and report on your test cases. Below is a complete reference of all available fields.
| Field | Required | Options / Format | Description |
|---|---|---|---|
| Test Case ID | Auto | TC-1, TC-2, ... | Auto-generated sequential identifier unique within the project. Cannot be edited. |
| Title | Yes | Free text (max 255 characters) | A concise, descriptive name for the test case. Should clearly communicate what is being tested. Example: "Login - Valid credentials redirect to dashboard". |
| Description | No | Rich text | A detailed explanation of the test scenario, its purpose, and any relevant context. Supports markdown formatting. |
| Priority | No | Critical, High, Medium, Low | Indicates how important this test case is. Critical tests should be run in every cycle; low-priority tests may be run less frequently. Helps with prioritizing test execution when time is limited. |
| Status | No | Draft, Active, Deprecated | Draft = still being written. Active = ready for execution. Deprecated = no longer relevant (kept for historical reference). Only Active test cases should be added to test cycles. |
| Type | No | Functional, Regression, Smoke, Integration, Performance, Security, Usability, Acceptance, Other | Classifies the kind of testing this case performs. Useful for filtering — e.g., run only Smoke tests for a quick sanity check before a release. |
| Preconditions | No | Rich text | Describes the state the system must be in before the test steps begin. Examples: "User must be logged in", "Feature flag X must be enabled", "Test data seeded via /api/seed". |
| Labels | No | Comma-separated tags | Free-form tags for cross-cutting categorization. Examples: login, payments, mobile, sprint-42. Labels work across folders, making them ideal for grouping test cases that span multiple feature areas. |
| Environment | No | Free text | The target environment or configuration for this test. Examples: Chrome 120 / Windows 11, iOS 17 / Safari, API Staging. |
| Automation ID | No | Free text | A unique identifier that maps this test case to an automated test in your CI/CD pipeline. Typically matches the test function name or test ID in your automation framework. See the Automation docs for details. |
| Automation Status | No | Not Automated, To Be Automated, Automated | Tracks automation progress. Not Automated = manual only. To Be Automated = planned for automation. Automated = has a corresponding automated test. |
| Folder | No | Folder path | The folder this test case belongs to. Test cases without a folder appear in the root "All Test Cases" view. You can move test cases between folders at any time. |
| Custom Fields | No | Varies (text, dropdown, number, date, checkbox) | If your project has custom fields configured, they appear alongside the built-in fields on the Details tab. Custom fields let you capture domain-specific metadata unique to your organization. |
Fields like Priority, Status, and Type are used as filter criteria in the test case list view. Filling them in consistently makes it much easier to find and organize test cases as your suite grows.
Next Steps
- Test Steps — Define step-by-step execution procedures
- Folders & Organization — Organize test cases with folders, search, and filters
- 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