Have you ever wondered how to run the same test with different URLs?
Did you want to run your suite in different environments - test, staging and possibly production and did not know what would be the best way to do it?
You came to the right place.
Typically, you record your tests on the development/test environment and then you want to run your tests on other environments as well.
We provide a base URL parameter that can be used in all remote runs methods.
Here's a list of components you can use to send a different base URL:
Base URL Parameter
In every custom action/validation, you can access your base URL using the "BASE_URL" parameter. e.g. console.log("Base URL:" + BASE_URL)
You can also use this in navigation step.
Overriding base URL and navigation hosts
In setup step in a test, you sometimes pass the base URL with a path to a specific location in your application. In that case, when passing a different base URL to the test, navigation will be relative to the base URL sent.
Example: If base Url in setup is http://staging.com/login , when passing this base Url parameter in runtime: http://preprod.com , the actual navigation in run time will be to : http://preprod.com/login.
In navigation steps, you sometimes navigate to a URL with the same host as in your setup step. In that case, when passing a different base URL to the test, navigation will be relative to the base URL sent.
Example: If base Url in setup is http://staging.com/ and the URL in navigation step is http://staging.com/ca . When passing this base Url parameter in runtime: http://preprod.com/ , the actual navigation in run time will be to : http://preprod.com/ca.
Rerun with the same parameters
This allows you to rerun locally, a test that was run remotely with different base URL. It will also use the same parameters as run by the remote run.
Read more here.