What describes the role of modules in Tosca automation?

• A. They are optional and not used for building tests.
• B. They store the technical information and are the foundation of Tosca test automation.
• C. They are used only for MBTA.
• D. They manage user accounts.

Answer: (B)

Modules in Tosca define how to interact with a specific part of the application under test. They store the technical information needed to perform actions, such as element locators for UI controls, the available actions, and the input/output parameters. Because a Module encapsulates these interaction details, it becomes a reusable building block that can be used across many test cases and test steps. This makes maintenance much easier: when something changes in the application, you update the module once and all tests that rely on it automatically reflect the change.

Modules come in different types (like UI modules for interfaces or API modules for services) and act as the foundation of Tosca automation, since tests are built by assembling steps that call these module actions with data. They are not optional, nor limited to a single project like MBTA, and they don’t handle user account management.