This repository contains testing infrastructure related to Trenchboot project. Tests are written for usage with Remote Testing Environment in Robot Framework. These platforms are currently supported.
The DUT needs to be connected with RTE as specified in apu-rte connection manual. Coreboot must be flashed for meta-trenchboot yocto tests to work correctly. To do that use coreboot/flash_coreboot.robot. After that os tests can be run correctly.
git clone https://github.com/3mdeb/testing-trenchboot.git
cd testing-trenchboot
git submodule update --init --checkout
virtualenv -p $(which python2) robot-venv
source robot-venv/bin/activate
pip install -r requirements.txt
Just replace the robot with:
docker run --rm -it -v ${PWD}:${PWD} -w ${PWD} 3mdeb/rf-docker
Commands below assume you have virtualenv with robot framework activated.
# run test `FB1.3...` from foo suite bar test cases
robot -t "FB1.3*" -L TRACE -v rte_ip:$RTE_IP -v config:$CONFIG -v fw_file:$FW_FILE ./foo/bar.robot
# run all test cases from foo suite bar
robot -L TRACE -v rte_ip:$RTE_IP -v config:$CONFIG -v fw_file:$FW_FILE -i $CONFIG ./foo/bar.robot
Of course you have to replace:
$RTE_IP- which is your RTE IP address, you can find it in variables.robot,$CONFIG- platform specific configuration for importing correct keywords and variables. List of supported platforms is shown below and all config files are located inplatform-configs/. It is also used with-iparameter to execute only the tests suitable for the given platform.$FW_FILE- path to firmware you want to use for given suite.
For example, to flash coreboot, type:
- method #1 (binary file exists locally on the user computer):
robot -L TRACE -v rte_ip:192.168.4.172 -v config:apu2 -v fw_file:./coreboot.rom ./coreboot/flash_coreboot.robot
- method #2 (binary file will be downloaded via FTP):
robot -L TRACE -v rte_ip:192.168.4.172 -v config:apu2 -v fw_version:v4.10.0.1 ./coreboot/flash_coreboot.robot
To run yocto tests and iPXE tests on asrock and supermicro platforms you must have preconfigured USB stick, with Trenchboot Yocto Image or iPXE loading image. USB Stick necessary for given tests must be set as primary boot option.
| Manufacturer | Platform | Firmware | Support | $CONFIG |
|---|---|---|---|---|
| PC Engines | apu2 | PC Engines coreboot fork | Full | apu2 |
| Asrock | R1000V | UEFI | Full | asrock |
| Supermicro | m11sdv-8ct-ln4f | UEFI | Full | supermicro |
| ASUS | KGPE-D16 | - | None | kgpe-d16 |
- Full - supported all test suites,
- Limited - supported basic tests - flashing firmware (coreboot/uefi) etc. [WIP],
- None - platform not yet supported (lack of config/tests) but listed for
enabling in the near future. This may also means that all of tests and configs
are in the
devstage.