Introduction

The Module feature addresses the challenge of repetitive creation of common steps across multiple tests. By introducing Modules, users can create named groups of steps that are reusable across tests, reducing redundancy and streamlining test maintenance.

Few examples that demonstrate the diverse applications of the Module feature

1. Common Login Module:
   • Open application, enter credentials, click login.
   • Imported into tests requiring login for consistent authentication.
2. User Registration Module:
   • Open registration page, fill user details, submit, and validate registration.
   • Ensures standardized user registration across multiple tests.
3. API Testing Module:
   • Make API calls with specified parameters, validate the response.
   • Ensures reusability and consistency in backend validation across tests.
4. Navigation Module:
   • Navigate to the dashboard, access a specific module, go to the target page.
   • Simplifies common navigation steps, across multiple tests targeting a page.

You can create, edit, and import modules, ensuring that changes made to a module are reflected across all tests where the module is used.

Creating a Module

You can select a continuous set of steps and create a module with a unique and meaningful name.

Importing a Module

You can easily import any module while creating a test, by clicking on Import a Module option

Editing a Module

Any edits made to the module are reflected across all tests where the module is used. You can perform the following actions on a module:

• Add a step
• Edit a step
• Delete a step

Variables in Modules

• Variables used within a module have a module namespace, similar to dataset variables.
• Variables from the module can be used outside the module in other steps within the test.
• Variables from outside the module cannot be used inside the module during import. This is enforced during module creation.