> For the complete documentation index, see [llms.txt](https://docs.testfirst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testfirst.com/testfirst-editor/write-manual-test-cases.md).

# Write Manual Test Cases

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><p>Create step-by-step manual tests with expected results.</p><ul><li>Ideal for exploratory or non-automatable scenarios</li><li>Simple and structured format</li><li>Useful for QA validation flows</li></ul></td><td><a href="https://2622859358-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErSaU4WjIuLC7zfVEh8L%2Fuploads%2FhjqIp8iapnvPrc3anN39%2FVisual%20Frame.png?alt=media&amp;token=795035f9-e627-4bdf-bcc5-ffa856f41dc6">Visual Frame.png</a></td></tr></tbody></table>

Manual test cases define **step-by-step actions and expected results** that a tester performs instead of an automated test.

They are useful when:

* The test cannot be automated
* Exploratory testing is required
* Human validation is needed

### When to Use Manual Tests

Use manual test cases when:

* The scenario involves **visual validation**
* The flow is **too complex or dynamic to automate**
* The test is **temporary or one-time**

***

## How to Create a Manual Test Case

### Option 1 - From Test Case Library

* Go to **Test Case Library**
* Right-click any node (**Project**, **Suite**, **Section**, or **Subsection**)
* Click **Add Manual Test Case**
* **Open** the new test case when prompted
* **Write** the preconditions and steps in the table, and add a reference if needed
* Click **Save**

### Option 2 - From Editor (Mini Library)

* Open the **TestFirst Editor**
* Open **Library** from the left-side navigation bar
* Right-click any node or use the **More actions** button\
  ![](https://2622859358-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErSaU4WjIuLC7zfVEh8L%2Fuploads%2Fu0d4sO60GApmigzeFLdV%2FScreenshot%202026-03-26%20004110.png?alt=media\&token=16e7767e-fd0c-4d80-8fa7-02afab2c7ccc)
* Click **Add Manual Test Case**
* **Enter** the test case **name**
* **Open** the new test case
* **Write** the preconditions and steps in the table, and add a reference if needed
* Click **Save**

### Option 3 - Write First, Then Save as Manual

1. Open the **TestFirst Editor**
2. **Record steps** or **write the test case in Gherkin**
3. Set the test type to **Manual**\
   ![](https://2622859358-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErSaU4WjIuLC7zfVEh8L%2Fuploads%2FaYLaYsKHi2MvCAbFvBGH%2FScreenshot%202026-03-25%20234021.png?alt=media\&token=dad5158d-b160-4033-b5d6-b87be0a65051)
4. Click **Convert to manual** in the confirmation
5. Click **Save**

***

### Writing Manual Test Steps

Manual test cases are written in a **structured table format**.

* **Action** → What the tester should do
* **Expected Result** → What should happen

#### Example

| Action                            | Expected Result                         |
| --------------------------------- | --------------------------------------- |
| Open the login page               | The login page is displayed             |
| Enter valid username and password | The input is accepted                   |
| Click "Sign In"                   | The user is redirected to the dashboard |

***

## Completing the Manual Test Case

After writing your steps:

1. Review the test case
2. Change the **Status** <i class="fa-arrow-right">:arrow-right:</i> **Ready for Testing**
3. Click **Save**

{% hint style="info" %}
Saving is required after updating the status.
{% endhint %}

## Tips for Writing Manual Test Cases

* Keep steps **clear and simple**
* Make expected results **verifiable**
* Avoid combining multiple actions in one step
* Use consistent wording across tests
