Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents




API Explorer

Link to API Explorer : <<API Explorer>>

User can get to know the API's information such as API category, Class name, API name, Applicable for, description and parameter details.

...

  •                 Using Environment Type & API Category.
  •                 Using Keywords.

 Using Environment Type & API Category

         Environment Type: Select appropriate environment (for Eg. select RDKV for Video devices, RDKB for for broadband devices and RDKC for Cameras)

         API Category: Category of the API user want to explore.

Using Keywords

         Keywords: Name of the API. (For eg: keyword='CHANNEL_TUNE' it will list out the API names which contains the word CHANNEL_TUNE)

...

Other than that user can find out the Test cases(with Step Information) that is using the specific API:        .

Build Test Utility

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

...

              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 Test Manager icon as shown below,
              Settings Test Manager --> Build Utility


Steps to include Build Utility in Test cases

...