Project that I think is exceedingly possible, but would be a bit time consuming, and I have no need for:
I think it would be pretty straightforward to replace a tool like ceedling/cmock with Rust to generate and orchestrate embedded C test cases.
Conversation
Use build-rs and cc-rs to handle the build system (instead of rake), use bindgen (or similar tools) to generate the APIs to test and mock, have a crate of handy building blocks, or just use std::collections.
No need to have a ruby env set up for embedded developers.
1
5
(this is NOT to trivialize the work that has gone into Ceedling! It is a very good project, and a ton of work has gone into it. That being said, I think Rust also has some benefits, particularly good tooling for FFI, that makes this a potential win. Still a ton of work to do tho)
1
2
But I think the ability to do something like:
rustctest --new . --from-cmake ./CMakeList.txt --testdir ./test
cd ./test
<edit some config files>
<write some unit tests in rust>
cargo test
Would be a pretty neat experience.
1
I guess if this is interesting to you: DM me, open for contracts :)
2
1
Replying to
I was thinking about moving my test code to Rust just this week... It's not really my first choice (if it were just me I would go for something more abstract like Haskell to replace current Lua code). However, the rest of the team would appreciate the choice of Rust for sure...
But this is FAR into the future I think.
Still stuck in a short-term cycle...