| commit | 192d5e763053568f4be1221bd0027bbe31c0253e | [log] [tgz] |
|---|---|---|
| author | Michael Walsh <micwalsh@us.ibm.com> | Thu Nov 01 14:09:11 2018 -0500 |
| committer | George Keishing <gkeishin@in.ibm.com> | Fri Nov 02 15:58:46 2018 +0000 |
| tree | 684c6c54566a9d75679b55098f639deb5983e7d7 | |
| parent | 815b1d5b35bcad54882124639772ace2ccd03292 [diff] |
In master_os_up_match, allow for host to be 'Quiesced' The OS host may very well be up and running while the 'host' state is 'Quiesced'. Change-Id: If25383d4d221ecdf4a96f9c6489bf48d7491c1b3 Signed-off-by: Michael Walsh <micwalsh@us.ibm.com>
Interface Feature List
Key Feature List
Debugging Supported List
Miscellaneous Packages required to be installed for OpenBmc Automation. Install the packages and it's dependencies via pip
REST base packages:
$ pip install -U requests $ pip install -U robotframework-requests $ pip install -U robotframework-httplibrary
SSH and SCP base packages: For more detailed installation instructions see robotframework-sshlibrary
$ pip install robotframework-sshlibrary $ pip install robotframework-scplibrary
Installing tox:
$ pip install -U tox
If using Python 3.x, use the corresponding pip3 to install packages.
These documents contain details on developing OpenBMC test code and debugging.
To verify the installation setup is completed and ready to execute.
$ git clone https://github.com/openbmc/openbmc-test-automation $ cd openbmc-test-automation
$ robot -v OPENBMC_HOST:xx.xx.xx.xx templates/test_openbmc_setup.robotwhere xx.xx.xx.xx is the BMC hostname or IP.
There are several sub-directories within the openbmc-test-automation base which contain test suites, tools, templates, etc. These sub-directories are classified as follows:
tests/: Contains the general test cases for OpenBMC stack functional verification.
extended/: Contains test cases for boot testing, network testing, code update testing etc.
systest/: Contains test cases for HTX bootme, IO storage and EEH testing.
xcat/: Contains test cases for XCAT automation.
gui/: Contains test cases for web UI and security scanning tool automation.
mnfg/: Contains test cases for factory reset (DHCP mode) and PGOOD testing.
network/: Contains test cases for network testing. It covers IPv4 in static mode and in DHCP mode.
snmp/: Contains test cases for SNMP (Simple Network Management Protocol) configuration testing.
remote_logging: Contains test cases for remote logging via rsyslog.
openpower/ras/: Contains test cases for RAS (Reliability, Availability and Serviceability) for an OpenPOWER system.
openpower/secureboot/: Contains test cases for secure boot testing on a secure boot feature enabled OpenPOWER system only.
tools/: Contains various tools.
templates/: Contains sample code examples and setup testing.
test_list/: Contains the argument files used for skipping test cases (e.g "skip_test", "skip_test_extended", etc.) or grouping them (e.g "HW_CI", "CT_basic_run", etc.).
OpenBMC is moving steadily towards DTMF Redfish, which is an open industry standard specification and schema that meets the expectations of end users for simple, modern and secure management of scalable platform hardware.
redfish_test: Contains test cases for DMTF Redfish-related feature supported on OpenBMC.
To run openbmc-automation first you need to install the prerequisite Python packages which will help to invoke tests through tox (Note that tox version 2.3.1 or greater is required) or via Robot CLI command.
Robot Command Line
Execute all test suites for tests/:
$ robot -v OPENBMC_HOST:xx.xx.xx.xx tests
Execute a test suite:
$ robot -v OPENBMC_HOST:xx.xx.xx.xx tests/test_basic_poweron.robot
Initialize the following environment variables which will be used during testing:
$ export OPENBMC_HOST=<openbmc machine ip address> $ export OPENBMC_PASSWORD=<openbmc password> $ export OPENBMC_USERNAME=<openbmc username> $ export OPENBMC_MODEL=[./data/Witherspoon.py, ./data/Palmetto.py, etc] $ export IPMI_COMMAND=<Dbus/External> $ export IPMI_PASSWORD=<External IPMI password>
For QEMU tests, set the following environment variables as well:
$ export SSH_PORT=<ssh port number> $ export HTTPS_PORT=<https port number>
Run tests:
$ tox -e tests
How to run individual test:
One specific test:
$ tox -e default -- --include Power_On_Test tests/test_basic_poweron.robot
No preset environment variables, default configuration for all supported systems:
$ OPENBMC_HOST=x.x.x.x tox -e default -- tests
No preset environment variables, one test case from a test suite:
$ OPENBMC_HOST=x.x.x.x tox -e default -- --include Power_On_Test tests/test_basic_poweron.robot
No preset environment variables, the entire test suite:
$ OPENBMC_HOST=x.x.x.x tox -e default -- tests
No preset environment variables, the entire test suite excluding test cases using argument file:
$ OPENBMC_HOST=x.x.x.x tox -e default -- --argumentfile test_lists/skip_test tests
Exclude test list for supported systems:
Palmetto: test_lists/skip_test_palmetto Witherspoon: test_lists/skip_test_witherspoon
How to run CI and CT bucket test:
Default CI test bucket list:
$ OPENBMC_HOST=x.x.x.x tox -e default -- --argumentfile test_lists/HW_CI tests
Default CI smoke test bucket list:
$ OPENBMC_HOST=x.x.x.x tox -e default -- --argumentfile test_lists/CT_basic_run tests
Run extended tests:
For-loop test (default iteration is 10):
$ robot -v OPENBMC_HOST:x.x.x.x -v OPENBMC_SYSTEMMODEL:xxxxxx -v ITERATION:n -v LOOP_TEST_COMMAND:xxxxxx extended/full_suite_regression.robot
Example using tox testing a test suite for 5 iterations "witherspoon":
OPENBMC_HOST=x.x.x.x LOOP_TEST_COMMAND="tests/test_fw_version.robot" ITERATION=5 OPENBMC_SYSTEMMODEL=witherspoon tox -e witherspoon -- ./extended/full_suite_regression.robot
Jenkins jobs tox commands
$ OPENBMC_HOST=x.x.x.x tox -e default -- --argumentfile test_lists/HW_CI tests
Currently supported BMC and PNOR update formats are UBI and non-UBI. For code update information, please refer to code-update.md
UBI Format *
For BMC code update, download the system type *.ubi.mdt.tar image from https://openpower.xyz/job/openbmc-build/ and run as follows:
For Witherspoon system:
$ cd extended/code_update/ $ robot -v OPENBMC_HOST:x.x.x.x -v IMAGE_FILE_PATH:<image path>/obmc-phosphor-image-witherspoon.ubi.mtd.tar --include REST_BMC_Code_Update bmc_code_update.robot
For host code update, download the system type *.pnor.squashfs.tar image from https://openpower.xyz/job/openpower-op-build/ and run as follows:
For Witherspoon system:
$ cd extended/code_update/ $ robot -v OPENBMC_HOST:x.x.x.x -v IMAGE_FILE_PATH:<image path>/witherspoon.pnor.squashfs.tar --include REST_Host_Code_Update host_code_update.robot
Non-UBI Format *
For BMC code update, download the system type *all.tar image from https://openpower.xyz/job/openbmc-build/ and run as follows:
For a Zaius system:
$ cd extended/code_update/ $ robot -v OPENBMC_HOST:x.x.x.x -v FILE_PATH:<image path>/zaius-<date time>.all.tar --include Initiate_Code_Update_BMC update_bmc.robot
For host code update, download the system type *.pnor from https://openpower.xyz/job/openpower-op-build/ and run as follows:
For a Zaius system:
$ cd extended/ $ robot -v OPENBMC_HOST:x.x.x.x -v PNOR_IMAGE_PATH:<image path>/zaius.pnor test_bios_update.robot