# Organise your Test Cases

Organising your test cases effectively is key to smooth testing and better project management. SimplifyQA makes this easy with features like mapping test cases to modules and submodules, as well as a handy tree view for navigation.

### Why Organise Test Cases?

1. **Enhanced Clarity:** Maintain a structured hierarchy for better visibility and easy access.
2. **Improved Navigation:** Quickly locate specific test cases using the tree view structure.

### How to Organise your Test Cases

#### 1. Map Test Cases to Modules and Submodules

Mapping test cases to relevant modules and submodules helps categorise them based on application functionality.

**Steps to Map Test Cases:**

* **Create Modules and Submodules:**
  * Navigate to the Test Case section in SimplifyQA from the left-hand panel.
  * Click "Add Module" from the left-hand section to create a new module and provide a meaningful name (e.g., "Login Module").
  * Add submodules under the module as needed (e.g., "Forgot Password", "User Authentication").

<figure><img src="/files/aPcDVcGD8hwFPfxLGVwy" alt="" width="309"><figcaption></figcaption></figure>

* **Assign Test Cases to Modules:**
  * Go to the Test Cases section.
  * Open the desired test case.
  * Select the Module and Submodule from the dropdown menus within the test case details.
  * Save your changes.

<figure><img src="/files/BOpAo6dsfn0Ufq8NvoFj" alt="" width="475"><figcaption></figcaption></figure>

#### 2. Navigate Test Cases using the Tree View

The tree view provides a hierarchical representation of your modules, submodules, and associated test cases.

**Steps to Use the Tree View:**

* Open the Test Cases section.
* The tree view will display all modules and submodules in a collapsible structure.
* Click on a module or submodule to view the associated test cases in the table on right side.
* Drag and drop test cases from the table into the desired module or submodule in the tree to organise them efficiently.
* You can also rearrange modules and submodules within the tree structure by simply dragging and dropping them to the desired position.

<figure><img src="/files/1ty9NR49nMUG4aU8XLQy" alt="" width="308"><figcaption></figcaption></figure>

#### Benefits of Tree View:

* Quickly locate test cases without searching through lists.
* Provides a clear overview of the module hierarchy and test case distribution.
* Easily navigate between different modules and submodules.

### Best Practices for Organising Test Cases

1. **Use Meaningful Names:** Assign descriptive names to modules, submodules, and test cases to make navigation intuitive.
2. **Adopt a Standard Structure:** Follow a consistent hierarchy for all projects to simplify understanding across teams.
3. **Regularly Update Mappings:** Ensure test cases remain mapped correctly when new modules or submodules are added.

### How Organised Test Cases Help

1. **Faster Test Execution:** Locate and execute test cases quickly during sprints or regression cycles.
2. **Comprehensive Coverage:** Ensure no modules are left untested by tracking test cases linked to each functionality.
3. **Simplified Maintenance:** Update or modify test cases with ease by navigating directly to the relevant module.

### Frequently Asked Questions (FAQs)

<details>

<summary><strong>Can I assign a test case to multiple modules or submodules?</strong></summary>

No, a test case can only be mapped to one module and submodule to maintain clarity and avoid duplication.

</details>


---

# 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.simplifyqa.ai/introduction-to-test-management-in-simplifyqa/organise-your-test-cases.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.