blob: 890bc8910e72dc1ff8e5799688a8aa8872b5a8a3 [file] [log] [blame]
Sweta Potthuri025e0122017-02-21 00:42:48 -06001*** Settings ***
2Documentation Basic BMC Linux kernel stability test.
3
4Resource ../lib/utils.robot
5Resource ../lib/connection_client.robot
6Resource ../lib/openbmc_ffdc.robot
7Resource ../lib/state_manager.robot
8
9Suite Setup Open Connection And Log In
10Suite Teardown Close All Connections
11
12# TODO: Collect proc data from system as part of FFDC
13# Refer openbmc/openbmc-test-automation#353
14Test Teardown FFDC On Test Case Fail
15
16*** Variables ***
17
18
19*** Test Cases ***
20
George Keishingdf11bfd2017-09-05 01:15:38 -050021File System Read Only
22 [Documentation] Verify that file system is read-only.
23 [Tags] File_System_Read_Only
24 ${output} ${stderr} ${rc}=
25 ... BMC Execute Command touch cold-play.txt ignore_err=${1}
26 Should Contain ${stderr} Read-only file system
27
28
Sweta Potthuri025e0122017-02-21 00:42:48 -060029Verify Boot Count After BMC Reboot
30 [Documentation] Verify boot count increments on BMC reboot.
31 [Tags] Verify_Boot_Count_After_BMC_Reboot
32
33 Set BMC Boot Count ${0}
34 Initiate BMC Reboot
Rahul Maheshwaria8f2b5e2017-08-23 04:38:43 -050035 Wait Until Keyword Succeeds 10 min 10 sec Is BMC Ready
36
Sweta Potthuri025e0122017-02-21 00:42:48 -060037 ${boot_count}= Get BMC Boot Count
38 Should Be Equal ${boot_count} ${1}
39 ... msg=Boot count is not incremented.