[Question] Support for no_std and custom test-framework?

[TornaxO7]

Hello! I'd like to ask if this crate supports two features:

1. Can I use nextest in a no_std environment?
2. Can I implement my own test-framework with nextest?

Context

I'm currently trying to implement a kernel in rust, so I'd need to tell cargo somehow to start qemu and running the executable in it. Sadly, the provided custom_test_framework feature gives me a lot of problems and it's eRFC is sadly closed. So it's not easy (or with only a lot of work) to have a working testing environment without std.

[sunshowers]

Thanks for the questions?

Can I use nextest in a no_std environment?

Nextest itself isn't no_std compatible, however you can run no_std tests for it using a target runner. I think based on what you've described, trying out a target runner might be the best approach.

Can I implement my own test-framework with nextest?

I'm not entirely sure what this means. Nextest is open source and you're free to do whatever you like with it, of course. But nextest is a custom test runner, not a framework or harness.

[TornaxO7]

Ok, thank you for the information!