tree 83b358ccc9569f8b4bd2810440047fa46aba4bba
parent 236e2438f18d122646d50fb50f9dab3fa767f071
author Ed Tanous <edtanous@google.com> 1614374917 -0800
committer Brad Bishop <bradleyb@fuzziesquirrel.com> 1616772389 +0000

Implement bmcweb ptest

Yocto implements ptest classes for recipes.  In general OpenBMC doesn't
implement ptest for any of its recipes.  This is the first in an attempt
to change that, specifically, this enables ptest for the bmcweb recipe.

Examples for ptest + meson recipes are pulled from here:
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=inherits%3Aptest+inherits%3Ameson

This commit implements the base ptest functionalityrequired to be able
to install and run the unit tests already present in bmcweb.  The
specific changes are:
1. bmcweb recipe now inherits from ptest
2. When ptest is enabled, bmcweb now requires gtest and gmock
dependencies.  This is done by updating DEPENDS.  We also now require
bash at runtime, so that dependency is added, as that seems to be what
the upstream recipes do.
3. The meta-layer now includes a "run-ptest" script.  This seems to be
the common convention in the upstream yocto recipes to include in the
meta layer so we should do the same thing here for consistency, even if
it is a little unconventional or odd.

To enable this and try it out, insert the following into your local.conf
DISTRO_FEATURES_append = " ptest"
CORE_IMAGE_EXTRA_INSTALL += "bmcweb-ptest"

This will add bmcweb ptests to your build.  Keep in mind, this takes a
lot of flash space, so qemu is likely the best target, unless you're on
a system with eMMC, or a lot of SPI flash free.  Once your system has
booted, you can run the tests by executing ptest_runner.

https://wiki.yoctoproject.org/wiki/Ptest

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I8c45c98afb941953c1855de2f3db10deea465b2a