HTX bootme error log check every loop cycle
Fixes:
- Added error log checking.
- Delete error log as part of test setup.
- Keyword name changes for setup and teardown.
Change-Id: I92e97d7f41ae240cab71733a728d67716460eb62
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/systest/htx_hardbootme_test.robot b/systest/htx_hardbootme_test.robot
index 8dd89a1..f0a0fba 100755
--- a/systest/htx_hardbootme_test.robot
+++ b/systest/htx_hardbootme_test.robot
@@ -36,12 +36,13 @@
# "size".
Resource ../syslib/utils_os.robot
+Resource ../lib/openbmc_ffdc_utils.robot
Library ../syslib/utils_keywords.py
Library ../lib/utils_files.py
Suite Setup Run Keyword Start SOL Console Logging
-Test Setup Pre Test Case Execution
-Test Teardown Post Test Case Execution
+Test Setup Test Setup Execution
+Test Teardown Test Teardown Execution
*** Variables ****
@@ -136,6 +137,7 @@
... Do Inventory And Compare ${json_final_file_path}
... ${PREV_INV_FILE_PATH}
+ Error Logs Should Not Exist
Power Off Host
# Close all SSH and REST active sessions.
@@ -206,7 +208,7 @@
... AND Sleep ${HTX_INTERVAL}
-Post Test Case Execution
+Test Teardown Execution
[Documentation] Do the post test teardown.
# 1. Shut down HTX exerciser if test Failed.
# 2. Capture FFDC on test failure.