Skip to main content

​
Modules & Tags

Modules and Tags are two ways to organise your test cases within a project. Modules are mandatory groupings — every test case belongs to one. Tags are optional labels you can apply for additional categorisation.

​
Modules

​
What is a module?

A Module represents a feature area or logical section of your application. Every test case must belong to a module. Modules appear in the left sidebar of the Test Cases page, making it easy to navigate between areas of your project. Examples of modules:
  • Login & Authentication
  • Checkout Flow
  • User Profile
  • API - Claims API
  • Dashboard

​
Creating a module

  1. From the left sidebar click Test Management → Modules
  2. Click Create Module
  3. Fill in the form:
​
Module Name
string
required
A clear name for the feature area. Minimum 3 characters.
Example: “Login & Authentication”
​
Description
text
required
A brief description of what this module covers.
Example: “All test cases related to user login, logout, and session management”
  1. Click Create Module. A unique Module Identifier (e.g. MOD-API-006) is automatically generated by the system.

​
Module actions

From the Modules list you can:
ActionDescription
ViewSee module details in read-only mode
EditUpdate the module name or description
DeletePermanently remove the module (requires confirmation)
View Test CasesNavigate directly to all test cases in this module
Deleting a module will also remove its association with all test cases inside it. Make sure to reassign or remove test cases before deleting a module.

​
How modules appear in test cases

When you open Test Cases, the left sidebar shows all modules for your project, each with a test case count. Click any module to view its test cases in the main panel. You can search modules by name using the search box at the top of the sidebar.

​
Tags

​
What is a tag?

A Tag is an optional label you can apply to a test case for additional categorisation — on top of the module it belongs to. Tags are useful for grouping test cases that span multiple modules, such as all regression tests or all API-related tests. Examples of tags:
  • regression
  • smoke
  • api
  • ui
  • security
  • performance
Tags are project-scoped — each project has its own set of tags. There are no system-wide default tags; all tags are created by your team.

​
Creating a tag

  1. From the left sidebar click Tags
  2. Click Create Tag
  3. Enter a Tag Name (minimum 3 characters)
  4. Click Save
New tags are created as inactive by default. You’ll need to activate a tag before it appears in the test case form dropdown.

​
Activating a tag

  1. Go to the Tags list
  2. Click Edit on the tag
  3. Toggle the Active switch to on
  4. Click Save
Only active tags are available when creating or editing test cases.

​
Tag actions

ActionDescription
EditUpdate the tag name or toggle active/inactive status
DeletePermanently remove the tag (requires confirmation)

​
Using tags on test cases

When creating or editing a test case, select a tag from the Tag dropdown. This field is optional and allows only one tag per test case. Tags can be cleared at any time.

​
Modules vs Tags — quick reference

ModulesTags
Required?Yes — every test case needs oneNo — optional
PurposeGroup test cases by feature areaLabel test cases across features
Appears inLeft sidebar of Test Cases pageTest case form dropdown
ScopeProject-specificProject-specific
IdentifierAuto-generated (e.g. MOD-API-006)Name only
One per test case?YesYes

​
What’s next?

Writing Test Cases

Create test cases within your modules

Running Tests

Execute test cases organised by module