The Tests

OpTestAt24driver

At24(Atmel24) eeprom driver to support openpower platform

This driver has following functionalities:

• ‘at24’ is the i2c client driver that interface the EEPROMs on the system.

• In P8 system, EEPROM devices contain the system VPDs information and this driver is capable of reading and programming the data to these devices.

class testcases.AT24driver.AT24driver(methodName='runTest')

host_hexdump(i_dev)

The hexdump utility is used to display the specified files. This function will display in both ASCII+hexadecimal format.

Param

i_dev: this is the file used as a input to hexdump for display info

Raises

common.Exceptions.CommandFailed

runTest()

This function has following test steps

1. Getting the host infromation(OS and kernel information)

2. Loading the necessary modules to test at24 device driver functionalites (i2c_dev, i2c_opal and at24)

3. Getting the list of i2c buses and eeprom chip addresses

4. Accessing the registers visible through the i2cbus using i2cdump utility

5. Getting the eeprom device data using hexdump utility in hex + Ascii format

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.AT24driver.SkirootAT24(methodName='runTest')

Run the same AT24driver test, but in skiroot environment.

setUp()

Hook method for setting up the test fixture before exercising it.

Basic IPL and reboot tests

These can be used as tests themselves to check all IPL and reboot types, or can be invoked on the command line to boot the machine a certain way or into a specific state.

class testcases.BasicIPL.BMCReset(methodName='runTest')

Reboot the BMC with the host off. This will check that the host is also powered off when the BMC comes back.

class testcases.BasicIPL.BMCResetThenRebootHost(methodName='runTest')

Reboot the BMC with the host on and once the BMC is back, reboot the host.

class testcases.BasicIPL.BasicIPL(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.BasicIPL.BootToOS(methodName='runTest')

Boot the default Operating System on the Host.

This will force and IPL and then look to get to a login prompt.

class testcases.BasicIPL.BootToPetitboot(methodName='runTest')

Boot to the Petitboot menu. It does not cancel any automatic boot countdown sequence.

It will force the machine off first, so it will do an IPL.

class testcases.BasicIPL.BootToPetitbootShell(methodName='runTest')

Boot to the Petitboot shell (i.e. pressing ‘x’ when the petitboot menu comes up).

It will force the machine off first, so it will do an IPL.

class testcases.BasicIPL.GotoPetitbootShell(methodName='runTest')

We goto petitboot shell rather than do the off/on-to-petitboot shell so that the skiroot test suite time to run each test is a bit more accurate, rather than hiding the first IPL in the first test that’s run.

class testcases.BasicIPL.HardPowerCycle(methodName='runTest')

Get to Petitboot, then issue a hard power cycle from the BMC, checking that we can get back to Petitboot.

class testcases.BasicIPL.OutOfBandWarmReset(methodName='runTest')

Does an IPL to petitboot, and then do a ‘warm reset’, checking that we can boot back up to Petitboot.

class testcases.BasicIPL.PowerOff(methodName='runTest')

Get to Petitboot, then ask the BMC for a normal power off sequence, checking that the host did indeed power off.

class testcases.BasicIPL.SoftPowerOff(methodName='runTest')

Do a soft power off (i.e. polite, asking the OS to shut down).

BMCResetTorture

This testcase does BMC reset torture in different scenarios.

class testcases.BMCResetTorture.BMCResetvsHostIPLTorture(methodName='runTest')

Repeatedly does the BMC Reset vs Host IPL Torture

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.BMCResetTorture.Host(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.BMCResetTorture.RuntimeBMCResetTorture(methodName='runTest')

Repeatedly does the BMC Reset at runtime (i.e at both skiroot and host)

setUp()

Hook method for setting up the test fixture before exercising it.

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.BMCResetTorture.Skiroot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.BMCResetTorture.StandbyBMCResetTorture(methodName='runTest')

Repeatedly does the BMC reset at standby state

setUp()

Hook method for setting up the test fixture before exercising it.

BootTorture:

Torture the machine with repeatedly trying to boot

Sample naming conventions below, see each test method for the applicable options per method.

–run testcases.BootTorture.BootTorture

^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^

module name subclass

–run testcases.BootTorture.BootTorture10

^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^

module name subclass

class testcases.BootTorture.BootTorture(methodName='runTest')

BootTorture x1024

–run testcases.BootTorture.BootTorture

classmethod setUpClass(boot_iterations=1024)

Hook method for setting up class fixture before running tests in the class.

class testcases.BootTorture.BootTorture10(methodName='runTest')

Just boot 10 times. Just a little bit of peril.

–run testcases.BootTorture.BootTorture10

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.BootTorture.ReBootTorture(methodName='runTest')

Soft Reboot Torture - i.e. running ‘reboot’ from Petitboot shell.

–run testcases.BootTorture.ReBootTorture

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.BootTorture.ReBootTorture10(methodName='runTest')

Reboot Torture, but only 10x.

–run testcases.BootTorture.ReBootTorture10

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

Console Bug 150765

A regresion test for a specific bug observed on FSP based systems.

Make sure ipmi sol console is connected before running this test Observe sol console messages while system IPL’s for two times For second IPL, Petitboot Kernel messages will not come on active SOL console.

class testcases.ConsoleBug150765.ConsoleBug150765(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

Console tests

A bunch of really simple console tests that have managed to break every BMC implementation we’ve ever thrown it at. Since we’re highly reliant on the BMC providing a reliable host console, if these tests fail at all, then we’re likely going to get spurious failures elsewhere in the test suite.

class testcases.Console.Console

Run the full class of Console tests

–run testcases.Console

class testcases.Console.Console16k(methodName='runTest')

hexdump 16kb of zeros and check we get all the lines of hexdump output on the console.

–run testcases.Console.Console16k

class testcases.Console.Console32k(methodName='runTest')

hexdump 32kb of zeros and check we get all the lines of hexdump output on the console. The idea is that console buffers on BMCs are likely to be less than 32kb, so we’ll be able to catch any silent wrapping of it.

–run testcases.Console.Console32k

class testcases.Console.Console8k(methodName='runTest')

hexdump 8kb of zeros and check we get all the lines of hexdump output on the console.

–run testcases.Console.Console8k

class testcases.Console.ControlC(methodName='runTest')

Start a process that does a bunch of console output, and then try and ‘control-c’ it to stop the process and get a prompt back.

–run testcases.Console.ControlC

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.Console.ControlZ(methodName='runTest')

Run a console output heavy task, try to control-z it, then kill it, the try_recover logic in OpTestUtil should recover the prompt

–run testcases.Console.ControlZ

CPU Hotplug Testcase

This test case is likely to catch bugs either in the kernel or in stop states we put cores/threads into when we hot unplug them.

class testcases.CpuHotPlug.CpuHotPlug(methodName='runTest')

Use the ppc64_cpu utility to turn SMT on/off and set to each possible SMT mode, which is effectively a CPU hotplug operation. Then start hotplugging CPU cores by using the ppc64_cpu utility to turn only a specific number of cores on.

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

DeviceTreeValidation

Check a bunch of device tree properties and structure for validity, and compare device tree in host and skiroot environments.

class testcases.DeviceTreeValidation.DeviceTreeValidation(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

twos_comp(val, bits)

compute the 2’s complement of int value val

class testcases.DeviceTreeValidation.DeviceTreeValidationHost(methodName='runTest')

class testcases.DeviceTreeValidation.DeviceTreeValidationSkiroot(methodName='runTest')

DeviceTreeWarnings

Check for any warnings from tools such as dtc in our device tree.

class testcases.DeviceTreeWarnings.DeviceTreeWarnings

Look at the warnings from dtc, filtering out any known issues.

class testcases.DeviceTreeWarnings.Host(methodName='runTest')

class testcases.DeviceTreeWarnings.Skiroot(methodName='runTest')

Delayed Power Off (DPO)

Delayed Power off testcase is to test OS graceful shutdown request to be notified from OPAL and OS should process the request. We will use “ipmitool power soft” command to issue DPO.

class testcases.DPO.Base(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.DPO.DPOSkiroot(methodName='runTest')

runTest()

This will test DPO feature in skiroot and Host

EnergyScale_BaseLine

This test is somewhat re-implementing the EnergyScale_BaseLine plugin for DVT except it’s not perfect, and don’t bet that it is the same as it’s only based on a log of a test run rather than the source code for that test.

class testcases.EnergyScale_BaseLine.EnergyScale_BaseLine(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

EPOW (Emergency POWer off)

This module tests the EPOW feature incase of FSP systems.

1. EPOW3Random.

   Simulate random EPOW3 temperature to check whether OPAL notify EPOW notification to Host OS. Once Host gets notified Host should do a graceful shutdown.

2. EPOW3LOW

   Simualate temperatures less than EPOW3 threshold and check whether Host OS is alive or not.

class testcases.EPOW.EPOW3LOW(methodName='runTest')

This test case will follow below procedure:

1. Based on Nebsenabled will get EPOW limits from FSP using def file present in /opt/fips/components/engd/. Different systems have different EPOW limits.

2. Test EPOW3_LOW—> Will test temperatures lower than EPOW3 temperature, a. From FSP it simulate to lesser ambient temperatures than EPOW3 temperature b. In this case system should be alive and it should not cause system shut-down.

If user faces any problem in bringing the system UP please run below command “smgr toolReset” in fsp console

class testcases.EPOW.EPOW3Random(methodName='runTest')

This testcase tests the EPOW feature of the FSP. Thus, it is only applicable to FSP based systems and will be skipped on other BMC types.

This test will:

1. It will gather EPOW limits

2. We will choose some random EPOW temp(test_temp) in b/w those limits

3. Simulate that temperature(test_temp)

4. Verify graceful shutdown happened or not

5. Once system reaches standby, simulate the ambient temp to EPOW3_RESET temperature(reset_temp) to bring back the system.

6. Bring back the system again to runtime.

If user faces any problem in bringing the system UP please run below command “smgr toolReset”

class testcases.EPOW.EPOWBase(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

fspresetReload

• FSP initiated reset

• Host initiated reset

• Once reset is done, verify host-fsp firmware interfaces

class testcases.fspresetReload.FIR(methodName='runTest')

class testcases.fspresetReload.FIRTorture(methodName='runTest')

class testcases.fspresetReload.HIR(methodName='runTest')

class testcases.fspresetReload.HIRTorture(methodName='runTest')

class testcases.fspresetReload.SIR(methodName='runTest')

class testcases.fspresetReload.SIRTorture(methodName='runTest')

class testcases.fspresetReload.fspresetReload(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

class testcases.fspresetReload.resetReload(methodName='runTest')

FSP TOD Corruption

Corrupt TOD and check host boot and runtime behaviours

class testcases.fspTODCorruption.TOD_CORRUPTION(methodName='runTest')

This function tests Boot and runtime behaviour when TOD is corrupted.

FWTS

Run the Canonical FirmWare Test Suite (FWTS, see https://wiki.ubuntu.com/FirmwareTestSuite for details).

Largely, if we can implement a test as part of FWTS, we should do it there as it’s easy to run and packaged.

class testcases.FWTS.FWTS(tests=())

Run the FWTS tests, importing the test results into op-test.

This is implemented as a TestSuite rather than a TestCase so we can add multiple TestCase results to the op-test test results.

class testcases.FWTS.FWTSCommandFailed(methodName='runTest')

class testcases.FWTS.FWTSCommandSkipped(methodName='runTest')

class testcases.FWTS.FWTSTest(methodName='runTest')

class testcases.FWTS.FWTSVersion(methodName='runTest')

gcov

A “Test Case” for extracting GCOV code coverage data from skiboot. The real use of this test case and code is to help construct code coverage reports for skiboot.

class testcases.gcov.Host(methodName='runTest')

Extract GCOV code coverage from a host OS.

class testcases.gcov.Skiroot(methodName='runTest')

Extract GCOV code coverage in skiroot environment.

class testcases.gcov.gcov

Base “test case” for extracting skiboot GCOV code coverage data from the host (use the Skiroot and Host TestCases for running this code).

This requires a GCOV build of skiboot.

We (rather convolutedly) do a HTTP POST operation (through shell!) back to the op-test process as since we may be running in skiroot, we don’t have all the nice usual ways of transferring files around. The good news is that implementing a simple HTTP POST request in shell isn’t that hard.

HelloWorld

A really simple Hello World test, just to check that we can run a test case.

Only useful as a unittest of op-test itself.

class testcases.HelloWorld.HelloWorld(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

I2C tests

This class will test functionality of following drivers: I2C Driver(Inter-Integrated Circuit) driver

class testcases.I2C.BasicI2C(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.I2C.BasicSkirootI2C(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.I2C.FullI2C(methodName='runTest')

This test has following test steps:

1. Getting host information(OS and kernel info)

2. Checking the required utilites are present on host or not

3. Loading the necessary modules to test I2C device driver functionalites (i2c_dev, i2c_opal and at24)

4. Getting the list of i2c buses

5. Querying the i2c bus for devices

6. Getting the list of i2c buses and eeprom chip addresses

7. Accessing the registers visible through the i2cbus using i2cdump utility

8. Listing the i2c adapter conetents and i2c bus entries to make sure sysfs entries created for each bus.

9. Testing i2cget functionality for limited samples

Avoiding i2cset functionality, it may damage the system.

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.I2C.I2C

Base class for I2C tests

host_get_info_of_eeprom_chips()

This function will get information of EEPROM chips attached to the i2c buses

Returns

str EEPROM chips information

Raises

common.Exceptions.CommandFailed

host_get_list_of_eeprom_chips()

It will return list with elements having pairs of eeprom chip addresses and corresponding i2c bus where the chip is attached. This information is getting through sysfs interface. format is

["0 0x50","0 0x51","1 0x51","1 0x52"....]

Returns

list – list having pairs of i2c bus number and eeprom chip address.

Raises

common.Exceptions.CommandFailed

host_get_list_of_i2c_buses()

This function will return the list of installed i2c buses on host in two formats:

list-by number, e.g.

["0","1","2",....]

list-by-name, eg

["i2c-0","i2c-1","i2c-2"....]

Returns

(l_list, l_list1) : list of i2c buses by number, list of i2c buses by name

Raises

common.Exceptions.CommandFailed

host_hexdump(i_dev)

The hexdump utility is used to display the specified files. This function will display in both ASCII+hexadecimal format.

Param

i_dev: this is the file used as a input to hexdump for display info

Raises

common.Exceptions.CommandFailed

i2c_dump(i_args)

This i2cdump function takes arguments in pair of a string like “i2cbus address”. i2cbus indicates the number or name of the I2C bus to be scanned. This number should correspond to one of the busses listed by i2cdetect -l. address indicates the address to be scanned on that bus, and is an integer between 0x03 and 0x77 i2cdump is a program to examine registers visible through the I2C bus.

The command may fail due to problems with the device, hardware, or firmware.

Parameters

i_args (str) – this is the argument to i2cdump utility. Arguments are in the form of “i2c-bus-number eeprom-chip-address” e.g. 0 0x51, 3 0x52

i2c_get(i_args, i_addr)

This function i2cget read from I2C/SMBus chip registers.

command usage:

i2cget [-f] [-y] i2cbus chip-address [data-address [mode]]

Parameters

• i_args (str) – this is the argument to i2cget utility. Arguments are in the form of “i2c-bus-number eeprom-chip-address” e.g. 0 0x51, 3 0x52

• i_addr – this is the data-address on chip, from where data will be read. e.g. “0x00”,”0x10”,”0x20”…

Returns

data present on data-address

i2c_set(i_args, i_addr, i_val)

This function i2cset will be used for setting I2C registers.

command usage:

i2cset [-f] [-y] [-m mask] [-r] i2cbus chip-address data-address [value] ...  [mode]

Parameters

• i_args (str) – this is the argument to i2cset utility. Arguments are in the form of “i2c-bus-number eeprom-chip-address” e.g. 0 0x51, 3 0x52 ….etc

• i_addr (str) – this is the data-address on chip, where data will be set e.g. 0x00”,”0x10”,”0x20”…

• i_val (str) – this is the value which will be set into data-address i_addr

query_i2c_bus(i_bus)

This function query’s the i2c bus for devices attached to it. i2cdetect is a utility to scan an I2C bus for devices

Param

i_bus: i2c bus numer

Raises

common.Exceptions.CommandFailed

exception testcases.I2C.I2CDetectUnsupported

Asked to do i2c detect on a bus that doesn’t support detection

Install HostOS

Installs HostOS on the host.

class testcases.InstallHostOS.InstallHostOS(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

Install RHEL

Installs RedHat Enterprise Linux (RHEL) on the host.

class testcases.InstallRhel.InstallRhel(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

Install Ubuntu

Installs Ubuntu on the host.

The idea behind this test is to both set up an OS suitable to run op-test against and check our backwards compatibility with installation media.

class testcases.InstallUbuntu.InstallUbuntu(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.InstallUbuntu.MyIPfromHost(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

IPL Params

This test verifies certain fw features are enabled/disabled during IPL time as per expectation. These features will control run time enablement of certain components.

class testcases.IplParams.Host(methodName='runTest')

class testcases.IplParams.Skiroot(methodName='runTest')

IPMI Torture

Use several threads in op-test to poke IPMI concurrently in a number of “safe” ways, and see when the BMC explodes.

class testcases.IpmiTorture.ConsoleIpmiTorture(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

class testcases.IpmiTorture.InbandIpmiThread(threadID, name, ipmi_method, cmd, execution_time)

run()

Method representing the thread’s activity.

You may override this method in a subclass. The standard run() method invokes the callable object passed to the object’s constructor as the target argument, if any, with sequential and keyword arguments taken from the args and kwargs arguments, respectively.

class testcases.IpmiTorture.IpmiInterfaceTorture(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

class testcases.IpmiTorture.OobIpmiThread(threadID, name, cmd, execution_time)

run()

Method representing the thread’s activity.

You may override this method in a subclass. The standard run() method invokes the callable object passed to the object’s constructor as the target argument, if any, with sequential and keyword arguments taken from the args and kwargs arguments, respectively.

class testcases.IpmiTorture.RuntimeConsoleTorture(methodName='runTest')

class testcases.IpmiTorture.RuntimeIpmiInterfaceTorture(methodName='runTest')

class testcases.IpmiTorture.SkirootConsoleTorture(methodName='runTest')

class testcases.IpmiTorture.SkirootIpmiTorture(methodName='runTest')

class testcases.IpmiTorture.SolConsoleThread(threadID, name, test, execution_time)

run()

Method representing the thread’s activity.

You may override this method in a subclass. The standard run() method invokes the callable object passed to the object’s constructor as the target argument, if any, with sequential and keyword arguments taken from the args and kwargs arguments, respectively.

class testcases.IpmiTorture.StandbyConsoleTorture(methodName='runTest')

class testcases.IpmiTorture.StandbyIpmiInterfaceTorture(methodName='runTest')

Kernel Log

Check the Linux kernel log in skiroot and the OS for warnings and errors, filtering for known benign problems (or problems that are just a Linux issue rather than a firmware issue).

class testcases.KernelLog.Host(methodName='runTest')

class testcases.KernelLog.Skiroot(methodName='runTest')

LightPathDiagnostics

Currently runs only in FSP platforms.

class testcases.LightPathDiagnostics.LightPathDiagnostics(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.LightPathDiagnostics.UsysAttnFSPTest(methodName='runTest')

This function tests system attention indicator LED

class testcases.LightPathDiagnostics.UsysAttnHostTest(methodName='runTest')

This function tests system attention indicator LED

class testcases.LightPathDiagnostics.UsysFaultTest(methodName='runTest')

This function tests usysfault identification of LED’s

class testcases.LightPathDiagnostics.UsysIdentifyTest(methodName='runTest')

This function tests usysident identification of LEDs

OpalErrorLog

Tests the OPAL error log functionality (as in PELs, not OPAL’s log).

Currently runs only in FSP platforms

class testcases.OpalErrorLog.BasicTest(methodName='runTest')

class testcases.OpalErrorLog.FullTest(methodName='runTest')

class testcases.OpalErrorLog.OpalErrorLog(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpalErrorLog.TortureTest(methodName='runTest')

opal-gard

Test different OPAL GARD Related functionality

class testcases.OpalGard.OpalGard(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

OPAL log test

Look for boot and runtime warnings and errors from OPAL (skiboot).

We filter out any “known errors”, such as how PRD can do invalid SCOMs but that it’s not an error error.

class testcases.OpalMsglog.Host(methodName='runTest')

class testcases.OpalMsglog.Skiroot(methodName='runTest')

OPAL sysfs Tests

This pokes a few bits of functionality accessible through sysfs that OPAL provides.

It includes:

• System powercaps, i.e. /sys/firmware/opal/powercap/

• Power Shift Ratio, i.e. /sys/firmware/opal/psr

• Sensor Groups, i.e. /sys/firmware/opal/sensor_groups/

• The OPAL symbol map, i.e. /sys/firmware/opal/symbol_map

• Exporting of random bits of memory, i.e. /sys/firmware/opal/exports/

class testcases.OpalSysfsTests.Host(methodName='runTest')

class testcases.OpalSysfsTests.Skiroot(methodName='runTest')

OpalUtils

Test different OPAL Utilities:

• getscom

• putscom

• gard

• pflash

class testcases.OpalUtils.OpalUtils(methodName='runTest')

runTest()

This testcase performs below steps:

1. SCOM Read operation

2. SCOM Write operation

3. List Gard records operation

4. Clear Gard records operation

5. pflash info operation

6. pflash read part operation

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestCAPI

CAPI tests for OpenPower testing.

This class will test the functionality of CAPI

Prerequisites:

1. Host must have a CAPI FPGA card

2. CAPI card must have been flashed with memcpy AFU

Extra timebase sync tests prerequisite:

3. PSL must support timebase sync

class testcases.OpTestCAPI.CxlDeviceFileTest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl module if required and check that the cxl device files afu0.0m and afu0.0s exist

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.CxlResetTest(methodName='runTest')

If a given system has a CAPI FPGA card, then load the cxl module if required, and test reset with cxl_eeh_tests.sh and memcpy_afu_ctx.

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.KernelAPITest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl and the cxl_memcpy modules if required, and test the kernel API of memcpy with memcpy_afu_ctx -K.

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.MemCpyAFUIrqTest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl module if required and test the memcpy AFU with memcpy_afu_ctx -i

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.MemCpyAFUReallocTest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl module if required and test the memcpy AFU with memcpy_afu_ctx -r

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.MemCpyAFUTest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl module if required and test the memcpy AFU with memcpy_afu_ctx

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.OpTestCAPI(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.SysfsABITest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl module if required and run the sysfs ABI tests from libcxl_tests

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestCAPI.TimeBaseSyncTest(methodName='runTest')

If a given system has a CAPI FPGA card, then this test load the cxl module if required and also check if the card PSL supports timebase sync. If it supports it, then test timebase sync with memcpy_afu_ctx -t

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestDumps

Different dumps for fsp platforms:

• fipsdump

• system dump

  host_dump_boottime

  Trigger dump when kernel boots(either Petitboot or OS kernel)

  host_dump_runtime

  Trigger dump when system is in OS or already booted to OS

  nmi_dump

  Trigger system dump by sending NMI interrupts to processors

class testcases.OpTestDumps.FIPS_DUMP(methodName='runTest')

class testcases.OpTestDumps.HOST_DUMP_BOOTTIME(methodName='runTest')

class testcases.OpTestDumps.HOST_DUMP_RUNTIME(methodName='runTest')

class testcases.OpTestDumps.NMI_DIAG_DUMP(methodName='runTest')

class testcases.OpTestDumps.SYSTEM_DUMP(methodName='runTest')

This function tests system dump functionality

1. Boot the system to runtime(Atleast to petitboot)

2. Trigger system dump from FSP

3. Wait for dump to finish & IPL to reach runtime

4. Check for system dump files in host

OpTestEEH

This testcase basically tests all OPAL EEH Error injection tests.

• fenced PHB

• frozen PE

exception testcases.OpTestEEH.EEHLocCodeFailed(thing, dev, log=None)

Failed to log location code along with failure.

exception testcases.OpTestEEH.EEHRecoveryFailed(thing, dev, log=None)

EEH Recovery failed on thing for reason.

exception testcases.OpTestEEH.EEHRemoveFailed(thing, dev, log=None)

EEH Remove failed on thing for reason.

class testcases.OpTestEEH.OpTestEEH(methodName='runTest')

check_eeh_pe_recovery(pe)

return True if PE is available in the system else return False. Which will be useful for checking the PE after injecting the EEH error

check_eeh_phb_recovery(i_domain)

This function is used to actually check the PHB recovery after an EEH Fenced PHB Error Injection.

We scrape the kernel log for the correct strings.

check_eeh_slot_resets()

Check for EEH Slot Reset count. i.e.

$ cat /proc/powerpc/eeh | tail -n 1
eeh_slot_resets=10

Returns integer (in above example ‘10’).

gather_logs()

This function is used to gather opal and kernel logs for each EEH iteration instead of full logs.

This should make it easier to debug problems as you’ll have the specific log messages that occured for each test.

get_dic_of_pe_vs_addr()

Get dictionary of pe vs config addr. e.g.

{'0001:0c:00.2': '2', '0001:0b:00.0': 'fb', '0001:0c:00.0': '2'}

get_list_of_pci_devices()

This function is used to get list of PCI devices available at that instant of time.

inject_error(addr, e, f, phb, pe)

Inject error:

addr

PE address

e

0

32 bit errors

1

64 bit errors

f (Function)

0

MMIO read

4

CFG read

6

MMIO write

10

CFG write

phb

PHB Index

pe

PE BDF address

prepare_logs()

This function is used to prepare opal and kernel logs to a reference point, so that we can compare logs for each EEH iteration easily.

Basically, we throw logs in a temp file and diff them afterwards.

run_pe_4(addr, e, f, phb, pe, con)

Inject error and check for recovery, finally gather logs.

Returns True if PE recovers, False if failed to recover.

setUp()

Hook method for setting up the test fixture before exercising it.

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

set_con_log_lev_crit()

EEH verbose is enabled in P9. Until we have a capable of setting console log level in runtime, or EEH verbose is disabled in P9, we need to disable the console logging to make tests run. (But at the cost of one additional IPL execution overhead)

TODO: Remove this once we have a way of disabling console log level in runtime without having an additional IPL.

class testcases.OpTestEEH.OpTestEEHbasic_fenced_phb(methodName='runTest')

This testcase has below steps:

1. Get the list of pci PHB domains

2. Get the root PHB domain where the root file system is installed(We need to skip this as EEH recovery will fail on root PHB).

3. Start injecting the fenced PHB errors in a for loop Only one time basic check whether PHB recovered or not

class testcases.OpTestEEH.OpTestEEHbasic_frozen_pe(methodName='runTest')

This testcase has below steps

1. Get the list of pci PHB domains

2. Get the root PHB domain where the root file system is installed(We need to skip this as EEH recovery will fail on root PHB).

3. get dictionary of pe vs config addr.

   Ex:

   {'0001:0c:00.2': '2', '0001:0b:00.0': 'fb', '0001:0c:00.0': '2'}
   

4. Prepare below command & Start inject frozenPE errors on all PE’s

   echo "PE_number:<0,1>:<function>:0:0" > /sys/kernel/debug/powerpc/PCIxxxx/err_injct
   

5. Gather necssary logs(dmesg & OPAL) and check the device(PE) got recovered or not.

class testcases.OpTestEEH.OpTestEEHmax_fenced_phb(methodName='runTest')

This testcase has below steps:

1. Get the list of pci PHB domains

2. Get the root PHB domain where the root file system is installed(We need to skip this as EEH recovery will fail on root PHB).

3. Set the MAX EEH Freeze count to 1 so that we can test max EEH Recovery capacity within less for loop executions By default it is 6,

4. Start injecting the fenced PHB errors two times across all PHB domains except root PHB.( As we set max EEH Freeze count to 1). So expectation is first time it should recover and second time EEH should properly remove the device and OS should not crash.

class testcases.OpTestEEH.OpTestEEHmax_frozen_pe(methodName='runTest')

This testcase has below steps

1. Get the list of pci PHB domains

2. Get the root PHB domain where the root file system is installed(We need to skip this as EEH recovery will fail on root PHB).

3. get dictionary of pe vs config addr. Ex:

   {'0001:0c:00.2': '2', '0001:0b:00.0': 'fb', '0001:0c:00.0': '2'}
   

4. Prepare below command & Start inject frozenPE errors on all PE’s

   echo "PE_number:<0,1>:<function>:0:0" > /sys/kernel/debug/powerpc/PCIxxxx/err_injct
   

5. Gather necssary logs(dmesg & OPAL) and check the device(PE) got recovered or not.

OpTestEM

Energy Management package for OpenPower testing.

This class will test the functionality of following drivers:

1. powernv cpuidle driver

2. powernv cpufreq driver

class testcases.OpTestEM.cpu_boost_freqs_host(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.cpu_freq_gov_host(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.cpu_freq_gov_skiroot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.cpu_freq_states_host(methodName='runTest')

This test will cover following test steps:

1. Check the cpupower utility is available in host.

2. Get available cpu scaling frequencies

3. Set the userspace governer for all cpu’s

4. test the cpufreq driver by set/verify cpu frequency

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.cpu_freq_states_skiroot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.cpu_idle_states_host(methodName='runTest')

This test will cover following test steps:

1. It will get the OS and kernel versions.

2. Check the cpupower utility is available in host.

3. Set the userspace governer for all cpu’s

4. test the cpuidle driver by enable/disable/verify the idle states

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.cpu_idle_states_skiroot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEM.slw_info(methodName='runTest')

This test just gathers the host CPU SLW info.

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestEnergyScale

While OpTestEM is concerned with runtime energy management such as CPU frequency scaling and stop states, OpTestEnergyScale is concerned with system level power consumption limits.

class testcases.OpTestEnergyScale.OpTestEnergyScale(methodName='runTest')

get_platform_power_limits(i_platform)

Get platform power limits. This is a hardcoded list for each platform type. We do not (yet) have a way to determine this dynamically.

Returns a tuple of low_limit,high_limit.

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestEnergyScale.OpTestEnergyScaleDCMIruntime(methodName='runTest')

class testcases.OpTestEnergyScale.OpTestEnergyScaleDCMIstandby(methodName='runTest')

Test below dcmi commands at both standby and runtime states

ipmitool dcmi discover         # This command is used to discover supported  capabilities in DCMI.
ipmitool dcmi power reading    # Get power related readings from the system.
ipmitool dcmi power get_limit  # Get the configured power limits.
ipmitool dcmi power sensors    # Prints the available DCMI sensors.
ipmitool dcmi get_temp_reading # Get Temperature Sensor Readings.
ipmitool dcmi get_mc_id_string # Get management controller identifier string.
ipmitool dcmi get_conf_param   # Get DCMI Configuration Parameters.
ipmitool dcmi oob_discover     # Ping/Pong Message for DCMI Discovery.

class testcases.OpTestEnergyScale.OpTestEnergyScaleRuntime(methodName='runTest')

Test Energy scale features at runtime:

1. Power OFF the system.

2. Power On the system to boot to host OS

3. Validate below Energy scale features at runtime state

   ipmitool dcmi power get_limit                # Get the configured power limits.
   ipmitool dcmi power set_limit limit <value>  # Power Limit Requested in Watts.
   ipmitool dcmi power activate                 # Activate the set power limit.
   ipmitool dcmi power deactivate               # Deactivate the set power limit.
   

4. Once platform power limit activated execute below dcmi commands at runtime state.

   ipmitool dcmi discover                       # This command is used to discover supported  capabilities in DCMI.
   ipmitool dcmi power reading                  # Get power related readings from the system.
   ipmitool dcmi power get_limit                # Get the configured power limits.
   ipmitool dcmi power sensors                  # Prints the available DCMI sensors.
   ipmitool dcmi get_temp_reading               # Get Temperature Sensor Readings.
   

5. Issue Power OFF/ON to check whether system boots after setting platform power limit at runtime.

6. Again in runtime execute all dcmi commands to check the functionality.

class testcases.OpTestEnergyScale.OpTestEnergyScaleStandby(methodName='runTest')

This test will test Energy scale features at standby state:

1. Power OFF the system.

2. Validate below Energy scale features at standby state

   ipmitool dcmi power get_limit                # Get the configured power limits.
   ipmitool dcmi power set_limit limit <value>  # Power Limit Requested in Watts.
   ipmitool dcmi power activate                 # Activate the set power limit.
   ipmitool dcmi power deactivate               # Deactivate the set power limit.
   

3. Once platform power limit activated execute below dcmi commands at standby state.

   ipmitool dcmi discover                       # This command is used to discover supported  capabilities in DCMI.
   ipmitool dcmi power reading                  # Get power related readings from the system.
   ipmitool dcmi power get_limit                # Get the configured power limits.
   ipmitool dcmi power sensors                  # Prints the available DCMI sensors.
   ipmitool dcmi get_temp_reading               # Get Temperature Sensor Readings.
   

4. Power ON the system.

5. Check after system booted to runtime, whether occ’s are active or not.

6. Again in runtime execute all dcmi commands to check the functionality.

OpTestExample: An example test case

This test case is meant to show a few best practices for writing a test case for op-test.

class testcases.OpTestExample.HostBasicCheck(methodName='runTest')

Class for Host based tests This class allows –run testcases.OpTestExample.HostBasicCheck

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestExample.OpTestExample(methodName='runTest')

This class is a demo to illustrate framework.

HostVersions()

Execute commands on target OS Key Sort in OPDemoFunc for order of execution

OPComboTest()

Execute commands on target OS Key Sort in OPDemoFunc for order of execution

OPDemoFunc(op_dictionary)

Process a command table

OPMisc()

Execute commands on target OS Key Sort in OPDemoFunc for order of execution

PetitbootVersions()

Execute commands on target OS Key Sort in OPDemoFunc for order of execution

setUp(my_connect='ipmi')

Hook method for setting up the test fixture before exercising it.

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.OpTestExample.SkirootBasicCheck(methodName='runTest')

Class for Skiroot based tests This class allows –run testcases.OpTestExample.SkirootBasicCheck

setUp()

Hook method for setting up the test fixture before exercising it.

testcases.OpTestExample.host_full_suite()

Function used to prepare a test suite (see op-test) This allows –run-suite example Tests run in order

testcases.OpTestExample.host_suite()

Function used to prepare a test suite (see op-test) This allows –run-suite example Tests run in order

testcases.OpTestExample.skiroot_full_suite()

Function used to prepare a test suite (see op-test) This allows –run-suite example Tests run in order

testcases.OpTestExample.skiroot_suite()

Function used to prepare a test suite (see op-test) This allows –run-suite example Tests run in order

OpTestFastReboot

Issue fast reboot in petitboot and host OS, on a system having skiboot 5.4 rc1(which has fast-reset feature). Any further tests on fast-reset system will be added here.

class testcases.OpTestFastReboot.FastRebootHost(methodName='runTest')

class testcases.OpTestFastReboot.FastRebootHostStress(methodName='runTest')

class testcases.OpTestFastReboot.FastRebootHostStressTorture(methodName='runTest')

class testcases.OpTestFastReboot.FastRebootHostTorture(methodName='runTest')

class testcases.OpTestFastReboot.FastRebootTorture(methodName='runTest')

class testcases.OpTestFastReboot.OpTestFastReboot(methodName='runTest')

runTest()

This function tests fast reset of power systems. It will check booting sequence when reboot command getting executed in both petitboot and host OS

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestHeartbeat

Heartbeat tests for OpenPower testing.

This class will test the functionality of ipmi heartbeat

1. kopald service should be running by defaulut since host should poll OPAL at time interval requested by OPAL

class testcases.OpTestHeartbeat.HeartbeatHost(methodName='runTest')

class testcases.OpTestHeartbeat.HeartbeatSkiroot(methodName='runTest')

Checks that kopald is running. This doesn’t really test that the ipmi heartbeat is working, and thus this is a big FIXME.

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestHMIHandling

HMI Handling package for OpenPower testing.

This class will test the functionality of following.

1. HMI Non-recoverable errors - Core checkstop and Hypervisor resource error

2. HMI Recoverable errors- proc_recv_done, proc_recv_error_masked and proc_recv_again

3. TFMR error injections

4. chip TOD error injections

class testcases.OpTestHMIHandling.ClearGard(methodName='runTest')

class testcases.OpTestHMIHandling.HMI_TFMR_ERRORS(methodName='runTest')

class testcases.OpTestHMIHandling.HypervisorResourceError(methodName='runTest')

class testcases.OpTestHMIHandling.MalfunctionAlert(methodName='runTest')

class testcases.OpTestHMIHandling.OpTestHMIHandling(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.OpTestHMIHandling.PROC_RECOV_DONE(methodName='runTest')

class testcases.OpTestHMIHandling.PROC_RECV_ERROR_MASKED(methodName='runTest')

class testcases.OpTestHMIHandling.SingleCoreTOD_ERRORS(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestHMIHandling.TOD_ERRORS(methodName='runTest')

OpTestInbandIPMI

Test the inband ipmi{OPEN Interface} fucntionality package for OpenPower platform.

This class will test the functionality of following commands

1. bmc, channel, chassis, dcmi, echo, event, exec, firewall, fru, lan mc, pef, power, raw, sdr, sel, sensor, session, user

class testcases.OpTestInbandIPMI.BasicInbandIPMI(methodName='runTest')

setUp(ipmi_method='ipmitool ')

Hook method for setting up the test fixture before exercising it.

test_sensor_list()

Run a fast and simple test (on IPMI sensors) to test base functionality of the inband IPMI interface.

This test is designed an a smoke test rather than for completeness.

class testcases.OpTestInbandIPMI.ExperimentalInbandIPMI(methodName='runTest')

setUp(ipmi_method='ipmitool ')

Hook method for setting up the test fixture before exercising it.

test_Info()

It will execute and test the ipmi <sdr/sel/mc/channel> info related commands.

Currently in the Experimental pool as the “ipmitool BLAH info” commands seem to have random return codes, so failure is common.

test_channel()

It will check basic channel functionalities: info and authentication capabilities.

class testcases.OpTestInbandIPMI.OpTestInbandIPMI(methodName='runTest')

A more complete test of inband IPMI functionality.

sensor_byid(i_sensor='Host Status')

It will execute and test the ipmi sensor get <id> functionality

Parameters

i_sensor (str) – sensor ID to retrieve data from

setUp(ipmi_method='ipmitool ')

Hook method for setting up the test fixture before exercising it.

test_chassis_bootdev()

It will execute and test the functionality of ipmi chassis bootdev <dev> where dev is none,pxe,cdrom,disk,bios,safe,diag,floppy, and none.

See the implementation for how nothing is as simple as it seems and we need weird exceptions.

test_chassis_identifytests()

It will execute and test the ipmi chassis identify commands

test_dcmi()

It will execute and test the dcmi related ipmi commands.

discover

This command is used to discover supported capabilities in DCMI

Power reading

Get power related readings from the system.

get_limit

Get the configured power limits.

sensors

Prints the available DCMI sensors.

get_mc_id_string

Get management controller identifier string

get_temp_reading

Get Temperature Sensor Readings.

get_conf_param

Get DCMI Configuration Parameters.

oob_discover

Ping/Pong Message for DCMI Discovery

test_echo()

It will execute and test the functionality of ipmi echo command.

test_event()

It will execute and test event related commands to test sel functionality.

Send a pre-defined test event to the System Event Log. The following events are included as a means to test the functionality of the System Event Log component of the BMC (an entry will be added each time the event N command is executed)

Currently supported values for N are:

1. Temperature: Upper Critical: Going High

2. Voltage Threshold: Lower Critical: Going Low

3. Memory: Correctable ECC

test_exec()

It will execute and test ipmi exec command.

FIXME: not yet implemented.

test_firewall()

It will execute and test firmware firewall info command.

test_fru_print()

It will execute and test the ipmi fru print command.

test_fru_read()

It will execute and test the ipmi fru read command. then the output file is displayed by hexdump

A FIXME is to check the content of the FRU for sanity.

test_mc()

It will execute and test the management controller(mc) commands functionality.

info

Displays information about the BMC hardware, including device revision, firmware revision, IPMI version supported, manufacturer ID, and information on additional device support.

watchdog get

Show current Watchdog Timer settings and countdown state.

watchdog off

Turn off a currently running Watchdog countdown timer.

watchdog reset

Reset the Watchdog Timer to its most recent state and restart the countdown timer.

selftest

Check on the basic health of the BMC by executing the Get Self Test results command and report the results.

setenables

Enables or disables the given option

getenables

Displays a list of the currently enabled options for the BMC.

getsysinfo

Retrieves system info from bmc for given argument

test_pef()

It will execute and test pef related commands:

info

This command will query the BMC and print information about the PEF supported features.

status

This command prints the current PEF status

policy

This command lists the PEF policy table entries

list

This command lists the PEF table entries.

test_raw()

This will test raw IPMI commands. For example to query the POH counter with a raw command.

Practically speaking, this tests ipmitool itself more than any firmware or OS functionality (when compared to the non-raw test).

test_sdr_elist_by_type()

It will execute and test the commands: ipmi sdr elist <all/fru/event/mcloc/compact/full/generic>

test_sdr_get_id()

It will execute and test the ipmi sdr get <sensor-id> command

test_sdr_list_by_type()

It will execute and test the ipmi sdr list <all/fru/event/mcloc/compact/full/generic>

test_sdr_type_list()

It will execute and test the ipmi sdr type <Temp/fan/Powersupply> commands

test_sel_clear()

It will execute the ipmi sel clear command.

Not all BMCs support this (notably simulators such as Qemu). In that case, we try anyway and skip the test rather than fail.

test_sel_clear_functionality()

It will execute and test the ipmi sel clear functionality.

test_sel_elist()

It will execute and test the ipmi sel elist functionality If invoked as elist (extended list) it will also use the Sensor Data Record entries to display the sensor ID for the sensor that caused each event.

test_sel_get_functionality()

It will execute and test the ipmi sel get <id> functionality.

test_sel_info()

It will execute and test the ipmi sel info functionality

test_sel_list()

It will execute and test ipmi sel list functionality. the entire contents of the System Event Log are displayed.

test_sel_list_first_3_entries()

It will execute and test the ipmi sel list first <3 entries>

test_sel_list_first_n_entries(i_num=1)

It will execute and test the ipmi sel list first <n entries>

Parameters

i_num (int) – The number of SELs to list

test_sel_list_last_3_entries()

It will execute and test the ipmi sel list last <3 entries>

test_sel_list_last_n_entries(i_num=1)

It will execute and test the ipmi sel list last <n entries>

Parameters

i_num (int) – The number of last SEL entries to list.

test_sel_set_time()

It will execute and test the ipmi sel set <time string> functionality Sets the SEL clock. Future SEL entries will use the time set by this command.

test_sel_time_get()

It will execute and test the ipmi sel time get functionality Displays the SEL clock’s current time.

test_sensor_get_host_status()

It will execute and test the ipmi sensor get “Host Status” functionality.

Not all BMCs support this sensor, so if we think a BMC doesn’t, and it fails, we skip the test rather than failing it.

test_sensor_get_occ_active()

It will execute and test the ipmi sensor get “OCC Active” functionality

test_sensor_get_os_boot()

It will execute and test the ipmi sensor get “OS Boot” functionality.

If the BMC doesn’t support the ‘OS Boot’ sensor, we try anyway and skip the test.

class testcases.OpTestInbandIPMI.SkirootBasicInbandIPMI(methodName='runTest')

setUp(ipmi_method='ipmitool ')

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestInbandIPMI.SkirootFullInbandIPMI(methodName='runTest')

setUp(ipmi_method='ipmitool ')

Hook method for setting up the test fixture before exercising it.

exception testcases.OpTestInbandIPMI.UnexpectedBootDevice(expected, actual)

OpTestInbandUsbInterface

Test the inband ipmi{USB Interface} fucntionality package for OpenPower platform.

This class will test the functionality of following commands

1. bmc, channel, chassis, dcmi, echo, event, exec, firewall, fru, lan mc, pef, power, raw, sdr, sel, sensor, session, user

It is all the same tests as testcases.OpTestInbandIPMI but using the USB interface rather than BT.

class testcases.OpTestInbandUsbInterface.BasicInbandUSB(methodName='runTest')

setUp(ipmi_method='ipmitool -I usb ')

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestInbandUsbInterface.ExperimentalInbandUSB(methodName='runTest')

setUp(ipmi_method='ipmitool -I usb ')

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestInbandUsbInterface.InbandUSB(methodName='runTest')

setUp(ipmi_method='ipmitool -I usb ')

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestInbandUsbInterface.SkirootBasicInbandUSB(methodName='runTest')

setUp(ipmi_method='ipmitool -I usb ')

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestInbandUsbInterface.SkirootInbandUSB(methodName='runTest')

setUp(ipmi_method='ipmitool -I usb ')

Hook method for setting up the test fixture before exercising it.

OpTestIPMILockMode

It will test in-band ipmi white-listed commands when ipmi is in locked mode

IPMI whitelist These are the commands that will be available over an unauthenticated interface when the BMC is in IPMI lockdown mode.

Generally one can access all in-band ipmi commands, But if we issue ipmi lock command then one can access only specific whitelisted in-band ipmi commands.

class testcases.OpTestIPMILockMode.OpTestIPMILockMode(methodName='runTest')

This test case will cover following test steps:

1. It will get the OS level installed on power platform

2. It will check for kernel version installed on the Open Power Machine

3. It will check for ipmitool command existence and ipmitool package

4. Load the necessary ipmi modules based on config values

5. Issue a ipmi lock command through out-of-band authenticated interface

6. Now BMC IPMI is in locked mode, at this point only white listed in-band ipmi commands sholud work(No other in-band ipmi command should work)

7. Execute and test the functionality of whitelisted in-band ipmi commands in locked mode

8. At the end of test issue a ipmi unlock command to revert the availablity of all in-band ipmi commands in unlocked mode.

run_inband_ipmi_whitelisted_cmds()

This function will execute whitelisted in-band ipmi commands and test the functionality in locked mode.

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestIPMIReprovision

ResetReprovision to default package for OpenPower testing.

This class will test the functionality of following ResetReprovision to default tests.

1. NVRAM Partition - IPMI Reprovision.

2. GARD Partition - IPMI Reprovision.

class testcases.OpTestIPMIReprovision.GARD(methodName='runTest')

This function will cover following test steps

Testcase: GARD Partition-IPMI Reprovision

1. Inject core checkstop using existed function from OpTestHMIHandling.py

2. Do a Hard reboot(IPMI Power OFF/ON)

3. Issue an IPMI PNOR Reprovision request command, to reset GUARD partition to default.

4. Wait for IPMI PNOR Reprovision progress to complete(00).

5. Check for GUARD parition whether the existing gard records erased or not.

6. Reboot the system back to see system is booting fine or not.

class testcases.OpTestIPMIReprovision.NVRAM(methodName='runTest')

This function will cover following test steps

Testcase: NVRAM Partition-IPMI Reprovision

1. Update NVRAM config data with test config data i.e nvram –update-config test-name=test-value

2. Issue an IPMI PNOR Reprovision request command, to reset NVRAM partition to default.

3. Wait for PNOR Reprovision progress to complete(00).

4. Do a Hard reboot(Power OFF/ON) to avoid nvram cache data.

5. Once system booted, check for NVRAM parition whether the test config data got erased or not.

class testcases.OpTestIPMIReprovision.OpTestIPMIReprovision(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestMtdPnorDriver

Test MTD PNOR Driver package for OpenPower testing.

Warning

This has been migrated along with other tests but never used in earnest. It is likely we could accomplish all of this on the host itself. I severely doubt this test case currently works as intended.

class testcases.OpTestMtdPnorDriver.OpTestMtdPnorDriver(methodName='runTest')

This function has following test steps

1. Get host information(OS and Kernel information)

2. Load the mtd module based on config value

3. Check /dev/mtd0 character device file existence on host

4. Copying the contents of the flash in a file /tmp/pnor

5. Getting the /tmp/pnor file into local x86 machine using scp utility

6. Remove existing /tmp/ffs directory and Clone latest ffs git repository in local x86 working machine

7. Compile ffs repository to get fcp utility

8. Check existence of fcp utility in ffs repository, after compiling

9. Get the PNOR flash contents on an x86 machine using fcp utility

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

OpTestNVRAM

This testcase will deal with testing nvram partition access functions like getting the list of partitions print/update config data in all the supported partitions

class testcases.OpTestNVRAM.HostNVRAM(methodName='runTest')

This function tests nvram partition access, print/update the config data and dumping the partition’s data. All these operations are done on supported partitions in both host OS and Petitboot.

exception testcases.OpTestNVRAM.NVRAMUpdateError(part, key, value, output)

class testcases.OpTestNVRAM.OpTestNVRAM(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestNVRAM.SkirootNVRAM(methodName='runTest')

OpTestOCC

OCC Control package for OpenPower testing.

This class will test the functionality of following.

1. OCC ResetEnableDisable

class testcases.OpTestOCC.OCCRESET_FSP(methodName='runTest')

class testcases.OpTestOCC.OCC_RESET(methodName='runTest')

class testcases.OpTestOCC.OpTestOCC(methodName='runTest')

class testcases.OpTestOCC.OpTestOCCBasic(methodName='runTest')

class testcases.OpTestOCC.OpTestOCCFull(methodName='runTest')

This function is used to test OCC Reset funtionality in BMC based systems. OCC Reset reload is limited to 3 times per full power cycle.

test_occ_enable_disable_functionality()

This function is used to test OCC Enable and Disable funtionality in BMC based systems. There is no limit for occ enable and disable, as of now doing 10 times in a loop.

test_occ_reset_n_times()

This function is used to test OCC Reset funtionality in BMC based systems. OCC Reset reload can be done more than 3 times per full power cycle, by resetting OCC resetreload count.

OpTestOpenCAPI

OpenCAPI tests for OpenPower testing.

This class will test the functionality of OpenCAPI

Prerequisites:

1. Host must have a OpenCAPI FPGA card

2. OpenCAPI card must have been flashed with memcpy3 AFU

class testcases.OpTestOpenCAPI.MemCpy3AFUAtomicCasTest(methodName='runTest')

If the system has a OpenCAPI FPGA card, then load the ocxl module if required and test the memcpy3 AFU with ocxl_memcpy -A

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestOpenCAPI.MemCpy3AFUIncrementTest(methodName='runTest')

If the system has a OpenCAPI FPGA card, then load the ocxl module if required and test the memcpy3 AFU with ocxl_memcpy -a

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestOpenCAPI.MemCpy3AFUIrqTest(methodName='runTest')

If the system has a OpenCAPI FPGA card, then load the ocxl module if required and test the memcpy3 AFU with ocxl_memcpy -i

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestOpenCAPI.MemCpy3AFUReallocTest(methodName='runTest')

If the system has a OpenCAPI FPGA card, then load the ocxl module if required and test the memcpy3 AFU with ocxl_memcpy -r

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestOpenCAPI.MemCpy3AFUTest(methodName='runTest')

If the system has a OpenCAPI FPGA card, then this test load the ocxl module if required and test the memcpy3 AFU with ocxl_memcpy

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestOpenCAPI.OcxlDeviceFileTest(methodName='runTest')

If the system has a OpenCAPI FPGA card, then this test load the ocxl module if required and check that the ocxl device files afu0.0m and afu0.0s exist

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestOpenCAPI.OpTestOpenCAPI(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestOOBIPMI

Test the out-of-band ipmi fucntionality package for OpenPower platform.

This class will test the functionality of following ipmi commands

1. bmc, channel, chassis, dcmi, echo, event, exec, firewall, fru, lan mc, pef, power, raw, sdr, sel, sensor, session, user

class testcases.OpTestOOBIPMI.OOBIPMIRuntime(methodName='runTest')

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

classmethod tearDownClass()

Hook method for deconstructing the class fixture after running all tests in the class.

class testcases.OpTestOOBIPMI.OOBIPMIStandby(methodName='runTest')

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

classmethod tearDownClass()

Hook method for deconstructing the class fixture after running all tests in the class.

class testcases.OpTestOOBIPMI.OpTestOOBIPMI(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

test_Info()

It will execute and test the ipmi <sdr/sel/mc/channel> info related commands.

test_bmc_boot_completed_cmd()

This function is used to check whether BMC Completed Booting.

Note

AMI BMC Specific

Note

This same functionality is provided elsewhere in op-test. This code is a candidate for removal.

test_bmc_golden_side_version()

This function is used to get the bmc golden image version.

Note

AMI BMC Specific

test_channel()

It will check basic channel functionalities: info and authentication capabilities.

test_chassis()

It will execute and test the ipmi chassis <cmd> commands cmd: status, poh, restart_cause, policy list and policy set

test_chassisBootdev()

It will execute and test the functionality of ipmi chassis bootdev <dev> dev: none,pxe,cdrom,disk,bios,safe,diag,floppy and none.

test_chassisIdentifytests()

It will execute and test the ipmi chassis identify commands.

test_fan_control_algorithm_1()

Step 1: Stop Fan Control Thread: ipmitool ... raw 0x3a 0x12 0x00 Step 2: Fan Control STOPPED OEM SEL created:

ipmitool ... sel list |grep OEM
7b | 04/20/2015 | 03:03:14 | OEM record c0 | 000000 | 3a1100ffffff

Step 3: #Run IsFanRunning OEM Command

ipmitool ... raw 0x3a 0x13
00

Note

AMI BMC Specific

test_fan_control_algorithm_2()

Step 1: Start Fan Control Thread:

ipmitool -I lanplus -U admin -P admin -H <BMC IP> raw 0x3a 0x12 0x01

Step 2: Fan Control STOPPED OEM SEL created

ipmitool -I lanplus -U admin -P admin -H <BMC IP> sel list |grep OEM
7b | 04/20/2015 | 03:03:14 | OEM record c0 | 000000 | 3a1100ffffff

Step 3: #Run IsFanRunning OEM Command

ipmitool -I lanplus -U admin -P admin -H <BMC IP> raw 0x3a 0x13
01

Note

AMI BMC Specific

test_firewall()

It will execute and test firmware firewall info command.

test_get_led_state_cmd()

This command is used to get the State of below Supported LED.

LED Number Table:

Fault RollUP LED	0x00
Power ON LED	0x01
Host Status LED	0x02
Chassis Identify LED	0x03

Note

AMI BMC Specific

test_get_pnor_partition_size_cmd()

This function is used to get partition size of given PNOR Partition. Currently added NVRAM,GUARD and BOOTKERNEL partitions. TODO: Add all the necessary partitions to get the size.

Note

AMI BMC specific.

test_oem_specific()

It will execute and test all Out-of-band ipmi commands. bmc, channel, chassis, dcmi, echo, event, exec, firewall, fru, lan mc, pef, power, raw, sdr, sel, sensor, session, user

FIXME: this may not be AMI specific.

test_pef()

It will execute and test pef related commands:

info

This command will query the BMC and print information about the PEF supported features.

status

This command prints the current PEF status

policy

This command lists the PEF policy table entries

list

This command lists the PEF table entries.

test_raw()

This will test raw IPMI commands. For example to query the POH counter with a raw command

test_read_pnor_partition_data()

This function is used to test reading of pnor partition data via ipmitool command. Here it will currently read NVRAM and FIRDATA partition’s data of size 254 bytes.

Note

AMI BMC Specific.

test_sel_list_first_3_entries()

It will execute and test the ipmi sel list first <3 entries>

test_sel_list_last_3_entries()

It will execute and test the ipmi sel list last <3 entries>

test_sensor_get_host_status()

It will execute and test the ipmi sensor get “Host Status” functionality

Note

AMI BMC Specific.

test_sensor_get_os_boot()

It will execute and test the ipmi sensor get “OS Boot” functionality

Note

AMI BMC Specific.

test_set_led_state_cmd()

This function is used to test set LED state feature.

LED Number Table:

Fault RollUP LED	0x00
Power ON LED	0x01
Host Status LED	0x02
Chassis Identify LED	0x03

LED State Table:

0x0	LED OFF
0x1	LED ON
0x2	LED Standby Blink Rate
0x3	LED Slow Blink rate.

Note

AMI BMC Specific

test_set_sel_time()

It will execute and test the ipmi sel set <time string> functionality Sets the SEL clock. Future SEL entries will use the time set by this command.

verify_bootdev(i_dev)

It will verify whether setting of given bootdevice is honoured or not by reading chassis bootparam get 5.

Parameters

i_dev (str) – boot device name. e.g. safe, disk, cdrom

class testcases.OpTestOOBIPMI.OpTestOOBIPMIBase(methodName='runTest')

run_ipmi_cmd(i_cmd)

It will execute and test the return code of ipmi command.

Parameters

i_cmd (str) – The ipmitool command, e.g. chassis power on

Returns

output of command

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestPCI: PCI checks

Perform various PCI validations and checks

–run-suite BasicPCI (includes skiroot_suite and host_suite) –run-suite pci-regression

Sample naming conventions below, see each test method for the applicable options per method.

–run testcases.OpTestPCI.PCISkiroot.pcie_link_errors

^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^ ^^^^^^^^^^^^^^^^

module name subclass test method

–run testcases.OpTestPCI.PCIHost.pcie_link_errors

^^^^^^^^^^^^^^^^^^^ ^^^^^^^ ^^^^^^^^^^^^^^^^

module name subclass test method

class testcases.OpTestPCI.OpClassPCI(methodName='runTest')

Main Parent class

We cannot guarantee a soft boot entry, so need to force to PS or OS

check_commands()

Checks for general capability to run commands

Case A –run testcases.OpTestPCI.PCISkiroot.check_commands Case B –run testcases.OpTestPCI.PCISkirootSoftboot.check_commands Case C –run testcases.OpTestPCI.PCISkirootHardboot.check_commands Case D –run testcases.OpTestPCI.PCIHost.check_commands Case E –run testcases.OpTestPCI.PCIHostSoftboot.check_commands Case F –run testcases.OpTestPCI.PCIHostHardboot.check_commands

compare_boot_devices()

This is best leveraged in the suite pci-regression, where both the skiroot/host softboot and the skiroot/host hardboot get done in the same wave, so that the global variables carry over to compare.

If both skiroot and host lspci completed, will compare lspci results.

If you want to compare against an input file, use compare_live_devices.

Case A –run testcases.OpTestPCI.PCISkiroot.compare_boot_devices Case B –run testcases.OpTestPCI.PCISkirootSoftboot.compare_boot_devices Case C –run testcases.OpTestPCI.PCISkirootHardboot.compare_boot_devices Case D –run testcases.OpTestPCI.PCIHost.compare_boot_devices Case E –run testcases.OpTestPCI.PCIHostSoftboot.compare_boot_devices Case F –run testcases.OpTestPCI.PCIHostHardboot.compare_boot_devices

compare_live_devices()

Compares the live system lspci against an input file, host-lspci provided either in conf file or via command line.

“ssh user@host lspci -mm -n > host-lspci.txt”

–host-lspci host-lspci.txt on command line

or

host_lspci=host-lspci.txt in conf file

Case A –run testcases.OpTestPCI.PCISkiroot.compare_live_devices Case B –run testcases.OpTestPCI.PCISkirootSoftboot.compare_live_devices Case C –run testcases.OpTestPCI.PCISkirootHardboot.compare_live_devices Case D –run testcases.OpTestPCI.PCIHost.compare_live_devices Case E –run testcases.OpTestPCI.PCIHostSoftboot.compare_live_devices Case F –run testcases.OpTestPCI.PCIHostHardboot.compare_live_devices

driver_bind()

Unbind and then bind the devices

Case A –run testcases.OpTestPCI.PCISkiroot.driver_bind Case B –run testcases.OpTestPCI.PCISkirootSoftboot.driver_bind Case C –run testcases.OpTestPCI.PCISkirootHardboot.driver_bind Case D –run testcases.OpTestPCI.PCIHost.driver_bind Case E –run testcases.OpTestPCI.PCIHostSoftboot.driver_bind Case F –run testcases.OpTestPCI.PCIHostHardboot.driver_bind

Special note on unbinding shared bmc ethernet ports, caution.

get_lspci()

Usually used internally, can be run for query of system

Case A –run testcases.OpTestPCI.PCISkiroot.get_lspci Case B –run testcases.OpTestPCI.PCISkirootSoftboot.get_lspci Case C –run testcases.OpTestPCI.PCISkirootHardboot.get_lspci Case D –run testcases.OpTestPCI.PCIHost.get_lspci Case E –run testcases.OpTestPCI.PCIHostSoftboot.get_lspci Case F –run testcases.OpTestPCI.PCIHostHardboot.get_lspci

get_lspci_file()

Usually used internally, can be run for query of system

Case A –run testcases.OpTestPCI.PCISkiroot.get_lspci_file Case B –run testcases.OpTestPCI.PCISkirootSoftboot.get_lspci_file Case C –run testcases.OpTestPCI.PCISkirootHardboot.get_lspci_file Case D –run testcases.OpTestPCI.PCIHost.get_lspci_file Case E –run testcases.OpTestPCI.PCIHostSoftboot.get_lspci_file Case F –run testcases.OpTestPCI.PCIHostHardboot.get_lspci_file

hot_plug_host()

NEEDS TESTING Case A –run testcases.OpTestPCI.PCIHost.hot_plug_host Case B –run testcases.OpTestPCI.PCIHostSoftboot.hot_plug_host Case C –run testcases.OpTestPCI.PCIHostHardboot.hot_plug_host

pci_link_check()

PCI link checks

Case A –run testcases.OpTestPCI.PCISkiroot.pci_link_check Case B –run testcases.OpTestPCI.PCISkirootSoftboot.pci_link_check Case C –run testcases.OpTestPCI.PCISkirootHardboot.pci_link_check Case D –run testcases.OpTestPCI.PCIHost.pci_link_check Case E –run testcases.OpTestPCI.PCIHostSoftboot.pci_link_check Case F –run testcases.OpTestPCI.PCIHostHardboot.pci_link_check

pcie_link_errors()

Checks for link errors

Case A –run testcases.OpTestPCI.PCISkiroot.pcie_link_errors Case B –run testcases.OpTestPCI.PCISkirootSoftboot.pcie_link_errors Case C –run testcases.OpTestPCI.PCISkirootHardboot.pcie_link_errors Case D –run testcases.OpTestPCI.PCIHost.pcie_link_errors Case E –run testcases.OpTestPCI.PCIHostSoftboot.pcie_link_errors Case F –run testcases.OpTestPCI.PCIHostHardboot.pcie_link_errors

classmethod refresh_console()

This method is used to set the shared class console back to the proper object (this gets set to the real console when we unbind the ethernet) in the driver_bind test as an example.

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

classmethod setUpClass(desired=None, power_cycle=0)

Main setUpClass, this is shared across all subclasses. This is called once when the subclass is instantiated.

classmethod set_console()

This method allows setting the shared class console to the real console when needed, i.e. driver_bind tests which unbind the ethernet drivers.

tearDown()

This is done at the end of each subclass test.

classmethod tearDownClass()

Main tearDownClass, this is shared across all subclasses. This is called once when the subclass is taken down.

class testcases.OpTestPCI.PCIHost(methodName='runTest')

Class allows to run parent classes with unique setup

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

classmethod setUpClass()

Main setUpClass, this is shared across all subclasses. This is called once when the subclass is instantiated.

class testcases.OpTestPCI.PCIHostHardboot(methodName='runTest')

Class allows to run parent classes with unique setup

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

classmethod setUpClass()

Main setUpClass, this is shared across all subclasses. This is called once when the subclass is instantiated.

classmethod tearDownClass()

Main tearDownClass, this is shared across all subclasses. This is called once when the subclass is taken down.

class testcases.OpTestPCI.PCIHostSoftboot(methodName='runTest')

Class allows to run parent classes with unique setup

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

classmethod setUpClass()

Main setUpClass, this is shared across all subclasses. This is called once when the subclass is instantiated.

classmethod tearDownClass()

Main tearDownClass, this is shared across all subclasses. This is called once when the subclass is taken down.

class testcases.OpTestPCI.PCISkiroot(methodName='runTest')

Class allows to run parent classes with unique setup

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

class testcases.OpTestPCI.PCISkirootHardboot(methodName='runTest')

Class allows to run parent classes with unique setup

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

classmethod setUpClass()

Main setUpClass, this is shared across all subclasses. This is called once when the subclass is instantiated.

classmethod tearDownClass()

Main tearDownClass, this is shared across all subclasses. This is called once when the subclass is taken down.

class testcases.OpTestPCI.PCISkirootSoftboot(methodName='runTest')

Class allows to run parent classes with unique setup

setUp()

All variables common to a subclass need to be defined here since this method gets called before each subclass test

classmethod setUpClass()

Main setUpClass, this is shared across all subclasses. This is called once when the subclass is instantiated.

classmethod tearDownClass()

Main tearDownClass, this is shared across all subclasses. This is called once when the subclass is taken down.

testcases.OpTestPCI.host_full_suite()

Function used to prepare a test suite (see op-test) –run testcases.OpTestPCI.host_full_suite

This suite does not care on soft vs hard boot

testcases.OpTestPCI.host_hardboot_suite()

Function used to prepare a test suite (see op-test) –run-suite pci-regression –run testcases.OpTestPCI.host_hardboot_suite

testcases.OpTestPCI.host_softboot_suite()

Function used to prepare a test suite (see op-test) –run-suite pci-regression –run testcases.OpTestPCI.host_softboot_suite

testcases.OpTestPCI.host_suite()

Function used to prepare a test suite (see op-test) –run-suite BasicPCI –run testcases.OpTestPCI.host_suite

This suite does not care on soft vs hard boot

testcases.OpTestPCI.skiroot_full_suite()

Function used to prepare a test suite (see op-test) –run testcases.OpTestPCI.skiroot_full_suite

This suite does not care on soft vs hard boot

testcases.OpTestPCI.skiroot_hardboot_suite()

Function used to prepare a test suite (see op-test) –run-suite pci-regression –run testcases.OpTestPCI.skiroot_hardboot_suite

testcases.OpTestPCI.skiroot_softboot_suite()

Function used to prepare a test suite (see op-test) –run-suite pci-regression –run testcases.OpTestPCI.skiroot_softboot_suite

testcases.OpTestPCI.skiroot_suite()

Function used to prepare a test suite (see op-test) –run-suite BasicPCI –run testcases.OpTestPCI.skiroot_suite

This suite does not care on soft vs hard boot

OpTestPNOR

This testcase will deal with testing access to the host pnor from petitboot through the pflash program

class testcases.OpTestPNOR.Host(methodName='runTest')

class testcases.OpTestPNOR.Skiroot(methodName='runTest')

OpTestPrdDaemon

PRD daemon for OpenPower testing.

This class will test the functionality of following.

• PRD (Processor Runtime Diagnostic) daemon should always be running in HOST OS.

• For testing out this feature, we require to kill the opal-prd daemon and make sure that the daemon spawns back always.

class testcases.OpTestPrdDaemon.OpTestPrdDaemon(methodName='runTest')

This function performs below steps

1. Initially connecting to host console for execution.

2. Check for whether opal-prd daemon is running or not if it is, get the PID of the opal-prd daemon

3. Kill the opal-prd daemon using its PID

4. Again check if opal-prd daemon spawns back

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestPrdDriver

PRD driver package for OpenPower testing.

This class will test the functionality of following:

• PRD (Processor Runtime Diagnostic) enables the support for handing certain RAS events by the userspace application.

• For testing out this feature, we require the userspace xscom-utils, part of the ‘skiboot’ tree.

• skiboot tree is cloning in /tmp directory.

• Using the xscom utility, we need to inject errors through FIR (Fault Isolation Register) and observe them getting cleared if PRD handles them successfully.

  • 0x01020013 IPOLL mask register

  • 0x02010840 PBA Local Fault isolation register

  • 0x02010843 PBA Local fault isolation mask register

class testcases.OpTestPrdDriver.OpTestPrdDriver(methodName='runTest')

prd_init()

This is a common function for all the PRD test cases. This will be executed before any test case starts. Basically this provides below requirements.

1. Validates all required host commands

2. Get the list Of Chips (Using getscom binary). e.g.

   ['00000000', '00000001', '00000010']
   

3. generate a random chip.

prd_test_core_fir(FIR, FIMR, ERROR)

This function injects some core FIR errors and verifies whether opal-prd clears the errors. and also this function injects errors on random chip.

Parameters

• FIR (str) – Local Fault Isolation register

• FIMR (str) – Local Fault Isolation mask register

• ERROR (str) – Core FIR error, this error will be written to FIR.

runTest()

This function performs below steps:

1. Initially connecting to host for execution.

2. check for IPOLL mask register value to see whether opal-prd is running or not if it is 0–>opal-prd is running–>continue else start opal-prd service again

3. call test_prd_for_fir() function for each core FIR error and this function can be used for any number of errors, like it is a generic function

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestRebootTimeout

Test it doesn’t take until the heat death of the universe to reboot.

class testcases.OpTestRebootTimeout.Host(methodName='runTest')

class testcases.OpTestRebootTimeout.RebootTime

A test to ensure that after issuing the reboot command, we receive it in OPAL in suitable time.

class testcases.OpTestRebootTimeout.Skiroot(methodName='runTest')

OpTestRTCdriver

RTC (Real Time Clock) package for OpenPower testing.

This class will test the functionality of following drivers

1. RTC driver: Real time clock

class testcases.OpTestRTCdriver.BasicRTC(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestRTCdriver.FullRTC(methodName='runTest')

RunFullRTC()

This function will cover following test steps

1. Getting host information(OS and Kernel info)

2. Loading rtc_opal module based on config option

3. Testing the rtc driver functions:

   • Display the current time,

   • set the Hardware Clock to a specified time,

   • set the Hardware Clock from the System Time, or

   • set the System Time from the Hardware Clock

   • keep the Hardware clock in UTC or local time format

   • Hardware clock compare, predict and adjust functions

   • Hardware clock debug and test modes

   • Reading the Hardware clock from special file instead of default

4. After executing above each function reading the Hardware clock in b/w functions.

hwclock_adjust()

This function tests hwclock adjust functionality

hwclock_debug_mode()

This function tests hwclock debug mode. In this mode setting hwclock from system time and setting system time from hwclock

hwclock_in_localtime()

This function keeps hwclock in local time format.

hwclock_in_utc()

This function keeps hwclock in UTC format.

hwclock_predict(i_time)

This function predict RTC reading at time given with –date

Parameters

i_time – time at which predict hwclock reading

hwclock_test_mode(i_time)

This function tests the hwclock test mode. In this mode setting the hwclock time using --set option. Here it just execute but should not set hwclock time.

Parameters

i_time (str) – time to set hwclock in test mode

hwclock_to_systime()

This function sets the system time from hwclock.

read_hwclock_from_file(i_file)

This function reads hwclock from special /dev/… file instead of default

setUp()

Hook method for setting up the test fixture before exercising it.

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

set_hwclock_in_localtime(i_time)

This function sets hwclock in local time format

Parameters

i_time – Time to set hwclock

set_hwclock_in_utc(i_time)

This function sets hwclock in UTC format

Parameters

i_time (str) – time to set hwclock e.g. “2016-01-01 12:12:12”

systime_to_hwclock()

This function sets the time of hwclock from system time

systime_to_hwclock_in_localtime()

This function sets the time of hwclock from system time in local time format

systime_to_hwclock_in_utc()

This function sets the time of hwclock from system time in UTC format

class testcases.OpTestRTCdriver.HostRTC(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.OpTestRTCdriver.SkirootRTC(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestSensors

Sensors package for OpenPower testing.

This class will test the functionality of following drivers

1. Hardware monitoring sensors(hwmon driver) using sensors utility

class testcases.OpTestSensors.OpTestSensors(methodName='runTest')

This test will cover following test steps:

1. It will check for kernel config option CONFIG_SENSORS_IBMPOWERNV

2. It will load ibmpowernv driver only on powernv platform

3. It will check for sensors command existence and lm_sensors package

4. start the lm_sensors service and detect any sensor chips using sensors-detect.

5. At the end it will test sensors command functionality with different options

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

OpTestSwitchEndianSyscall

Switch endian system call package for OpenPower testing.

This class will test the functionality of following.

1. It will test switch_endian() system call by executing the registers changes in other endian. By calling switch_endian sys call, should not effect register and memory space.

2. This functionality is implemented in linux git repository /linux/tools/testing/selftests/powerpc/switch_endian

3. In this test, will clone latest linux git repository and make required files. At the end will execute switch_endian_test executable file.

class testcases.OpTestSwitchEndianSyscall.OpTestSwitchEndianSyscall(methodName='runTest')

If git and gcc commands are availble on host, this function will clone linux git repository and check for switch_endian_test directory and make the required files. And finally execute bin file switch_endian_test.

check_dir_exists(i_dir)

It will check for existence of switch_endian directory in the cloned repository

Parameters

i_dir – linux source directory

make_test(i_dir)

It will prepare for executable bin files using make command At the end it will check for bin file switch_endian_test and will throw an exception in case of missing bin file after make

Parameters

i_dir – linux source directory

run_once(i_dir)

This function will run executable file switch_endian_test and check for switch_endian() sys call functionality

Parameters

i_dir – linux source directory

setUp()

Hook method for setting up the test fixture before exercising it.

OpTestSystemBootSequence

It will test below system boot sequence operations

Mc cold reset boot sequence.

0. Power off state (and auto reboot policy should be off)

1. Make sure BMC is pinging

2. Issue Cold reset to BMC => ipmitool <…> mc reset cold

3. Ensure BMC stops pinging, wait until BMC fully boots

4. Open network sol console => ipmitool <…> sol activate

5. Power on system => ipmitool <…> chassis power on

6. Make sure boots to Host OS, SOL fine

Mc warm reset boot sequence

0. Power off state (and auto reboot policy should be off)

1. Make sure BMC is pinging

2. Issue warm reset to BMC => ipmitool <…> mc reset warm

3. Ensure BMC stops pinging, wait until BMC fully boots

4. Open network sol console => ipmitool <…> sol activate

5. Power on system => ipmitool <…> chassis power on

6. Make sure boots to Host OS, SOL fine

class testcases.OpTestSystemBootSequence.ColdReset_IPL(methodName='runTest')

This function will test mc cold reset boot sequence, It has below steps

1. Do a system Power OFF(Host should go down)

2. Set auto reboot policy to off(chassis policy always-off)

3. Issue a BMC Cold reset.

4. After BMC comes up, Issue a Power ON of the system

5. Check for system status and gather OPAL msg log.

class testcases.OpTestSystemBootSequence.OpTestSystemBootSequence(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

class testcases.OpTestSystemBootSequence.PowerPolicyOFF_IPL(methodName='runTest')

This function will test system auto reboot policy always-off. It has below steps

1. Do a system Power OFF(Host should go down)

2. Set auto reboot policy to off(chassis policy always-off)

3. Issue a BMC Cold reset.

4. After BMC comes up, expect the system to not boot.

5. Issue a Power ON of the system

6. Check for system status and gather OPAL msg log.

class testcases.OpTestSystemBootSequence.PowerPolicyON_IPL(methodName='runTest')

This function will test system auto reboot policy always-on. It has below steps

1. Do a system Power OFF(Host should go down)

2. Set auto reboot policy to on(chassis policy always-on)

3. Issue a BMC Cold reset.

4. After BMC comes up, Here expect the system to boot, If not power policy is not working as expected

5. Check for system status and gather OPAL msg log.

class testcases.OpTestSystemBootSequence.PowerPolicyPrevious_IPL(methodName='runTest')

This function will test system auto reboot policy previous It has below steps

1. Do a system Power OFF(Host should go down)

2. Set auto reboot policy to previous(chassis policy previous)

3. Issue a BMC Cold reset.

4. After BMC comes up, system power status will change based on previous power status before issuing cold reset.

5. Check for system status and gather OPAL msg log.

class testcases.OpTestSystemBootSequence.WarmReset_IPL(methodName='runTest')

This function will test mc warm reset boot sequence, It has below steps

1. Do a system Power OFF(Host should go down)

2. Set auto reboot policy to off(chassis policy always-off)

3. Issue a BMC Warm reset.

4. After BMC comes up, Issue a Power ON of the system

5. Check for system status and gather OPAL msg log.

PCI Slot/Location Codes

This test will use the device tree to determine if the pciex is a root/switch fabric with one or more switch devices.

Slot labels and loc codes are retrieved and if missing or empty the test will identify for investigation. Not all test results reporting missing or empty slot labels or loc codes are problems, it is the system owner to make that determination.

class testcases.PciSlotLocCodes.HostDT(methodName='runTest')

HostDT Class performs PCI DT checks in the Host OS –run testcases.PciSlotLocCodes.HostDT

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.PciSlotLocCodes.PciDT(methodName='runTest')

PciDT Class –run testcases.PciSlotLocCodes

build_slot_loc_tables()

Builds a dictionary to track slots and loc codes and their values.

doit()

Performs the building of an lspci like lookup that will be used to output helpful information when failures occur as well as logging both good and not so good results to the debug log for analysis.

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.PciSlotLocCodes.SkirootDT(methodName='runTest')

SkirootDT Class performs PCI DT checks in skiroot –run testcases.PciSlotLocCodes.SkirootDT

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

Petitboot Dropbear Server

Test Dropbear SSH Serevr is not present in skiroot

The skiroot (pettiboot environment) firmware contains dropbear for it’s ssh client functioanlity. We do not want to enable network accessable system in the environemnt for security reasons.

This test ensures that the ssh server is not running at boot

class testcases.PetitbootDropbearServer.PetitbootDropbearServer(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

Petitboot Internationalization (i8n)

Test that Petitboot can correctly display languages other than English.

class testcases.Petitbooti18n.Petitbooti18n(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

RunHostTest

Runs a bunch of commands from a file on the op-test running system on the host.

class testcases.RunHostTest.RunHostTest(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

SbePassThrough

Test case for SBE passthrough

class testcases.SbePassThrough.SbePassThrough(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

Secureboot IPL Tests

class testcases.SecureBoot.KeyTransitionPNOR(methodName='runTest')

Secure boot key transition test: Ensure successful key transition in SEEPROM Types of Key Transition PNOR images:

• dev to dev

• dev to prod

• prod to dev

• prod to prod

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SecureBoot.OPALContainerTest(methodName='runTest')

System having Signed PNOR(either production or developement mode) Flash signed containers with wrong keys Secureboot verify should fail and boot should abort

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SecureBoot.SecureBoot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SecureBoot.SignedPNOR(methodName='runTest')

Secure boot IPL test: Ensure successful boot with properly signed PNOR.

SB Mode	sign mode	Boot result
ON	Signed	Pass
OFF	Signed	Pass

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SecureBoot.SignedToPNOR(methodName='runTest')

Secure boot IPL test: Ensure successful boot with properly signed to PNOR(To match the keys which are got replaced after KeyTransitionPNOR flash test).

SB Mode	sign mode	Boot result
ON	Signed	Pass
OFF	Signed	Pass

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SecureBoot.UnSignedPNOR(methodName='runTest')

Secure boot IPL test: Ensure prevention of boot with improperly signed PNOR.

SB Mode	sign mode	Boot result
ON	Unsigned	Fail
OFF	Unsigned	Pass

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SecureBoot.VerifyOPALSecureboot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

System Login

Really simple tests to ensure we can simply log into a booted host.

class testcases.SystemLogin.BMCLogin(methodName='runTest')

Log into the BMC via SSH and run different commands

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SystemLogin.ExampleRestAPI(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SystemLogin.OOBHostLogin(methodName='runTest')

Log into the host via out of band console and run different commands

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.SystemLogin.SSHHostLogin(methodName='runTest')

Log into the host via SSH and run different commands

setUp()

Hook method for setting up the test fixture before exercising it.

Test OpenBMC REST API

Tests a bunch of functionality only available through OpenBMC REST API

Generally takes about 10 minutes to run rest-api suite

Note

The OpenBMC REST API is not a long term nor stable API. It’s just as likely that OpenBMC changes their API as anything.

class testcases.testRestAPI.HostBounces(methodName='runTest')

Performs Reboots and Power On/Off variety Purpose is to exercise the REST API’s –run testcases.testRestAPI.HostBounces

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

test_hard_reboot()

REST Hard Reboot –run testcases.testRestAPI.HostBounces.test_hard_reboot

test_power_off()

REST Power Off –run testcases.testRestAPI.HostBounces.test_power_off

test_power_on()

REST Power On –run testcases.testRestAPI.HostBounces.test_power_on

test_power_soft()

REST Power Soft Off –run testcases.testRestAPI.HostBounces.test_power_soft

test_soft_reboot()

REST Soft Reboot –run testcases.testRestAPI.HostBounces.test_soft_reboot

class testcases.testRestAPI.HostOff(methodName='runTest')

Runtime Class performs tests with Host On HostOff Class will turn the Host Off –run testcases.testRestAPI.Runtime –run testcases.testRestAPI.HostOff

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.testRestAPI.RestAPI(methodName='runTest')

RestAPI Class - Execution order independent –run-suite rest-api –run testcases.testRestAPI.Runtime –run testcases.testRestAPI.HostOff or run the individual tests

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

class testcases.testRestAPI.Runtime(methodName='runTest')

Runtime Class performs tests with Host On HostOff Class will turn the Host Off –run testcases.testRestAPI.Runtime –run testcases.testRestAPI.HostOff

classmethod setUpClass()

Hook method for setting up class fixture before running tests in the class.

test_clear_gard_record()

REST Clear ALL Gard Records –run testcases.testRestAPI.Runtime.test_clear_gard_record –run testcases.testRestAPI.HostOff.test_clear_gard_record

test_clear_sel()

REST Clear SELs –run testcases.testRestAPI.Runtime.test_clear_sel –run testcases.testRestAPI.HostOff.test_clear_sel

test_dump_sels()

REST Dump SELs –run testcases.testRestAPI.Runtime.test_dump_sels –run testcases.testRestAPI.HostOff.test_dump_sels

test_factory_reset_network()

REST Factory Reset Network USE AT YOUR OWN RISK –run testcases.testRestAPI.Runtime.test_factory_reset_network –run testcases.testRestAPI.HostOff.test_factory_reset_network

test_factory_reset_software()

REST Factory Reset Software USE AT YOUR OWN RISK –run testcases.testRestAPI.Runtime.test_factory_reset_software –run testcases.testRestAPI.HostOff.test_factory_reset_software

test_field_mode_enable_disable()

REST Field Mode Enable and Disable –run testcases.testRestAPI.Runtime.test_field_mode_enable_disable –run testcases.testRestAPI.HostOff.test_field_mode_enable_disable

test_get_boot_progress()

REST Get Boot Progress –run testcases.testRestAPI.Runtime.test_get_boot_progress –run testcases.testRestAPI.HostOff.test_get_boot_progress

test_image_lists()

REST Image Interfaces –run testcases.testRestAPI.Runtime.test_image_lists –run testcases.testRestAPI.HostOff.test_image_lists

test_inventory()

REST Get Inventory –run testcases.testRestAPI.Runtime.test_inventory –run testcases.testRestAPI.HostOff.test_inventory

test_list_sel()

REST List SELs –run testcases.testRestAPI.Runtime.test_list_sel –run testcases.testRestAPI.HostOff.test_list_sel

test_obmc_create_dump()

REST OBMC Create Dump –run testcases.testRestAPI.Runtime.test_obmc_create_dump –run testcases.testRestAPI.HostOff.test_obmc_create_dump

test_obmc_delete_dumps()

REST OBMC Delete ALL Dumps –run testcases.testRestAPI.Runtime.test_obmc_delete_dumps –run testcases.testRestAPI.HostOff.test_obmc_delete_dumps

test_obmc_download_dumps()

REST OBMC Download ALL Dumps –run testcases.testRestAPI.Runtime.test_obmc_download_dumps –run testcases.testRestAPI.HostOff.test_obmc_download_dumps

test_obmc_dump()

REST OBMC List, Create and Download a Dump –run testcases.testRestAPI.Runtime.test_obmc_dump –run testcases.testRestAPI.HostOff.test_obmc_dump

test_obmc_states()

REST OBMC States –run testcases.testRestAPI.Runtime.test_obmc_states –run testcases.testRestAPI.HostOff.test_obmc_states

test_occ_active()

REST OCC Active –run testcases.testRestAPI.Runtime.test_occ_active –run testcases.testRestAPI.HostOff.test_occ_active

test_sensors()

REST Sensors –run testcases.testRestAPI.Runtime.test_sensors –run testcases.testRestAPI.HostOff.test_sensors

test_set_bootdevs()

REST Set Boot Device to Setup then Regular, this leaves the boot device as we found it –run testcases.testRestAPI.Runtime.test_set_bootdevs –run testcases.testRestAPI.HostOff.test_set_bootdevs

test_software_enumerate()

REST Software Enumerate –run testcases.testRestAPI.Runtime.test_software_enumerate –run testcases.testRestAPI.HostOff.test_software_enumerate

test_system_power_cap()

REST System Power Cap –run testcases.testRestAPI.Runtime.test_system_power_cap –run testcases.testRestAPI.HostOff.test_system_power_cap

test_tpm_policy_setting()

REST TPM Policy Settings –run testcases.testRestAPI.Runtime.test_tpm_policy_setting –run testcases.testRestAPI.HostOff.test_tpm_policy_setting

test_update_root_password()

REST Update Root Password Caution if OpTestConfiguration bmc_password is modified util_bmc_server does automatic login with stored credentials –run testcases.testRestAPI.Runtime.test_update_root_password –run testcases.testRestAPI.HostOff.test_update_root_password

test_upload_image()

REST Upload Image –run testcases.testRestAPI.Runtime.test_upload_image –run testcases.testRestAPI.HostOff.test_upload_image

Trustedboot IPL Tests

This tests expect a TPM chip to be installed/removed on the system and also a secureboot mode enabled/disabled accordingly.

If TPM chip is installed –> provide –trusted-mode in command line If secureboot is enabled –> provide –secure-mode in command line

The “TPM Required” policy means:

enabled:

Node must have at least 1 functional TPM to boot, otherwise system will terminate

disabled:

Node can boot without a functional TPM

If system has a working TPM, the policy is a don’t care. If secure mode is not enabled, the policy is a don’t care. if you set policy to “enabled” and remove/inject error on TPM -and- system is in secure mode, system boot will terminate if you set policy to disable and remove/inject error on the TPM -and- system is in secure mode, system will still boot

class testcases.TrustedBoot.FunctionalTPM_PolicyOFF(methodName='runTest')

Functional TPM, TPM Required(cleared)

• Test IPL, Measurements & event logs(Secure Mode Override jumper(s) ON or OFF)

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.TrustedBoot.FunctionalTPM_PolicyON(methodName='runTest')

Functional TPM, TPM Required(set)

• Test IPL, Measurements & event logs(Secure Mode Override jumper(s) can be ON or OFF)

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.TrustedBoot.NoFunctionalTPM_PolicyOFF(methodName='runTest')

No Functional TPM, TPM Required(cleared)

• Test IPL, Measurements & event logs(Secure Mode Override jumper(s) can be ON or OFF)

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.TrustedBoot.NoFunctionalTPM_PolicyON(methodName='runTest')

No Functional TPM, TPM Required(set)

• Test IPL, Measurements & event logs(Secure Mode Override jumper(s) can be ON or OFF)

setUp()

Hook method for setting up the test fixture before exercising it.

class testcases.TrustedBoot.TrustedBoot(methodName='runTest')

setUp()

Hook method for setting up the test fixture before exercising it.

tearDown()

Hook method for deconstructing the test fixture after testing it.

class testcases.TrustedBoot.VerifyOPALTrustedBoot(methodName='runTest')

1. It verify whether OPAL measures and records of all the resources it loads from PNOR.

2. It also verifies the corresponding DT properties for trustedboot and TPM device.

setUp()

Hook method for setting up the test fixture before exercising it.