/openbmc/openbmc-test-automation/ |
H A D | README.md | 1 ## Features of OpenBMC Test Automation 5 - DMTF Redfish 6 - Out-of-band IPMI 7 - SSH to BMC and Host OS 8 - [Legacy REST](https://github.com/openbmc/openbmc-test-automation/releases/tag/v4.0-stable) 12 - Power on/off 13 - Reboot Host 14 - Reset BMC 15 - Code update BMC and host 16 - Power management [all …]
|
H A D | CONTRIBUTING.md | 1 # Contributing to OpenBMC Test Automation 3 Guide to working on OpenBMC test automation. This document will always be a 4 work-in-progress, feel free to propose changes. 8 - Reference 9 …[OpenBMC CLA](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-g… 10 - Reference 11 …[OpenBMC docs](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#submitting-changes-via-… 15 - Reference 16 …Formatting Commit Messages](https://github.com/openbmc/docs/blob/master/CONTRIBUTING.md#formatting… 20 - [Redfish Coding Guidelines](docs/redfish_coding_guidelines.md) [all …]
|
/openbmc/openbmc-test-automation/test_lists/ |
H A D | skip_test_palmetto | 1 # https://github.com/openbmc/openbmc/issues/93 2 --exclude System_Present 3 --exclude Chassis_Present 4 # https://github.com/openbmc/openbmc-test-automation/issues/207 5 --exclude Disable_PowerCap 6 # https://github.com/openbmc/openbmc-test-automation/issues/123 7 --exclude Execute_ipmi_BT_capabilities_command 9 --exclude io_board_Present 10 --exclude io_board_Fault 11 --exclude Verify_Enabling_OCC_Turbo_Setting_Via_IPMI [all …]
|
H A D | skip_test_witherspoon | 1 # https://github.com/openbmc/openbmc-test-automation/issues/822 2 --exclude Verify_Minimal_Memory_Buffer_Inventory 3 --exclude Verify_Minimal_Main_Planar_Inventory 4 --exclude Verify_Minimal_System_Inventory 5 # NA test case for Witherspoon 6 --exclude io_board_Present 7 --exclude io_board_Fault 8 # System LED test cases which are NA for Witherspoon system. 9 --exclude Test_Heartbeat_LED_And_Verify_Via_REST 10 --exclude Test_Beep_LED_And_Verify_Via_REST [all …]
|
/openbmc/docs/testing/ |
H A D | run-test-docker.md | 1 # Run OpenBMC Test Automation Using Docker 3 Running OpenBMC automation using Docker involves creating a Docker image and 4 then running automation tests inside the Docker container. 18 3. Clone openbmc-build-scripts repository. 20 `git clone https://github.com/openbmc/openbmc-build-scripts` 22 4. Change directory to openbmc-build-scripts. 24 `cd openbmc-build-scripts` 28 "openbmc/ubuntu-robot-qemu". You can check images using "docker images" 31 `./scripts/build-qemu-robot-docker.sh` 37 --build-arg http_proxy=<IP>:<PORT> --build-arg https_proxy=<IP>:<PORT> [all …]
|
/openbmc/openbmc-test-automation/bin/ |
H A D | jenkins_funcs.sh | 13 # - Recognizing existing git repo if appropriate. 14 # - Cloning git repo. 15 # - Running caller's post_clone_command. 25 # git repo will be used as-is. 27 # clone of openbmc-test-automation. Note 29 # BMC Test code developers who may wish to 32 if [ -d "${git_dir_path}" -a "${git_dir_path}" != "${WORKSPACE}" ] ; then 39 set -x 40 mkdir -p "${git_dir_path}" || return 1 44 rm -Rf ./openbmc-build-scripts [all …]
|
H A D | python | 10 # cd openbmc-test-automation/bin 11 # ln -s select_version python 13 # The PATH variable should contain the expanded path to openbmc-test-automation/bin. 28 local target_program_path_var="${1:-target_program_path}" ; shift 48 # ln -s select_version python 50 base_program_path=$(readlink -f "${0}") 55 echo -n "**ERROR** ${base_program_name} should never be called directly." 66 … # Now use the "type" built-in to search the PATH variable for a list of target program candidates. 67 candidates=$(type -ap ${alternate_program_name}) 70 # /home/robot/openbmc-test-automation/bin/python [all …]
|
H A D | select_version | 10 # cd openbmc-test-automation/bin 11 # ln -s select_version python 13 # The PATH variable should contain the expanded path to openbmc-test-automation/bin. 28 local target_program_path_var="${1:-target_program_path}" ; shift 48 # ln -s select_version python 50 base_program_path=$(readlink -f "${0}") 55 echo -n "**ERROR** ${base_program_name} should never be called directly." 66 … # Now use the "type" built-in to search the PATH variable for a list of target program candidates. 67 candidates=$(type -ap ${alternate_program_name}) 70 # /home/robot/openbmc-test-automation/bin/python [all …]
|
H A D | robot | 10 # cd openbmc-test-automation/bin 11 # ln -s select_version python 13 # The PATH variable should contain the expanded path to openbmc-test-automation/bin. 28 local target_program_path_var="${1:-target_program_path}" ; shift 48 # ln -s select_version python 50 base_program_path=$(readlink -f "${0}") 55 echo -n "**ERROR** ${base_program_name} should never be called directly." 66 … # Now use the "type" built-in to search the PATH variable for a list of target program candidates. 67 candidates=$(type -ap ${alternate_program_name}) 70 # /home/robot/openbmc-test-automation/bin/python [all …]
|
/openbmc/openbmc-test-automation/docs/ |
H A D | code_standards_check.md | 10 Project [codespell](https://github.com/codespell-project/codespell) designed 24 ### 2. robotframework-lint 26 Project [robotframework-lint](https://pypi.org/project/robotframework-lint/) for 30 $ pip install –upgrade robotframework-lint 42 [custom rules](https://github.com/openbmc/openbmc-test-automation/blob/master/robot_custom_rules.py) 47 that Tags are equivalent to test case names or task names. 55 $ awk -f check_robot_tags.awk ~/openbmc-test-automation/redfish/test_xit.robot 56 --- /home/openbmc-test-automation/redfish/test_xit.robot:
|
H A D | openbmc_test_tools.md | 1 ## Tools used in OpenBMC Test Automation 8 $ ipmitool -V 12 ## Hardware Test Executive (HTX): 14 HTX is a suite of test tools for stressing system hardware. It is routinely used 15 by the test suites under `systest/`. Refer to 16 [README](https://github.com/open-power/HTX) 21 [README](https://github.com/openbmc/phosphor-logging/blob/master/README.md#remote-logging-via-rsysl… 25 Pre-requisite: A Power Linux system is required. 27 - Obtain the SEL (System Error Log) parser tools: 28 - Go to https://openpower.xyz/job/openpower/job/openpower-op-build/ [all …]
|
H A D | boot_test.md | 1 Boot test is one of the cornerstone of OpenBMC test infrastructure. 3 The boot plugins are used in the test and as well can be use a stand-alone 4 mechanism to test your system to run variety of supported boot sequences. 6 **Boot test sequence example:** 9 robot -v OPENBMC_HOST:xx.xx.xx.xx -v OPENBMC_PASSWORD:xxx -v 'boot_stack:<boot1>:<boot2>:<bootn>:' … 13 [data/boot_lists/All](https://github.com/openbmc/openbmc-test-automation/blob/master/data/boot_list… 18 robot -v OPENBMC_HOST:xx.xx.xx.xx -v OPENBMC_PASSWORD:xxx -v 'boot_stack:Redfish Power On:Redfish … 21 and it will give the following on the console the boot test report: 25 ---------------------------------------- ----- ---- ----
|
/openbmc/openbmc-build-scripts/jenkins/ |
H A D | run-meta-ci | 1 #!/bin/bash -xe 4 # This script is responsible for setting up a openbmc/openbmc build 5 # environment for a meta-* repository. 8 # WORKSPACE: Directory which contains the extracted meta-* 9 # layer test is running against 10 # GERRIT_PROJECT: openbmc/meta-* layer under test (i.e. openbmc/meta-phosphor) 11 # GERRIT_BRANCH: Branch under test (default is master) 16 GERRIT_BRANCH=${GERRIT_BRANCH:-"master"} 19 # TODO - Need test repo to branch 20 # git clone https://github.com/openbmc/openbmc-test-automation.git --branch ${GERRIT_BRANCH} --sing… [all …]
|
/openbmc/openbmc-test-automation/extended/ |
H A D | run_keyword.robot | 11 # This may contain a colon-delimited list of library/resource 22 # cd $HOME/git/openbmc-test-automation 23 # export PYTHONPATH=${HOME}/git/openbmc-test-automation/lib/ 25 # robot --outputdir=/tmp -v OPENBMC_HOST:barp01 -v 'keyword_string:Log To Console Hi.' 28 # robot --outputdir=/tmp -v OPENBMC_HOST:barp01 29 # -v 'keyword_string:${state}= Get State quiet=${1} ; Rpvar state' 30 # -v lib_file_path:state.py extended/run_keyword.robot 35 Test Tags Run_Keyword_Pgm 52 *** Test Cases ***
|
/openbmc/openbmc-tools/tof-voters/config/ |
H A D | rejected_patterns.yaml | 3 - openbmc/s2600wf-misc 4 - openbmc/witherspoon-pfault-analysis 7 - ".*-oem" 8 - "openbmc/google-.*" 9 - "openbmc/ibm-.*" 10 - "openbmc/intel-.*" 11 - "openbmc/meta-.*" 14 - "/COMMIT_MSG" 15 - "/PATCHSET_LEVEL" 20 - ".*/create_pel.*" [all …]
|
/openbmc/openbmc-build-scripts/scripts/ |
H A D | run-robot.sh | 1 #!/bin/bash -x 2 # Extract and run the OpenBMC robot test suite 4 # The robot test results will be copied to ${HOME} 7 # IP_ADDR IP Address of openbmc 8 # SSH_PORT SSH port of openbmc 9 # HTTPS_PORT HTTPS port of openbmc 14 # ROBOT_TEST_CMD Command to execute from within obmc robot test framework 15 # Default will be "tox -e qemu -- --include QEMU_CI tests" 21 MACHINE=${MACHINE:-"qemu"} 22 ROBOT_CODE_HOME=${ROBOT_CODE_HOME:-/tmp/$(whoami)/${RANDOM}/obmc-robot/} [all …]
|
H A D | get_unit_test_report.py | 3 # This script generates the unit test coverage report for openbmc project. 22 # https://github.com/openbmc/phosphor-dbus-monitor.git NO 23 # https://github.com/openbmc/phosphor-sel-logger.git;protocol=git NO 40 "openbmc-tools", 42 "openbmc", 43 "openbmc.github.io", 44 "phosphor-ecc", 45 "phosphor-pcie-presence", 46 "phosphor-u-boot-env-mgr", 47 "rrd-ipmi-blob", [all …]
|
/openbmc/openbmc/ |
H A D | README.md | 1 # OpenBMC chapter 3 …](https://jenkins.o… 5 OpenBMC is a Linux distribution for management controllers used in devices such 10 [D-Bus](https://www.freedesktop.org/wiki/Software/dbus/) to allow easy 13 ## Setting up your OpenBMC project 18 …mentation](https://docs.yoctoproject.org/ref-manual/system-requirements.html#required-packages-for… 38 git clone https://github.com/openbmc/openbmc 39 cd openbmc 49 The script needs to be sourced while in the top directory of the OpenBMC 60 [meta-phosphor/docs](https://github.com/openbmc/openbmc/blob/master/meta-phosphor/docs/supported-ma… [all …]
|
/openbmc/bmcweb/docs/ |
H A D | CLIENTS.md | 5 non-exhaustive list of tests and clients that bmcweb is expected to be 6 compatible with, they are split into a couple categories. Entries in the test 8 specification. Entries in the clients category are intended to host user-facing 18 Redfish-Service-Validator: A tool to verify through GET requests that bmcweb 20 <https://github.com/DMTF/Redfish-Service-Validator.git> 24 Redfish-Protocol-Validator: A tool to verify the protocol-level interactions 25 with the Redfish wire-protocol, and checks those against the Redfish 26 specification. <https://github.com/DMTF/Redfish-Protocol-Validator> 30 OpenBMC-test-automation: A tool based on robot framework for testing some 31 portion of the OpenBMC Redfish use cases. [all …]
|
/openbmc/openbmc-test-automation/ffdc/ |
H A D | README.md | 4 $ python3 collect_ffdc.py -h 10 -r, --remote TEXT Hostname/IP of the remote host 11 -u, --username TEXT Username of the remote host. 12 -p, --password TEXT Password of the remote host. 13 -port_ssh INTEGER SSH port value. [default: 22] 14 -port_https INTEGER HTTPS port value. [default: 443] 15 -port_ipmi INTEGER IPMI port value. [default: 623] 16 -c, --config TEXT YAML Configuration file for log collection. [default: 17 <local path>/openbmc-test-automation/ffdc/ffdc_config.yaml] 18 -l, --location TEXT Location to save logs [default: /tmp] [all …]
|
/openbmc/openbmc-test-automation/lib/ |
H A D | gen_call_robot.py | 4 This module provides functions which are useful to plug-ins call-point programs that wish to make e… 47 …# Environment variable TMP_ROBOT_DIR_PATH can be set by the user to indicate that robot-generated … 63 …# Environment variable SAVE_STATUS_POLICY governs when robot-generated output files (e.g. the log.… 104 …o set environment variable ROBOT_TEST_RUNNING_FROM_SB when ROBOT_TEST_BASE_DIR_PATH is not pre-set. 110 # - User sandbox: 111 …# If there is a <developer's home dir>/git/openbmc-test-automation/, ROBOT_TEST_BASE_DIR_PATH will… 112 # set to that path. Otherwise, we set it to <program dir path>/git/openbmc-test-automation/ 113 # - Not in user sandbox: 114 # ROBOT_TEST_BASE_DIR_PATH will be set to <program dir path>/git/openbmc-test-automation/ 126 suffix = "git/openbmc-test-automation/" [all …]
|
/openbmc/openbmc-test-automation/gui/lib/ |
H A D | utils_get_version.py | 39 openbmc-test-automation and return as a dictionary. 50 [google-chrome]: Not installed 58 [robotframework-angularjs]: 0.0.10 59 [robotframework-scplibrary]: 1.2.0 60 [robotframework-extendedselenium2library]: 0.9.1 66 for package in ["python", "python3", "robot", "firefox", "google-chrome"]: 67 # Note: "robot --version" returns 0x00000000000000fb. 70 package + " --version", valid_rcs=[0, 0x7F, 0xFB] 79 "robotframework-angularjs", 80 "robotframework-scplibrary", [all …]
|
/openbmc/openbmc-test-automation/redfish/update_service/ |
H A D | test_redfish_image_upload.robot | 2 Documentation Test upload image with invalid images. 3 ... This test expects the following bad tarball image files 13 # openbmc/openbmc-test-automation/blob/master/docs/code_update.md#generating-bad-firmware-image-for… 15 # Test Parameters: 33 Test Setup Printn 34 Test Teardown Test Teardown Execution 36 Test Tags Redfish_Image_Upload 43 *** Test Cases *** 182 Test Teardown Execution 183 [Documentation] Do the post test teardown. [all …]
|
/openbmc/docs/ |
H A D | features.md | 1 # OpenBMC Features 3 Follow links to learn more about OpenBMC features: 5 - [BMCWeb][] HTTP/Web server 6 - [WebUI Vue][] web application 7 - REST Management: [BMCWeb Redfish][], [Phosphor REST APIs][] includes [Host 9 - [D-Bus interfaces][] describes internal interfaces 10 - [D-Bus Object Mapper][] 11 - [Remote KVM][] 12 - [IPMI in band][] and [IPMI out of band][] 13 - Full IPMI 2.0 Compliance with DCMI [all …]
|
/openbmc/docs/designs/ |
H A D | physical-topology.md | 14 power supplies, connect to cables, and be cooled by fans. OpenBMC does not 20 [prior proposal](https://gerrit.openbmc.org/c/openbmc/docs/+/41468), but 27 Changes to phosphor-dbus-interfaces documenting new Associations have been 28 [proposed](https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/46806) 37 - Must represent one-to-many relationships from chassis inventory objects which: 38 - Connect to cables 39 - Contain other chassis and/or are contained by a chassis 40 - Contain storage drives 41 - Are cooled by fans 42 - Are powered by power supplies [all …]
|