Modules and Features

Modules represent the functional areas, components, or features of the application you are testing. They give you a way to organize test cases by what part of your product they cover, making it easy to see coverage gaps and focus testing efforts.

What Are Modules?

A module maps to a distinct area of your application. For example:

• Authentication -- Login, registration, password reset, OAuth.
• Shopping Cart -- Add to cart, remove items, update quantities, checkout.
• User Profile -- Profile editing, avatar upload, notification settings.
• Admin Dashboard -- User management, system settings, audit logs.
• Payments -- Credit card processing, refunds, invoicing.

Modules help answer the question: "How well tested is each part of our application?"

Create a Module

1. Open your project.
2. Click Modules in the project navigation.
3. Click + New Module.
4. Fill in the details:
   • Name -- The name of the feature or component (e.g., "User Authentication").
   • Description -- What this module covers in your application.
   • Parent Module -- (Optional) Select a parent to create a nested hierarchy.
5. Click Create Module.

Build a Module Hierarchy

You can nest modules to mirror the structure of your application:

1. When creating a module, select a Parent Module from the dropdown.
2. The new module appears as a child of the parent.

Example hierarchy:

E-Commerce Platform
  |-- User Management
  |     |-- Authentication
  |     |-- User Profile
  |     |-- Roles & Permissions
  |-- Product Catalog
  |     |-- Search
  |     |-- Product Details
  |     |-- Categories
  |-- Shopping Cart
  |     |-- Cart Management
  |     |-- Checkout
  |-- Payments
        |-- Credit Card
        |-- PayPal
        |-- Refunds

tip

Keep your module hierarchy aligned with how your development team thinks about the product. If developers talk about "the checkout flow" or "the admin panel," those are good module names.

Organize Test Cases by Module

Assign a Module During Test Case Creation

When creating or editing a test case, select the relevant module from the Module dropdown. This associates the test case with that area of your application.

Move Test Cases Between Modules

1. Open the test case.
2. Click Edit.
3. Change the Module field.
4. Click Save.

You can also use bulk operations to move multiple test cases at once.

Track Coverage by Module

Each module displays coverage metrics:

Metric	Description
Total test cases	Number of test cases assigned to this module.
Approved test cases	How many are in the Approved lifecycle status.
Last execution pass rate	The pass rate from the most recent test run that included tests from this module.
Untested	Test cases that have never been executed.

Module Coverage View

1. Go to Modules.
2. The overview page shows all modules with their coverage status:
   • Well covered -- High number of approved test cases with good pass rates.
   • Needs attention -- Few test cases or declining pass rates.
   • Not covered -- No test cases assigned.

info

Modules with no test cases are highlighted so you can quickly identify areas of your application that have no testing coverage.

Feature Tracking

Within each module, you can track individual features:

1. Open a module.
2. View the list of test cases grouped by tags or sub-modules.
3. See which features have passing tests, failing tests, or no tests at all.

This gives you a feature-level view of quality, which is useful for:

• Release planning -- Decide which features are ready for release based on test coverage.
• Risk assessment -- Identify high-risk areas with low coverage or recent failures.
• Sprint retrospectives -- Review which modules received testing attention and which did not.

Reorganize Modules

Rename a Module

1. Go to Modules.
2. Click on the module you want to rename.
3. Click Edit (or the pencil icon).
4. Update the name.
5. Click Save.

Move a Module

To change a module's parent:

1. Open the module.
2. Click Edit.
3. Change the Parent Module field.
4. Click Save.

You can also drag and drop modules in the hierarchy view to reorder them.

Archive a Module

If a module is no longer relevant (e.g., a feature was removed):

1. Open the module.
2. Click Archive.
3. Confirm the action.

Archived modules are hidden from the default view but can be restored. Test cases within an archived module are not deleted.

Best Practices

• Mirror your product structure -- Your module hierarchy should reflect how your application is organized. This makes it intuitive for your team to find and maintain tests.
• Review coverage gaps monthly -- Check the module coverage view regularly to identify areas that need more test cases.
• Keep modules up to date -- When features are added or removed from your product, update the module structure accordingly.
• Use modules with requirements -- Combine module-based organization with requirements traceability for a complete picture of what is tested and what is not.