commit 4898c50a74db6c9f3a64168cb88bab1f8c3fd851
author Sathyajith M S <sathyajith.ms@in.ibm.com> Wed Nov 20 01:51:03 2019 -0600
committer George Keishing <gkeishin@in.ibm.com> Tue Dec 03 16:44:30 2019 +0000
tree 9ed1ff024d5a924db22a1b9e254e9fd4f9404b24
parent cf6f9487c1bc2f0a0389d7076976018949b6e6bf

New - Verify Crash Dump Directory After NMI Inject

Created new 'Verify Crash Dump Directory After NMI Inject'
keyword to be called in place of existing in-line code.

Change-Id: If6512f8b403b1e8396221d96ffe2d0a2467fb657
Signed-off-by: Sathyajith M S <sathyajith.ms@in.ibm.com>
Signed-off-by: Naman Navin Hegde <nhegde89@in.ibm.com>

openpower/test_nmi_interface.robot

diff --git a/openpower/test_nmi_interface.robot b/openpower/test_nmi_interface.robot
index 695ecf1..482c528 100644
--- a/openpower/test_nmi_interface.robot
+++ b/openpower/test_nmi_interface.robot
@@ -32,14 +32,19 @@
     [Setup]  Test Setup Execution  ${0}
 
     Trigger NMI  valid_status_codes=[${HTTP_OK}]
-    # NMI Post Crash Dump Verification
+    Verify Crash Dump Directory After NMI Inject
+
+
+*** Keywords ***
+
+Verify Crash Dump Directory After NMI Inject
+    [Documentation]  Verification of crash dump directory after NMI inject.
+
     Wait Until Keyword Succeeds  10 min  1 min  Is Host Rebooted
     Is OS Booted
     Wait Until Keyword Succeeds  1 min  10 sec  Verify Crash Dump Directory
 
 
-*** Keywords ***
-
 Test Setup Execution
     [Documentation]  Test setup execution.
     [Arguments]  ${secure_boot_mode}=${1}
@@ -74,10 +79,12 @@
     Redfish.Post  ${SYSTEM_BASE_URI}Actions/ComputerSystem.Reset
     ...  body={"ResetType": "Nmi"}  valid_status_codes=${valid_status_codes}
 
+
 Verify Crash Dump Directory
     [Documentation]  Verify that the crash dump directory is not empty.
 
     # As per the requirement, there should be a crash dump file
     # after successful NMI injection.
+
     ${output}  ${stderr}  ${rc}=
     ...  OS Execute Command  ls -ltr /var/crash/*  print_out=1