Test Automation

No more manual refactoring of scripts -- with ARD, testers automate test script generation from the model.
As a tester, you record automated tests and export script files that you execute with your test automation framework. Instead of having to manually refactor and record all test variants, you use 
Agile Requirements Designer
 to automate test script generation for your test paths. 
Agile Requirements Designer
 can automate generation of test scripts for any platform, be it mobile, desktop, web, client/server, or mainframe. The only requirement is that you have an existing test automation engine available for the platform. 
Agile Requirements Designer
 generates your test automation scripts for the test engine. The engine then interacts with the mainframe screen, mobile device, desktop application, or web interface, respectively. 
Agile Requirements Designer
 has been applied to many ecosystems, utilizing test engines such as eggPlant, HP UFT, Ranorex, Selenium, and Cucumber/Gherkin, to name a few.
Automation Workflow
  1. Analyze your existing test cases. Identify code snippets and variables to build the flow that describes your system. Use predefined Keywords and define custom variables. 
  2. In each block of the flow, associate an action with a test code snippet and variable values for one test step.
  3. Generate and export test paths as automation scripts. 
  4. Run the scripts in your test automation engine.
If your test framework requires wrapper code, parameterize these prefixes or suffixes that you want to add automatically. There is no need to create extra flow blocks to insert headers and footers into the script, as flow blocks should only represent actions. You can generate one merged script, or several separate script files. The header and footer is added before and after the one merged script, or before and after each separate script file, respectively. For example, the header contains code to open the browser before running the tests; the footer contains code to close the browser after running the tests.
You can choose to exclude specific blocks or decisions from being wrapped with automation headers and footers: If overlapping braces or actions cause you issues, go to the Automation tab of a block, and enable the "Exempt Items from Automation Headers and Footers" checkbox for it.
Each test case can have several automation layers with different automation configurations. This feature enables you to export several different script files for one test case.
When you log into a CA TDM TDoD service and select profiles as a Target and Source, these profiles are remembered next time you log into the same service. They will also be used for resolving expressions containing “T” and “S” – e.g. the @execsql()@ function.
To add automation scripts to your test flow, use the following articles:
  1. Automation Scripts Examples: Learn from examples
  2. Define Your Automation Configuration: Create the configuration file that contains your custom test code library
  3. Construct Scripts from a Model: Lay out your flow and construct your test scripts