Check eSEL property AdditionalData is not EMPTY
This use case will detect bugs like openbmc/openbmc#1217
Resolves openbmc/openbmc-test-automation#394
Change-Id: I7e89ecffcb4ff4461a90fc566a617f26409706b9
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/tests/test_esel.robot b/tests/test_esel.robot
index c9db34e..24581d4 100644
--- a/tests/test_esel.robot
+++ b/tests/test_esel.robot
@@ -52,7 +52,7 @@
Verify Multiple eSEL Using REST
- [Documentation] Generate multiple eSEL log and Verify using REST.
+ [Documentation] Generate multiple eSEL log and verify using REST.
[setup] Restart Logging Service
[Tags] Verify_Multiple_eSEL_Using_REST
Create eSEL
@@ -61,6 +61,25 @@
Should Be Equal As Integers ${entries} ${2}
+Check eSEL AdditionalData
+ [Documentation] Generate eSEL log and verify AdditionalData is
+ ... not empty.
+ [setup] Restart Logging Service
+ [Tags] Check_eSEL_AdditionalData
+ Create eSEL
+ ${resp}= OpenBMC Get Request ${BMC_LOGGING_ENTRY}${1}
+ Should Be Equal As Strings ${resp.status_code} ${HTTP_OK}
+ ${jsondata}= To JSON ${resp.content}
+ # "/xyz/openbmc_project/logging/entry/1": {
+ # "Timestamp": 1487743771812,
+ # "AdditionalData": [],
+ # "Message": "org.open_power.Error.Host.Event.Event",
+ # "Id": 1,
+ # "Severity": "xyz.openbmc_project.Logging.Entry.Level.Emergency"
+ # }
+ Should Not Be Empty ${jsondata["data"]["AdditionalData"]}
+
+
Test Wrong Reservation_ID
[Documentation] This testcase is to test BMC can handle multi-requestor's
... oem partial add command with incorrect reservation id.