The xPack solution to the challenge

[ilg-ul]

The xPack solution for executing multi-platform tests entails using various build configurations, each customised for a specific environment. These configurations incorporate their own dependencies, which may include different toolchains or even different versions of the same toolchain.

With such configurations defined, invoking the tests becomes straightforward.

Let's consider the @micro-os-plus/utils-lists project (a real life, fully functional project).

After satisfying the prerequisites (basically Node.js), the sequence of commands to run all tests is as follows:

rm -rf ~/Work/micro-os-plus/utils-lists-xpack.git && \
mkdir -p ~/Work/micro-os-plus && \
git clone \
  https://github.com/micro-os-plus/utils-lists-xpack.git \
  ~/Work/micro-os-plus/utils-lists-xpack.git

xpm run install-all -C ~/Work/micro-os-plus/utils-lists-xpack.git/tests
xpm run test-all -C ~/Work/micro-os-plus/utils-lists-xpack.git/tests

That's all!

These five commands will compile and execute the unit tests:

• As native processes on the development machine.
• As semihosted Cortex-M0/M3/M4/M7F/A15/A72 cross-applications emulated on QEMU Arm boards.
• As semihosted RISC-V RV32IMAC/RV32IMAFDC cross-applications emulated on QEMU RISC-V boards.

The tests are compiled using multiple toolchains:

• gcc 11, 12, 13 (native)
• clang 13, 14, 15, 16 (native)
• arm-none-eabi-gcc 11, 12, 13 (Cortex-M, AArch32)
• aarch64-none-elf-gcc 11, 12, 13 (AArch64)
• risc-none-elf-gcc 11, 12, 13 (RISC-V 32/64)

In total, there are over 160 variants of the same tests, executed by these commands!

Moreover, the aforementioned five commands can be used identically on Windows, macOS (x64/arm64), and GNU/Linux (x64/arm64).

Quite impressive, isn't it? Can you outdo that?