Unit-Test support (opposed to integration-tests only)

[t-moe]

I have some ideas on how to tackle this already, but it needs some changes on the host-side as well and is a bigger endeavor

[t-moe]

Work in progress
https://github.com/probe-rs/embedded-test/tree/next
https://github.com/probe-rs/probe-rs/tree/embedded_test_v2

[kaspar030]

Work in progress https://github.com/probe-rs/embedded-test/tree/next https://github.com/probe-rs/probe-rs/tree/embedded_test_v2

This looks very promising! 👍

... can we put the elf parsing stuff into a library? We do have non-probe-rs runners, and we're in the process of adding tests that report over a serial channel.

[t-moe]

Do you mean the std tests with your custom runner ? ( https://github.com/kaspar030/embedded-test-std-runner )
Because I plan to re-add support for this runner. e.g. by collecting all the tests with linkme so that the list command still works...

Do you still need elf parsing in that case? I.e. is there some other runner I'm not aware of?

[kaspar030]

Do you still need elf parsing in that case? I.e. is there some other runner I'm not aware of?

Cool, then not having an elf parser is fine :)

[t-moe]

Making good progress here.

What works so far:

• Run unit tests (lib) on esp32c6 (riscv). Probe-rs reads them from ELF directly.
• Run unit tests (lib) on std with embedded-test-std-runner. Tests are collected with linkme crate and reported via json as before.

Things left to do:

• Test whether my ELF Symbols can be read by probe-rs on arm and xtensa.
  When I exported this symbol on x86, my test case would issue a SIGSEV in the dynamic loader 😮
  Is it ok, if I use your CI/CD cluster again @bugadani ?
• Test whether bin unit tests work
• Cleanup

[bugadani]

Is it ok, if I use your CI/CD cluster again

of course, please do