# 3.1.2 Adding Test Case

On the dash board click on the test cases.

![](/files/-Mc9jUXQO4X8N-hfQyhx)

If your product has client select the client

Select the functionality which you want to add test cases.

Click on the “**New Test Case Button**”.

![](/files/-Mc9jUXRkJU2umQgPRPn)

Here you can see two parts

* Functionality definition
* Test case definition

In the test case definition part you need to fill the below fields

* Enter the test case reference
* Select the test case type
* Select severity
* Select Priority
* Enter the estimated time
* Select the weightage
* Test case levels are optional

After fill the form you can save the test case or draft the test case.

Click on the **Draft** button.

![](/files/-Mc9jUXSAhMqRD0mvWDd)

Draft means you are making the test case for review purpose. Whenever you click on the draft button test case status is set to the draft state.

![](/files/-Mc9jUXT4LssZG-h5VXZ)

Now manager/Lean will start reviewing the test case

Click on the edit icon.

![Inserting image...](/files/-Mc9jUXUZ_x9-6dMzRfl)

Click on the For review button. Now your test case is in review state.

![](/files/-Mc9jUXVq1KtRlUuhOTN)

After reviewing the test case again click on the edit icon

Then save the test case. Your test case ready to execute.&#x20;

![](/files/-Mc9jUXWMfoV6xa0W6EW)

**Note:** Only ready state test case is you able to execute remaining you test cases you cannot.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.qatts.com/v-3.0/get-to-start-automating-web-applications/manual-test-script-development/untitled.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
