RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
User can login into Automatics through any one of the two authentication modes. One is Self-Authentication and another is LDAP Authentication.
By giving the respective credentials such as username & password and selecting either of the Self Authentication/LDAP Authentication modes from the drop down, user can login to Automatics Tool.
...
User can see the Builds Processed Details for a default time period of 30 days. User can change the date and click on filter to see the required details.
User can also see the Execution Details of Last 4.
...
To perform test execution, user needs to add test details to Automatics system. This can be done from Manage Scripts page.
Script Details
To add a new script, user can click on “Add New” link on the right top of page. Field “Automation Id” should be unique name that identifies an automated test. This id should match with the automation id in automated test case. Automatics considers RDK builds in any of the 3 categories ‘Sprint’, “Stable” and “Release”. A test case can be mapped to execute in any or all of the build types.
On Next page, Environment can be selected. In the screen shown below, the test is RDKV device related. So mapping the test against RDKV environment. Next applicable device model/s can be selected. End point “RACK_DEVICE” refers to devices managed by rack system and “DESK DEVICE” refers to desk devices. Head end field refers to device head end. If head end is provided, then during execution, Automatics can request for devices from given head end.
...