[RDKE] L2 Tests And Integration With CI for Remote Debugger Dynamic Updates

run_l2.sh

@@ -27,6 +27,9 @@ mkdir -p "$RESULT_DIR"
 mkdir -p "$OUTPUT_DIR"
 mkdir -p "$STATIC_PROFILE_DIR"
 mkdir -p "$LIB_DIR"
+mkdir -p /media/apps/RDK-RRD-Test/etc/rrd
+
+touch /media/apps/RDK-RRD-Test/etc/rrd/remote_debugger.json
 
 apt-get remove systemd
 apt-get update && apt-get install -y tcpdump
@@ -56,6 +59,10 @@ rm -rf /tmp/rrd/*
 rm -rf /opt/logs/remotedebugger.log*
 
 # Run L2 Test cases
+pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_dynamic_profile_missing_report.json test/functional-tests/tests/test_rrd_dynamic_profile_missing_report.py
+pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_dynamic_profile_harmful_report.json test/functional-tests/tests/test_rrd_dynamic_profile_harmful_report.py
+pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_dynamic_profile_report.json test/functional-tests/tests/test_rrd_dynamic_profile_report.py
+pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_append_dynamic_profile_static_notfound.json test/functional-tests/tests/test_rrd_append_dynamic_profile_static_notfound.py
 pytest  --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_single_instance.json test/functional-tests/tests/test_rrd_single_instance.py
 pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_start_control.json test/functional-tests/tests/test_rrd_start_control.py
 pytest --json-report --json-report-summary --json-report-file $RESULT_DIR/rrd_start_subscribe_and_wait.json test/functional-tests/tests/test_rrd_start_subscribe_and_wait.py

test/functional-tests/features/rrd_append_dynamic_profile_static_not_found.feature

@@ -0,0 +1,45 @@
+##########################################################################
+# If not stated otherwise in this file or this component's LICENSE
+# file the following copyright and licenses apply:
+#
+# Copyright 2018 RDK Management
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##########################################################################
+
+Feature: Remote Debugger Append Request Missing Issuetype
+
+  Scenario: Verify remote debugger process is running
+    Given the remote debugger process is not running
+    When I start the remote debugger process
+    Then the remote debugger process should be running
+
+  Scenario: Send WebPA event for Issuetype Test.TestRun1_apnd and verify logs
+    Given the remote debugger is running
+    When I trigger the event "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.RDKRemoteDebugger.IssueType"
+    Then the logs should contain "SUCCESS: Message sending Done"
+    Then the logs should be seen with "SUCCESS: Message Reception Done"
+    And the issuetype request should match between Send and Receive
+
+  Scenario: Verify the Issuetype is found in dynamic profile
+    Given the remote debugger received the message from RBUS command
+    When the remotedebugger read the json file form the dynamic path
+    Then remotedebugger json read and parse should be success in dynamic path
+
+  Scenario: Verify the Issuetype is not found in static profile
+    Given the remote debugger received the message from RBUS command
+    When the remotedebugger static json profile is present
+    Then remotedebugger should read the Json file
+    And remotedebugger logs should contain the Json File Parse Success
+    And remotedebugger should log as the Issue requested is not found in the profile
+    And issuetype is not found in static json and abort command execution

test/functional-tests/features/rrd_dynamic_profile_missing_report.feature

@@ -0,0 +1,45 @@
+##########################################################################
+# If not stated otherwise in this file or this component's LICENSE
+# file the following copyright and licenses apply:
+#
+# Copyright 2018 RDK Management
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##########################################################################
+
+Feature: Remote Debugger Missing Issuetype
+
+  Scenario: Verify remote debugger process is running
+    Given the remote debugger process is not running
+    When I start the remote debugger process
+    Then the remote debugger process should be running
+
+  Scenario: Send WebPA event for Issuetype Test and verify logs
+    Given the remote debugger is running
+    When I trigger the event "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.RDKRemoteDebugger.IssueType"
+    Then the logs should contain "SUCCESS: Message sending Done"
+    Then the logs should be seen with "SUCCESS: Message Reception Done"
+    And the issuetype request should match between Send and Receive
+
+  Scenario: Verify the Issuetype is not found in static profile
+    Given the remote debugger received the message from RBUS command
+    When the remotedebugger static json profile is present
+    Then remotedebugger should read the Json file
+    And remotedebugger logs should contain the Json File Parse Success
+    And remotedebugger should log as the Issue requested is not found in the profile
+
+  Scenario: Verify the Issuetype is not found in dynamic path
+    Given the remote debugger issuetype is missing in static profile
+    When the remotedebugger read the json file form the dynamic path
+    Then remotedebugger json read and parse should be failed
+    And remotedebugger should request RDM to download the package

test/functional-tests/features/rrd_dynamic_profile_report.feature

@@ -0,0 +1,60 @@
+##########################################################################
+# If not stated otherwise in this file or this component's LICENSE
+# file the following copyright and licenses apply:
+#
+# Copyright 2018 RDK Management
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##########################################################################
+
+Feature: Remote Debugger Dynamic Issuetype Report
+
+  Scenario: Verify remote debugger process is running
+    Given the remote debugger process is not running
+    When I start the remote debugger process
+    Then the remote debugger process should be running
+
+  Scenario: Send WebPA event for Issuetype Test and verify logs
+    Given the remote debugger is running
+    When I trigger the event "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.RDKRemoteDebugger.IssueType"
+    Then the logs should contain "SUCCESS: Message sending Done"
+    Then the logs should be seen with "SUCCESS: Message Reception Done"
+    And the issuetype request should match between Send and Receive
+
+  Scenario: Verify the Issuetype is not found in static profile
+    Given the remote debugger received the message from RBUS command
+    When the remotedebugger static json profile is present
+    Then remotedebugger should read the Json file
+    And remotedebugger logs should contain the Json File Parse Success
+    And remotedebugger should log as the Issue requested is not found in the profile
+
+  Scenario: Verify the Issuetype in dynamic path
+    Given the remote debugger issuetype is missing in static profile
+    When the remotedebugger read the json file form the dynamic path
+    Then remotedebugger json read and parse should be success
+    And remotedebugger should read the Issuetype from dynamic profile
+    And the issue data node and sub-node should be found in the JSON file
+    And the directory should be created to store the executed output
+    And Sanity check to validate the commands should be executed
+    And Command output shopuld be added to the output file
+    And the issuetype systemd service should start successfully
+    And the journalctl service should start successfully
+    And the process should sleep with timeout
+    And the issuetype systemd service should stop successfully
+    And the remotedebugger should call script to upload the debug report
+
+  Scenario: Upload remote debugger debug report
+    Given the remote debugger upload script is present
+    When I check the upload status in the logs
+    Then the upload should be successful if upload is success
+    Or the upload should fail if upload fails    

test/functional-tests/features/test_rrd_dynamic_profile_harmful_report.feature

@@ -0,0 +1,55 @@
+##########################################################################
+# If not stated otherwise in this file or this component's LICENSE
+# file the following copyright and licenses apply:
+#
+# Copyright 2018 RDK Management
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##########################################################################
+
+Feature: Remote Debugger Harmful Commands Dynamic Issuetype Report
+
+  Scenario: Verify remote debugger process is running
+    Given the remote debugger process is not running
+    When I start the remote debugger process
+    Then the remote debugger process should be running
+
+  Scenario: Send WebPA event for Issuetype Test and verify logs
+    Given the remote debugger is running
+    When I trigger the event "Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.RDKRemoteDebugger.IssueType"
+    Then the logs should contain "SUCCESS: Message sending Done"
+    Then the logs should be seen with "SUCCESS: Message Reception Done"
+    And the issuetype request should match between Send and Receive
+
+  Scenario: Verify the Issuetype is not found in static profile
+    Given the remote debugger received the message from RBUS command
+    When the remotedebugger static json profile is present
+    Then remotedebugger should read the Json file
+    And remotedebugger logs should contain the Json File Parse Success
+    And remotedebugger should log as the Issue requested is not found in the profile
+
+  Scenario: Verify the Issuetype in dynamic path
+    Given the remote debugger issuetype is missing in static profile
+    When the remotedebugger read the json file form the dynamic path
+    Then remotedebugger json read and parse should be success
+    And remotedebugger should read the Issuetype from dynamic profile
+
+  Scenario: Check for harmfull commands and abort
+    Given remote debugger parse the Dynamic json profile successfully
+    When the issue node and subnode are present in the profile
+    Then the remote debugger should read the Sanity Check list from profile
+    And the remotedebugger should perform sanity check on issue commands
+    Given the remote debugger profile has the harmfull commands
+    When the issue command and the sanity commands are matched
+    Then the remote debugger should exit the processing of commands
+    And Abort the commmand execution and skip report upload

test/functional-tests/tests/create_json.sh

@@ -0,0 +1,39 @@
+##########################################################################
+# If not stated otherwise in this file or this component's LICENSE
+# file the following copyright and licenses apply:
+#
+# Copyright 2018 RDK Management
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+##########################################################################
+
+#!/bin/bash
+
+# Step 1: Create a JSON file
+json_file="/media/apps/RDK-RRD-Test/etc/rrd/remote_debugger.json"
+echo '{
+  "Test": {
+    "TestRun3": {
+      "Commands": "cat /version.txt;uptime;rm -rf;cat /tmp/.deviceDetails.cache",
+      "Timeout": 10
+    },
+    "TestRun2": {
+      "Commands": "cat /version.txt;uptime;/proc/version;cat /proc/buddyinfo;cat /proc/meminfo;cat /tmp/.deviceDetails.cache",
+      "Timeout": 10
+    },
+    "TestRun1": {
+      "Commands": "cat /version.txt;uptime;cat /proc/buddyinfo;cat /proc/meminfo;cat /tmp/.deviceDetails.cache",
+      "Timeout": 10
+    }
+  }
+}' > $json_file

test/functional-tests/tests/helper_functions.py

@@ -36,7 +36,13 @@
 HARMFULL_STRING = "Command.Harm"
 MISSING_STRING = "Test.TestRun"
 BACKGROUND_STRING = "Device.Dump"
-
+DYNAMIC_DIR="/media/apps/RDK-RRD-Test/etc/rrd"
+DYNAMIC_JSON_FILE = "/media/apps/RDK-RRD-Test/etc/rrd/remote_debugger.json"
+DYNAMIC_STRING = "Test"
+DYNAMIC_HARMFUL_STRING = "Test.TestRun3"
+APPEND_STRING ="Test.TestRun2_apnd"
+APPEND_STRING1 ="Test.TestRun4_apnd"
+APPEND_JSON_FILE ="/media/apps/RDK-RRD-Test/etc/rrd/remote_debugger.json"
 def remove_logfile():
     try:
         if os.path.exists(RRD_LOG_FILE):