Test Design of rinv python version

Test Design of rinv python version

##＃ Introduction

This document provides an overview of test of command rinv that is conducted on the IBM Witherspoon Physical Machine. This test plan is intended for the use of xCAT FVT team.

The test is against xCAT version 2.13.11. The build of xCAT will be picked up from the xcat.org

Overview of xCAT FVT

Test Software Requirements

Operating System ：Red Hat Enterprise Linux Server release 7.4

Other Softwares

xCAT 2.13.11

Test Hardware Requirements

MN: any machines with latest xcat installed
CN: Witherspoon node (p9)

xCAT Test Detail Section

Test environment preparation

• new OpenBMC python version rpm installation steps:

  • Use yum install gcc and python-devel.ppc64le:

    yum install -y gcc python-devel.ppc64le 
    

  • Install pip refer to https://pip.pypa.io/en/stable/installing/. Use pip to install gevent, greenlet, certifi, chardet, idna, urllib3, requests:

    pip install gevent greenlet certifi chardet idna urllib3 requests
    

  • Download and install xCAT-openbmc-py-2.13.10-snap201801250418.noarch.rpm:

    wget http://xcat.org/files/xcat/xcat-dep/2.x_Linux/beta/xCAT-openbmc-py-2.13.10-snap201801250418.noarch.rpm
    yum localinstall -y xCAT-openbmc-py-2.13.10-snap201801250418.noarch.rpm
    

  • enable OpenBMC python version:

    export XCAT_OPENBMC_PYTHON=YES
    

Test cases

The test cases is given according to the rinv' help information for machines managed by openbmc.

OpenPOWER (OpenBMC) server specific: rinv [model|serial|firm|cpu|dimm|all] [-V|--verbose]

Test case 1

Check if rinv -h or --help could display help information for openbmc.

1. Run rinv -h or rinv --help
2. Expected output should be help information.

Test case 2

Check if rinv noderange model could retrieves the machine's model number.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange model
3. Expected output should be the node's model information.

Test case 3

Check if rinv noderange serial could retrieves the machine's serial number.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange serial
3. Expected output should be the node's serial information.

Test case 4

Check if rinv noderange firm could retrieves the machine's firmware version.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange firm
3. Expected output should be the node's firmware version.

Test case 5

Check if rinv noderange cpu could retrieves the machine's firmware version.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange firm
3. Expected output should be the node's firmware version.

Test case 6

Check if rinv noderange dimm could retrieves the machine's dual in-line memory module information.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange dimm
3. Expected output should be the node's dual in-line memory module information.

Test case 7

Check if rinv noderange all could retrieves the machine's all information include cpu, memory, power etc.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange all
3. Expected output should be the node's all information.

Test case 8

Check if rinv noderange all -V / --verbose could retrieves the machine's all information in verbose format.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange all -V/ --verbose
3. Expected output should be the node's verbose information.

Test case 9

Check if rinv noderange false_value.

1. Define node. The node's definition should have bmc's ip. BMC should work correctly.
2. Run rinv nodegrange false_value
3. Expected output should be warning message.