Sebastian Scholz

Yeah, we wrote it ourselves.

I think it's been a while, but I think it uses Hyper as a web server.

I think it's called Hyper.

And basically it manages access to it.

At that time, so it has a web interface and at that time,

We wanted to kind of get fancy, and I have a little bit of a background in Flutter development as well.

So the web interface is based on Flutter, but the actual logic and the serving of the files is in Rust.

Exactly.

So this is one of the unfortunate truth.

If you do develop your own system, there's no one solution fits all kind of a thing.

So we did try to find generic solutions for embedded testing.

And I don't know how it looks right now, but a couple of years ago, two and a half years ago,

There wasn't really a lot that helped you write actual tests for the embedded target and run them.

So yes, this solution of the integration tests and the test suite itself is also a custom solution that we developed in Rust as well.

So the whole integration test suite is also written in Rust and developed in-house.

Yes, pretty much.

So basically, it's a binary that has all of the tests in it.

And then we just upload this binary to the hardware and then let it run.

And we look at the output via a communication protocol.

I think for that, we use just UART, a very common low-level communication protocol.