Following are the new pages added for scriptless execution support in Orchestration

API Explorer

Link to API Explorer : <<API Explorer>>

...

               Build utility in automatics is creating the frequently used steps as utility. The same utility can be injected in to any other testcases. 
               For example, if 4 steps are used in common for multiple testcases then user can club those four steps into a build utility and then user can insert that utility into any other test cases.
               The advantage of build utility is reusability since it decreases the effort for user to create the same steps again and again.

Create Test Utility

              Build utility can be created in the same way as build test case.
              User can create utility by clicking Build Utility tab under Test Manager icon as shown below,
              Test Manager --> Build Utility

Steps to include Build Utility in Test cases

             First user should create the repeated steps as utility as shown above.

...

• • Select command type as USER_DEFINED_UTILITY and then automatically all the build utilities created will be loaded.
  • Then user can select the utility that must be included in the testcase as shown above

Build Test Case

Link to Build Test case : <<Build Test case>>

...

By clicking the delete icon in Action column in Available test cases table, user can delete the test case. 

Test Constants

Link For Test Constants :<<Test Constants>>

...

              The main advantage of the test constant is it avoids the stabilization effort or test case developer can change the value at one place rather than spending effort on searching all the testcases that                     uses the string.
              Also, whenever user changes any value of the test constant, it impacts all the testcases that are using that test constant.
              So, while editing test constant one should be very careful as its impact might be huge

Create Test Constant

              Test constant can be created through test constants page under settings tab. Settings →  Test Constants
              User should click on Add Constant button and add the constant name and constant value as shown below.
              Constants name must be unique.

Steps to include Test Constants in Test cases

             To add test constant in test case we need to use {{as the trigger. When user enters {{ then all the test constants are listed under as shown below.
             Test constants always starts with TC$ and user can select the test constant as per the requirement.

...