RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Papers & Presentations Archive
SYSTEM TEST PLAN / TEST RESULTS | |||||||||||||||||||||||||||||||||||||||||
Project Id. | E-09874-01-01 | Project Name | RDK B&V | ||||||||||||||||||||||||||||||||||||||
System Test plan prepared /last modified by | Amrita Banik | System Test plan prepared /last modified on | 14/06/2019 | Total no of bugs | 0 | ||||||||||||||||||||||||||||||||||||
Test Start Date | 25-Jun-19 | Test End Date | 25-Jun-19 | ||||||||||||||||||||||||||||||||||||||
Scope of Testing | CcspEthAgent Validation in RDK-B RPI | ||||||||||||||||||||||||||||||||||||||||
System Test Cases | Test Results | Actual Outcome | |||||||||||||||||||||||||||||||||||||||
Test No. | Test Case Scenario No | Test Date | Req. ID | Test Case Scenario Description | Test Description (explaining test Condition, Setup and other details) | Test Case Designed For | Expected outcome | Iteration No. | Actual Result | ||||||||||||||||||||||||||||||||
Note: Web UI username is admin and Password is password. Test executed with multiple wired clients. | |||||||||||||||||||||||||||||||||||||||||
1 | T1 | 25/06/2019 | REFPLTB_336 | Validation of Boot-up using top command | 1) Boot up board and type ‘top’ command | Robustness | 1) No process should consistently occupy high CPU percentage. | 2 | Passed | 1) No process is consistently occupying high CPU percentage. | |||||||||||||||||||||||||||||||
2 | T2 | 25/06/2019 | REFPLTB_336 | Validation of Boot-up using reboot command | 1) Boot up board and type ‘reboot -f’ command | Robustness | 1) Box should get rebooted successfully | 2 | Passed | 1) Box rebooted successfully | |||||||||||||||||||||||||||||||
3 | T3 | 25/06/2019 | REFPLTB_336 | Validation of Boot-up by wireless connected client | Prerequisite: Client PC (Wired Client) should be connected to RPI box through USB to Ethernet adapter. 1) Boot up board 2) Open browser in connected client and enter "http://10.0.0.1" 3) Enter new SSID, connect to that SSID using mobile and browse | Robustness | 1) Box should get booted successfully 2) Captive portal should be displayed. 3) Browsing should happen successfully. | 2 | Passed | 1) Box booted successfully 2) Captive portal displayed successfully. 3) Browsing happened successfully. | |||||||||||||||||||||||||||||||
4 | T4 | 25/06/2019 | REFPLTB_336 | Validation of Boot-up by wired connected client | Prerequisite: Client PC (Wired Client) should be connected to RPI box through USB to Ethernet adapter. 1) Open browser in connected client and enter http: //10.0.0.1 2) Browse https: //www.google.com | Robustness | 1) WebUI should be displayed. 2) Browsing should happen successfully. | 2 | Passed | 1) WebUI got displayed. 2) Browsing happened successfully. | |||||||||||||||||||||||||||||||
5 | T5 | 25/06/2019 | REFPLTB_336 | Validation of Connected device Web UI page | Prerequisite: Client PC (Wired Client) should be connected to RPI box through USB to Ethernet adapter. 1) Boot up board 2) Open browser in connected client and enter "http://10.0.0.1" 3) Login to Web UI and go to “Connected Device” page 4) Verify the functionality for “Prefer Private Connection” 5) Verify that Online Devices section is showing data related to presently connected wired client 6) Verify that Offline Device section is showing data related to offline(previously connected) wired client | Robustness | 1) Box should get booted successfully 2) Web UI page should be displayed. 3) Login should be successful and “Connected Device” page should be displayed. 4) It should work for private connection 5) Presently connected devices should be displayed under Online Devices section 6) The device that once connected but presently not available should be displayed under Offline devices | 2 | Passed | 1) Box booted successfully 2) Web UI page got displayed. 3) Login was successful and “Connected Device” page got displayed. 4) It worked for private connection 5) Presently connected devices are displayed under Online Devices section 6) The devices that once connected but presently not available are displayed under Offline devices | |||||||||||||||||||||||||||||||
6 | T6 | 25/06/2019 | REFPLTB_336 | Validation of data displayed in Connected device using dmcli | Prerequisite: Client PC (Wired Client) should be connected to RPI box through USB to Ethernet adapter. 1) In R-Pi board terminal, execute the below mentioned dmcli commands and verify the respective output i) dmcli eRT getv Device.Hosts.HostNumberOfEntries ii) dmcli eRT getv Device.Hosts.Host.1.PhysAddress iii) dmcli eRT getv Device.Hosts.Host.1.IPAddress iv) dmcli eRT getv Device.Hosts.Host.1.DHCPClient v) dmcli eRT getv Device.Hosts.Host.1.Layer3Interface vi) dmcli eRT getv Device.Hosts.Host.1.HostName vi) dmcli eRT getv Device.Hosts.Host.1.Ipv4AddressNumberOfEntries vii) dmcli eRT getv Device.Hosts.Host.1.Ipv4Address.1.IPAddress viii) dmcli eRT getv Device.Hosts.Host.1.X_CISCO_COM_RSSI ix) dmcli eRT getv Device.Hosts.Host.1.AddressSource | Robustness | 1) dmcli should display below mentioned output: i) It should display number of host entries ii) It should display the physical address(MAC) for the connected device iii) It should display the IP address of connected device iv) It should display the client whether it is 'DHCP' client v) It should display Layer3Interface vi) It should display hostname of connected client vi) It should display number of entries in Ipv4 address vii) It should display the IPv4 address viii) It should display the RSSI value for wireless connected device ix) It should display Address source of the connected host | 2 | Passed | 1) dmcli should display below mentioned output: i) It displayed number of host entries ii) It displayed the physical address(MAC) for the connected device iii) It displayed the IP address of connected device iv) It displayed the client whether it is 'DHCP' client v) It displayed Layer3Interface vi) It displayed hostname of connected client vi) It displayed number of entries in Ipv4 address vii) It displayed the IPv4 address viii) It displayed the RSSI value for wireless connected device ix) It displayed Address source of the connected host | |||||||||||||||||||||||||||||||
7 | T7 | 25/06/2019 | REFPLTB_336 | Validation of Connected device WAN Network page | Prerequisite: Client PC (Wired Client) should be connected to RPI box through USB to Ethernet adapter. 1) Go to Gateway > connection > WAN Network 2) Click on DOCSIS, It will pop-up the message window 3) Execute the dmcli to make Ethernet button disable: dmcli eRT setv Device.Ethernet.X_RDKCENTRAL-COM_WAN.Enabled bool false | Robustness | 1) Verify in the left panel of WebUI, under “Connection” menu “Xfinity Network” and “WAN Network” sub-menu labels are displayed 2) Ethernet button should be enabled by default and WAN IP Address (IPv4) should show the R-PI box IP address 3) Message should display “DOCSIS Support is not available in RPI Boards” 4) It should display error message “Execution fail(error code:CCSP_ERR_INVALID_PARAMETER_VALUE(9007))” | 2 | Passed | 1) Xfinity Network sub-menu displayed “Xfinity Network” and “WAN Network” 2) Ethernet button is enabled by default and WAN IP Address (IPv4) 192.168.2.92 showed which is the R-PI box IP address 2) Message got displayed “DOCSIS Support is not available in RPI Boards” 3) It displayed error message “Execution fail(error code:CCSP_ERR_INVALID_PARAMETER_VALUE(9007))” |
Powered by a free Atlassian Confluence Open Source Project License granted to RDKCentral. Evaluate Confluence today.