...

Link to Build Test Utility : <<Build Test Utility>>

               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 advantages of build utility are reuse and it decreases the effort for user to create the same steps again and again.

...

             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

Manage Scripts

Link to Manage Script page: <<Manage Script page>>

For enabling, disabling, cloning and updating the testcase. We are using manage script page.    User  User needs to create a testcase by click on this button . 

...

For Mac address select check box E.g 00-xx-xx-xx-xx-xx and for good devices click on -> . . It will list the good devices. We can have Schedule trigger option also available, and the time needs to be mentioned. Device Group we can select based on the Automation ID. Build Appender and Notification mail will be mandatory. Source Repo needs to be mentioned based on the repo's available in the repository. Once all the details mentioned user Should click on the Trigger Job button. Once done Trigger will start successfully and via Job manager Tab.

Job Manager

Link to Job manager page : <<Job manager page>>.

User once trigger the testcase can able to find the execution results by clicking this button Image Added Once testcase triggered successfully. Following image will be available.

Image Added

We can find the full execution logs by clicking this button. Image Added . User can get the full execution logs and find out the pass and failure steps in detail. 

By clicking this icon we can see the child Jobs name . After that click on thsi icon .Then Jenkins Execution logs will be available . We can verify pass and failures of all the steps.