I agree with Ruth, when you want to run the tests for real, repeatedly, you
would have the generated automation scripts stored in some repository and
have a third-party test automation engine execute them. These days more
often there is the strategy to let the CI/CD pipeline kick off these test
as part of a deployment in some environment.
When you are in the “design” and/or “develop” phase of your test automation
- i.e. defining the test automation config snippets and adding them to your
process blocks – then it is possible to run a command-line command for each
generated test path. It is defined in the Execution File field of the
“Layers” section of your automation config file. On the “export automation
scripts” window you will see a green play button (tooltip = execute script)
that will execute the command lines for the paths selected.
You can assess that the generated scripts are working ok, etc... I would
not recommend to use this for official testing. You will notice that before
the tests are started from the command line the scripts are always
regenerated. That can take a long time and is not practical is you need to
rerun the scripts. It’s running from the command line on your ARD system,
very often that is not the host that can actually send out the requests
that your test automation needs to execute – e.g. connectivity, etc...
Cheers,
Danny