Image Types:

basesdk-amd64 / sdk-amd64

Image Deployment:

APT

Type:

functional

Description

Ensure that the sample image recipes can be built on the SDK and that the commands in the documentation work.

---

Pre Conditions

1. Clone the tests repository from another computer (Note that the branch being tested may change depending on the release, please make sure to clone the correct branch for the release in question):

$ git clone --branch apertis/v2024dev3 https://gitlab.apertis.org/infrastructure/apertis-image-recipes.git

2. Copy the test directory apertis-image-recipes to the target device:

$ DUT_IP=<device-ip>

$ scp -r apertis-image-recipes user@$DUT_IP:

3. Log into the target device:

$ ssh user@$DUT_IP

4. Plenty of free storage space must be available as the test will consume up to 15GB
5. Network connectivity on the DUT as these tests fetch packages and data over the network.

---

Execution Steps

1. add `run-test-in-systemd` to the PATH

$ PATH=$(pwd)/apertis-tests/common/:$PATH

2. build under /home which has enough storage space

$ sudo -u user cp -a ./apertis-image-recipes ~user/ && cd ~user/apertis-image-recipes

3. VirtualBox doesn't support nested KVM virtualization, so remove the
4. kvm module. This should trigger the chroot-based Debos backend instead
5. of the fakemachine one

$ modprobe -r kvm_intel

$ run-test-in-systemd --user=user --timeout=5min --name ensure-no-kvm test ! -e /dev/kvm

$ run-test-in-systemd --user=user --timeout=180min --name test-sample-documentation test/test-sample-documentation

---

Expected

The automated test should succeed

Notes

• Lots of debos messages will be logged on the standard output. Upon test fail, the script will abort with:

Job for generated-test-case-test-sample-documentation.service failed because the control process exited with error code.

>See "systemctl --user status generated-test-case-test-sample-documentation.service" and "journalctl --user -xe" for details.

>Command exited with non-zero status 1