Update test runner to run tests from metadata

This change adds functionality to the test runner script to search a
directory tree for generated test metadata files, build up a graph of
test groups, and run a user-specified list of groups with all of their
dependencies.

Tests are run through an external runner executable provided on the
command line. The executable is called with the path to a unit test
binary file.

The old test runner functionality to run a single test directly from its
binary path is maintained, but now uses a runner executable. This is
configured in GN using the build variable "pw_automatic_test_runner",
which replaces the functionality of "pw_unit_test_create_run_targets".

Change-Id: Ic1ed959d87a71266408e1f26e0ae1bf906eebfb0
7 files changed
tree: 1511df0e0292e9948a28648b99a05837f4ed056a
  1. docs/
  2. pw_bloat/
  3. pw_build/
  4. pw_cmd/
  5. pw_docgen/
  6. pw_dumb_io/
  7. pw_dumb_io_baremetal_stm32f429/
  8. pw_dumb_io_stdio/
  9. pw_preprocessor/
  10. pw_span/
  11. pw_status/
  12. pw_string/
  13. pw_toolchain/
  14. pw_unit_test/
  15. targets/
  16. .clang-format
  17. .gitignore
  18. .gn
  19. AUTHORS
  20. BUILD
  21. BUILD.gn
  22. BUILDCONFIG.gn
  23. CONTRIBUTING.md
  24. LICENSE
  25. modules.gni
  26. presubmit.py
  27. pw_vars_default.gni
  28. README.md
  29. WORKSPACE
README.md

Pigweed embedded oriented software libraries

Pigweed is a collection of embedded-focused libraries, which we call “modules”. These modules are designed for small-footprint MMU-less microcontrollers like the ST Micro STM32L452 or the Nordic NRF82832. The modules are designed to facilitate easy integration into existing codebases.

Pigweed is in the early stages of development.