Version 3 (modified by Vojtech Horky, 6 years ago) ( diff )

Extra opts

Automated testing of HelenOS in a virtual machine

Part of HelenOS continuous testing are also tests that are executed inside HelenOS. That is, we launch a VM (QEMU or MSIM at the moment) and check that command executed inside HelenOS gives the expected output. This page contains a brief overview of how to write such testing scenarios and how to run them.


For this to work, you need to have Python 3, QEMU, ImageMagick (i.e. convert command) and SED. For testing on mips32, you will also need MSIM, Xvfb (or Xephyr), xterm and xdotool.

The testing script is in the root of the CI repository. To try it, prepare a HelenOS image (or grab one from for one of the supported architectures. Here, we will assume you have downloaded HelenOS with binutils and PCC for amd64 into helenos-amd64-with-binutils-pcc.iso into clone of CI repository.

For this image, we choose to run a scenario where we compile and run a Hello, World! program written in C. Scenarios are located under scenarios folder in CI repository, their format will be described later on.

To actually run the scenario, we launch the script and specify path to the boot image, architecture and path to the scenario. Advanced options will be described later.

./ \
    --arch amd64 \
    --image helenos-amd64-with-binutils-pcc.iso \
    --scenario scenarios/coast/pcc/hello.yml

When you run this script, you will see that it starts QEMU with HelenOS and waits until the terminal appears. Then it automatically types commands that compiles hello.c and launches the compiled a.out binary. QEMU is then terminated and if all went okay, we will see a message about successful pass of the scenario (or error message explaining the reason for failure).

The use described in the paragraphs above is the basic usage. Usually, we would like to run the scenario without actual QEMU window (as not to distract us) and maybe dump all the contents of the terminal session. Switches for just right that are here:

Hides any windows, i.e. we can run the script on background or on CI server.
--memory MB
Change the amount of memory available to the virtual machine.
--pass OPTION
Extra options to pass through to the emulator (can be specified multiple times).
--vterm-dump FILENAME.txt
Where to store dump of the whole terminal session.
--last-screenshot FILENAME.png
Where to store screenshot just before the VM is terminated.
Prints (a lot of) debugging messages.
Note: See TracWiki for help on using the wiki.