> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating and Editing Test Cases

> Create test cases in TestDino using forms, quick entry mode, or suite context menus. Edit inline for quick changes or open full-screen for detailed updates.

export const VideoSchema = ({name, description, thumbnailUrl, uploadDate, duration, contentUrl, embedUrl}) => {
  const schema = {
    "@context": "https://schema.org",
    "@type": "VideoObject",
    name,
    description,
    thumbnailUrl,
    uploadDate,
    ...duration ? {
      duration
    } : {},
    ...contentUrl ? {
      contentUrl
    } : {},
    ...embedUrl ? {
      embedUrl
    } : {},
    publisher: {
      "@type": "Organization",
      name: "TestDino",
      logo: {
        "@type": "ImageObject",
        url: "https://docs.testdino.com/logo/light.svg"
      }
    }
  };
  return <script type="application/ld+json" dangerouslySetInnerHTML={{
    __html: JSON.stringify(schema)
  }} />;
};

<VideoSchema name="AI-Powered Manual Test Case Creation with TestDino MCP" description="Create manual test cases in TestDino using the MCP server with AI assistants like Claude or Cursor." thumbnailUrl="https://i.ytimg.com/vi/uxCpfPdgZPw/maxresdefault.jpg" uploadDate="2025-12-16T00:00:00+00:00" contentUrl="https://www.youtube.com/watch?v=uxCpfPdgZPw" embedUrl="https://www.youtube.com/embed/uxCpfPdgZPw" />

The Test Case Management tab provides multiple ways to create test cases. Each method supports a different workflow, from full detailed entry to quick creation within a suite.

<iframe className="w-full rounded-lg h-[500px]" src="https://www.youtube.com/embed/uxCpfPdgZPw" title="AI-Powered Manual Test Case Creation with TestDino MCP" frameBorder="0" allow="accelerometer; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; embedding" referrerPolicy="strict-origin-when-cross-origin" allowFullScreen />

## Three Creation Methods

You can create a new test case in three different ways, depending on the level of detail you want to add upfront.

### 1. New Test Case

* Click the **New Test Case** button in the top navigation bar.

* This opens the complete "Create Test Case" form with all properties: title, description, steps, and classifications.

<video controls loop preload="metadata" aria-label="Creating a test case in the full Create Test Case form with title, description, steps, and classifications" src="https://tdstorageus.blob.core.windows.net/public/docs/_unlisted/test-management/test-case/creating-editing/new-test-case.mp4" />

### 2. Quick Test Creation Within Suite

* At the bottom of the test case list within any suite, find the row labeled "**Create quick test**".

* Type a title into the input field and press Enter.

* This instantly creates a new test case in that suite with only a title. You can then double-click it to edit and add more details later.

<video controls loop preload="metadata" aria-label="Quick test creation adding a title-only test case at the bottom of a suite list" src="https://tdstorageus.blob.core.windows.net/public/docs/_unlisted/test-management/test-case/creating-editing/quick-test-creation-within-suite.mp4" />

### 3. From Suite Menu

* Click the action menu (⋮) on any suite.

* Select **Add Test Case**.

* This opens the full creation form, but the **Test Suite** field is pre-selected with the suite you chose.

<video controls loop preload="metadata" aria-label="Adding a test case from the suite action menu with the suite pre-selected" src="https://tdstorageus.blob.core.windows.net/public/docs/_unlisted/test-management/test-case/creating-editing/from-suite-menu.mp4" />

<Callout icon="triangle-exclamation" color="#F59E0B">
  **Warning**

  A test case must be assigned to a suite. This is a **required field**. If you import test cases without specifying a suite, they are automatically placed in the **"Unassigned"** suite.
</Callout>

## Inline Editing

<video controls loop preload="metadata" aria-label="Inline editing a test case in sheet view and full-screen view" src="https://tdstorageus.blob.core.windows.net/public/docs/_unlisted/test-management/test-case/creating-editing/inline-editing.mp4" />

An individual test case can be viewed in two modes: **Sheet View** and **Full-Screen View.**

### 1. Sheet View (Default)

Clicking on a test case once opens it in a **side sheet** on the right side of the screen.

This sheet displays all test case information in a scrollable panel. Two quick action buttons appear at the top:

* **Full Screen:** Expands the test case to occupy the full screen.

* **Print:** Exports the test case details to a printable format (PDF), including all core information, steps, and metadata.

#### Editing in Sheet View

You can edit any field directly in the sheet:

* Single click to open the sheet.

* Double-click on any editable field to modify it or use the pencil icon next to editable fields.

* After editing, confirm changes with the tick (✓) icon or discard with the cross (×) icon.

This applies to text fields, dropdowns, and tags. All updates are saved instantly upon confirmation.

### 2. Full-Screen View

The full-screen mode provides a detailed layout suitable for reviews, documentation exports, or test audits.

Click the full-screen icon in the top-right corner of the sheet to open the test case in a wider layout. Editing options remain the same as in sheet view.

## Adding Test Steps

When creating or editing a test case, switch between **Classic** and **Gherkin** step formats using the tabs in the step editor.

<Tabs>
  <Tab title="Classic">
    Each step has three fields:

    1. **Action** - What action to perform
    2. **Test Data** - Input data (optional)
    3. **Expected Result** - What should happen

    Click **Add Step** to append additional steps.
  </Tab>

  <Tab title="Gherkin (BDD)">
    Write behavior-driven steps using structured keywords:

    1. **Given** - Describe the initial context
    2. **When** - Describe the action or event
    3. **Then** - Describe the expected outcome
    4. **And / But** - Add conditions or exceptions

    Each step maps to one keyword and its description.
  </Tab>
</Tabs>

See [Test Case Structure](/test-management/test-case/structure#test-steps) for the full field reference.

## Related

<CardGroup cols={2}>
  <Card title="Test Case Structure" icon="flask" href="/test-management/test-case/structure">
    Fields, steps, custom fields, and attachments
  </Card>

  <Card title="Organizing at Scale" icon="layer-group" href="/test-management/test-case/organizing-at-scale">
    Suites, tags, and bulk operations
  </Card>

  <Card title="Import & Export" icon="file-import" href="/test-management/import-export">
    Bulk import from CSV or TestRail
  </Card>

  <Card title="MCP Integration" icon="plug" href="/mcp/overview">
    Create and manage test cases with AI
  </Card>
</CardGroup>
