RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
...
API Explorer
Link to API Explorer: <<Api Explorer (rdkcentral.com)>>
User can get to know the API's information such as API category, Class name, API name, Applicable for, description and parameter details.
...
Environment Type: Select appropriate environment (for Eg. select E.g., select RDKV for Video devices, RDKB for broadband devices)
...
Link to Build Test Utility: <<Build Utility (rdkcentral.com)>>
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.
...
User can create testcase by clicking the above link and this is used to build create new testcase, Edit testcase.
The build test case Page will be as shown below:
...
* Delete Step: By clicking the delete icon, User can delete the particular test step
- Iterational
Iterational option will create a iteration step as shown below.Use-
User should be able to add Test Script with Iterational step and able to select LOOP/EXITLOOP from test type and able to enter the itteration count and duration in seconds.
The fields are explained below,
1. Step No:
Step number will be non-editable text box.
2. Description:
User should enter the detailed description about the test step.
3. Test Type:
User should select the test type. The drop down contains LOOP and EXIT-LOOP.
4. Input:
Provide steps to validate-
- Launch app/url through browser
Navigate to build testcase page.
Provide Valid test case id, select test type 'Functional', select device model...etc. and click on Next button, it will navigate to next page-build testcase page.
select Add Step and select Iterational step.
select LOOP/EXITLOOP from test type.
Add iteration count/duration in seconds by clicking input icon.
Iterational option will create an iteration step as shown below.
The fields are explained below,
1. Step No:
Step number will be non-editable text box.
2. Description:
User should enter the detailed description about the test step.
3. Test Type:
User should select the test type. The drop down contains LOOP and EXIT-LOOP.
4. Input:
By clicking theBy clicking the settings icon in the Action filed, User will be navigated to Add Iteration or Duration page as shown below.
...
We need to provide either Iteration Count or Duration in Seconds and click -> Save button. Now the Command / Test step added successfully.
- Conditional
Use-
Conditional option will create a condition step as shown below.
User should be able to add Test Script with Conditional step
The fields are explained below,
1. Step No.:
Step number will be non editable text box.
2. Description:
User should enter the detailed description about the test step.
3. Test Type:
User should select the test type. The drop down contains IF, ELSE-IF and ELSE.
4. Input:
By clicking the settings icon in the Action filed, User will be navigated to Add Condition page as shown below.
* Operator: User should select the Operator type. The drop down contains AND and OR options.
step is use add condition (E.g., IF, IFELSE, ELSE).
Provide steps to validate-
1.Launch url Automatics (rdkcentral.com)
2.Navigate to build testcase page
3. Provide Valid test case id, select test type 'Functional', select devicemodel...etc and click on Next button, it will navigate to next page-build testcase page
4. select Add step and select conditional step
5. select IF/ELSEIF/ELSE condition from test type
Conditional option will create a condition step as shown below.
The fields are explained below,
1. Step No.:
Step number will be non editable text box.
2. Description:
User should enter the detailed description about the test step.
3. Test Type:
User should select the test type. The drop down contains IF, ELSE-IF and ELSE.
4. Input:
By clicking the settings icon in the Action filed, User will be navigated to Add Condition page as shown below.
* Operator: User should select the Operator type. The drop down contains AND and OR options.
* * Invert Result: User should select the NOT check box to invert condition.
...
After entering all the details of the input condition, need to click on the plus icon. User can verify once whether all the details are valid and then click on the Save button. Now the command/test step detail is added.
- Check Point
Use-
- Check point is
...
- use to add some sub steps inside and get a valid primary output from them. User can add child step by clicking child step icon.
- By clicking child step user can able to add step, conditional, iterational and import steps.
Provide steps to validate-
- Launch url Build Test Case (xcal.tv)
- Navigate to build testcase page.
- Provide Valid test case id, select test type 'Functional', select device model...etc. and click on Next button, it will navigate to next page-build testcase page
- select Add step and select Checkpoint step.
User should be able to add Test Script with Checkpoint
The fields are explained below,
1. Step No:
Step number will be a non-editable text box.
2. Description:
The user should enter a detailed description of the test step.
3. Expected Result:
User should enter expected result of the step.
4. Impact:
User should enter the impact of the step.
5. Action:
This field is explained above under Step.
- Import Steps
Use-
Import steps is used to import steps from existing testcase or user can import test steps from other testcase.
Provide steps to validate-
1.Launch url Build Test Case (xcal.tv)
2.Navigate to build testcase page
3. Provide Valid test case id, select test type 'Functional', select device model...etc. and click on Next button, it will navigate to next page-build testcase page
4. select Add step and select import steps
5. Select import testcase from this testcase/other testcase
How to add Check point-
User should be able to add Test Script with Checkpoint
The fields are explained below,
1. Step No:
Step number will be a non-editable text box.
2. Description:
The user should enter a detailed description of the test step.
3. Expected Result:
User should enter expected result of the step.
4. Impact:
User should enter the impact of the step.
5. Action:
This field is explained above under Step.
...
User can import a test step from the same testcase by clicking the Import Steps Button in Action.
...
By providing the Step Number(case-sensitive) in the given textbox and click Import, given step will be cloned/imported.
Import test steps from other testcase-
User can import a test step from the other testcase by clicking the Import Steps Button in Action.
By providing the Testcase ID in the given textbox and click Import, given testcase steps will be cloned/imported.
EDIT, CLONE& DELETE Test case.
...
Overview
Community Forums
Content Tools
Tasks