Layer testing

[Bravo555]

In terms of testing the layer, we can highlight 2 parts:

1. Checking the validity of the recipes. I think this can be done easily as bitbake --dry-run can be used to not build the recipe, but only check if it can be built. This should be run for every recipe that we have, and can easily be run on a Github Actions runner, because it doesn't actually build any packages.
2. Runtime testing. If the thin-edge recipe can be built, then we should run the thin-edge.io integration test suite on a device running an image with thin-edge.io. This can be done on a qemu emulator, but we should make sure to also try to verify using an actual device, e.g. a raspberry pi. This can be tricky because AFAIK the test suite can require multiple devices to run some test cases, so we'll need to make sure if our understanding is correct, and if so, figure out a solution to this problem, in case we want to be able to run the test suite on demand on physical devices.

More on Yocto layer testing:

• https://docs.yoctoproject.org/4.3.2/dev-manual/runtime-testing.html
• https://docs.yoctoproject.org/4.3.2/ref-manual/release-process.html#testing-and-quality-assurance

Child issues

• Running RobotFramework test suite on Yocto #60