...

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

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 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

Create Test Utility

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

Image Modified

Steps to include Build Utility in Test cases

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

             Then user can add that utility as a step while creating the test case as shown below,

Image Modified

 If user want to include the utility in test case below steps should be followed,

• • 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

Test Constants

               Test constant here in automatics means the command or log file or any string that gets used more frequently is called as a test constant
               We can declare the test constant once and can use the same in multiple places.

              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.

Image Modified

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

Image Modified

Manage Test Trigger

For triggering the test cases and verify the test results it will be available inside Manage Test Trigger Tab.

Manage Test Trigger tab has following devices-> RDK-V, RDK-B, RDK-C For these devices we can Trigger our testcases and Scheduled Triggering part as a sub tabs.

Image Added

For Environment Type we need toSelect the appropriate environment (for E.g. select RDKV for Video devices, RDKB for broadband devices and RDKC for Cameras). Based on the selected Sub Environment Type value, testcases will be present in the next window.