Frequently Asked Question

A test is an element that makes sense to be executed on its own. It contains the commands to be executed, variables and their definitions, and, if necessary, files used during the test execution. A test can be called by other tests (as long as it doesn't create a circular dependency), and when this happens, its variables and files are included in the execution. A test can be executed at any time and can also be added to a UAT.

A component, on the other hand, is an element that is not meant to be executed independently. It represents a reusable step that can be used across multiple tests — for example, the setup and login sequence at the beginning of many tests. A component only contains the commands to execute; it does not have variables or additional files, nor can it call other tests. However, a component can include parameters, which are indicated by an “@” symbol before the parameter name. When a test calls a component, it is responsible for assigning values to each of the component’s parameters.