Manage Automation Configuration Files

By default, ard stores automation configurations in one file. For more complex test sets, you have the option of maintaining configurations in separate files in a version-controlled directory structure. Using the Git Connector to manage complex configurations brings the following advantages:
ard24
By default, 
Agile Requirements Designer
 stores automation configurations in one file. For more complex test sets, you have the option of maintaining configurations in separate files in a version-controlled directory structure. Using the Git Connector to manage complex configurations brings the following advantages:
  • Storing configurations in separate files enables you to use  features of your integrated development environment (IDE) to edit code snippets.
  • Integrated file version control enables your team to track revisions of configuration files in Git repositories. 
  • You can call Git commands such as merge, pull, and push right in the 
    Agile Requirements Designer
     interface, and do not need to switch to the command line. 
The Git Connector provides very limited functionality for managing automation scripts through Git. For a more complete solution, we recommend using a full-featured Git GUI application. For more information on how to enable the Git Connector, see Enable Standard Settings and Advanced Features.
Configure the Git Connector for Automation Configurations
 
Agile Requirements Designer
 supports file version control with Git. In the following we assume that you have already installed a Git client and cloned a repository.
Follow these steps:
 
  1. Set up a folder to store objects and actions in directories and files:
    1. Click 
      Home
      ,
       General Config
    2. Click the 
      Load 
      button in the top, and select the directory where you store the general configuration files.
    3. Click 
      Save & Close
      .
    4. Click 
      Home
      ,
       Automation
      .
    5. Click the 
      Load 
      button in the top, and select the directory where you store the automation configuration files.
    6. Click 
      Save & Close
      .
  2. Click 
    Home
    ,
     General Config
    . Click the 
    GIT File Status
     tab.
    1. Click the 
      General Configuration
       tab and define the Git Folder for the general configuration file.
    2. Click the 
      Automation Configuration
       tab and define the Git Folder for the automation configuration file.
    3. Click the 
      Automation Scripts
       tab and define the Git Folder for the automation scripts file.
    4. Click 
      Save & Close
      .
  3. Click 
    Home
    ,
     Automation
    , and click the 
    Layers 
    tab. For each layer, do the following:
    1. Enable 
      Advanced, Select objects and actions from folder location.
       
    2. Enter your local Git repository location in the
       Advanced, File Structure Location 
      field.
    3. Define your 
      Git Remote Name
      .
    4. (Optional)
       
      Enable one or more of the following options:
      If you enable both options, 
      Agile Requirements Designer
      commits and pushes configuration changes when you click 
      Save
       in the 
      Automation Configuration
       window.
      •  
        Commit changes to local branch when saving
         
      •  
        Push changes to remote origin when saving
         
    5. Click 
      Save As
       and close. 
The 
Commit changes
 and 
Push changes
 check boxes do not depend on each other. For example, you can have a previous commit that you have not yet pushed. In this case, if the 
Commit changes
 option was disabled and the 
Push changes
 check box was enabled, then nothing would be committed, but the previously un-pushed commit would be pushed.
To create a new configuration without overwriting the current configuration, use 
Save As
 and save a copy under a new name.
Create a File Structure
The code snippet editor in 
Agile Requirements Designer
 does not have any advanced editing features. You may want to use an IDE to open the files from the Automation Configuration directory, and edit more complex code snippets in your preferred source editor to make use of error handling and IntelliSense. 
Your 
Objects & Actions
 have an implicit tree structure:
Object Type
Action Type
Code Snippet
Click
Create List
...
Open Application
...
Validate Exists
...
Open
Click
..
Press Keys
...
Rather than applying a configuration to each layer, you can set up a file structure in your git repository. 
  • C:\MYGIT\
    • Click\
      • Create List.txt
      • Open Application.txt
      • Validate Exists.txt
    • Open\
      • Click.txt
      • Press Keys.txt
Share Configurations
You can use Git on the command line to share configurations, or in 
Agile Requirements Designer
. For details, see the Git documentation.
  1. Click 
    Home
    ,
     General Config
  2. Click the 
    GIT File Status
     tab.
  3. Select a target 
    Branch
    .
  4. Use Git commands to receive or submit changes to configuration files.
    • Pull - download others' changes from repository
    • Push - upload your changes to repository
    • Settings 
    • Merge - merge branches
    • Delete - delete a branch
    • Branch - make a new branch
    • Clone - download an existing repository and its history
    • Commit - record change snapshot of this branch in history
    • Push changes immediately