Test Parameterization

why do we need to parameterize a test ? while a session is very specific to an environment, the tests should be environment agnostic i e we should be able to execute it on any environment when you create a test or relicx generates a test, you can parameterize all the inputs required to run a test on another environment it is expected that the target environment will have the required data for the successful completion of the test for example, your test is supposed to create a user with a specific username and if you do not pass a new name every time you run the test, it will fail with a duplicate user error test parameterization is an easy way to address this problem usually, login credentials, general inputs on screens are all parameterized and are exposed in the test run screen at the time of execution how to parameterize your test ? before you start parameterizing your test, the first step would be to find out where the parameters are defined the parameters for every test can be seen by clicking the parameters & config button on the test edit page declaring a parameter whenever we are using data within an individual test, rather than hardcoding values within the actions/steps of our test, we can always declare a parameter to declare a parameter, we just write it in place, rather than a hardcoded value for an action as an example, if we wanted to write the name “ben” into a form, we could replace it with ${name} note the parameter name is a user choice, and they are case insensitive , but it must be in the ${parameter} format there are also some reserved names ${login url} ${username} ${password} ${base url} using a parameter whenever we run a test, we can provide a value for all of the parameters used in that test whenever we execute a test suite, all of the parameters across the suite will be shown so a value can be provided