Parameters are essential in automated testing, enabling dynamic data management and flexibility in test execution.
Various parameter types facilitate data sharing, customization, and manipulation to meet testing needs.
By effectively leveraging these different parameter types, automated tests can become more scalable, maintainable, and adaptable to evolving data requirements.
Below are the key types of parameters and their functionalities.
Input Parameters & Data Sets
Input parameters allow test scripts to receive values from predefined data sets. Each planned test execution (Planned Run) can be linked to a specific data set, ensuring that scripts dynamically use relevant values during execution.
Output parameters represent the values that a component is expected to provide as output. Components utilize both input and output parameters.
Global Data Parameters
Global Data parameters enhance data management by enabling data sharing across tests within a project. They function as input parameters that support data branching for different test scenarios and include a hierarchical lookup mechanism when dataset values are empty. This approach improves flexibility, minimizes redundancy, and enhances test reusability.
Internal Parameters
Internal parameters store values used within a script, enabling reuse and modification throughout script execution. They help maintain consistency and simplify complex test logic.
By effectively leveraging these different parameter types, automated tests can become more scalable, maintainable, and adaptable to evolving data
Parameter Type Comparison
The table below outlines the parameters used in testing, detailing how they are written and read during test execution.
Parameter type | Write | Read |
Input Parameters | Defined statically in the Data Set | During test/component execution |
Output Parameters | Set dynamically by the component | By the test/component that invokes the component that defines the parameter |
Internal Parameters | Set dynamically during test/component execution | By the test/component that defined them |
Global Data | Defined statically at the folder, cycle, or project level | During test/component execution |