Skip to main content
Version: master

Testing meta-erlang

meta-erlang is tested at three levels during development:

Most test scripts are written using Lux (LUcid eXpect scripting). Lux is written in Erlang and is well suited for testing interactive programs such as the Erlang shell, which makes it a natural fit for this layer.

Testing Packages With ptest​

Not all recipes in meta-erlang provides ptest packages yet. Where available, they follow the ptest conventions and can be run on the target. Ptest support is a work in progress.

To include ptest packages in an image, add the following to conf/local.conf:

DISTRO_FEATURES:append = " ptest"
EXTRA_IMAGE_FEATURES += "ptest-pkgs"

Then, on the target, run:

ptest-runner

Performing Automated Runtime Testing​

Runtime tests are written using the oeqa framework. They are Python scripts that inherit from oeqa test classes and run on the target system.

The layer organizes these tests as follows:

PathDescription
<meta-erlang>/lib/oeqameta-erlang oeqa integration
<meta-erlang>/lib/oeqa/runtime/casesoeqa test cases; wrappers that copy Lux scripts to the target and run them
<meta-erlang>/lib/oeqa/runtime/files/luxLux test scripts

oeqa sets up the environment (booting the image, copying files, connecting to the target). Lux then performs the actual test logic on the target.

Running the runtime tests​

Enable testimage in conf/local.conf:

IMAGE_CLASSES += "testimage"
TEST_SUITES = "ping ssh beam"

Build the image and run the tests with QEMU:

bitbake core-image-minimal
bitbake core-image-minimal -c testimage

Test results and logs are written to tmp/log/oeqa/

Automated test suites for the meta-erlang layer​

The third level provides end-to-end automation. The <meta-erlang>/tests folder combines bitbake-setup and Lux scripts to exercise the full build and test process.

See <meta-erlang>/tests/README.md for details on how to run these tests.