Fauvido Technologies builds the testing layer for physical computing. Our product Macrohill lets firmware teams test against a live emulation of their hardware: inject faults, author test cases with AI or by hand, run profilers (Memory, CPU in terms of instructions), and replay recorded sensor data. We also provide a CLI that can intergrate into your CI/CD pipeline and make E2E testing on every commit, on the emulated board, possible.
No reviews yetBe the first to leave a review for Fauvido Technologies
Maker
📌
I am a student and I work at a team which builds solar race cars. We've always had the problem of waiting for hardware to arrive before we can do any tests, or having everything work in the air conditioned room but when stepping in the sun ruined it (the irony of a solar car circuitry being messed up due to the sun). Hence, I came up with this idea, it's still in heavy development phase. But it would be awesome if you could play around with it!
Report
A CLI integration is great, but how about adding a web dashboard that visualizes profiling results across test runs. Would make it way easier for teams to spot regressions in CPU or memory usage at a glance instead of digging through CI logs.
Report
Maker
@kucuksahal10675 Hello! Do you mean profiling report across different firmware iterations? As in, you change the code and you want to see if you are utilizing the CPU better? If so, then yeah, this makes sense, this will get to that stage. Thanks for the input
Report
A CLI that plugs into CI is great, but can you add a way to export test runs as a standardized report like JUnit XML or SARIF. That would make the results drop straight into GitHub Actions or Jenkins without extra glue code and let devs see firmware regressions right next to their other test failures.
Report
Maker
@kumsalmnyj Hey! That's actually pretty smart and I didn't think about it. I am not sure what kind of reports do teams make for these things, so I'll do some research. Thanks for the valuable input!
Report
One thing that would really help our team: a way to share and reuse custom fault injection profiles across projects, maybe through a simple registry or versioned config files. Right now we keep recreating the same fault scenarios for each board family, and it gets messy fast.
Report
Maker
@rdvantunzwcz1 Hello! That makes sense. I am yet to develop this to a point where teams can share stuff, it's more catered towards individuals right now. In the future however, I will be letting teams handle their testing profiles in collab.
Report
finally a tool that gets how painful firmware testing really is. the fault injection on a live emulation alone is worth checking out.
Report
Maker
@ykselhzrer9n0b Hey, thanks man! Firmware testing indeed is painful.
A CLI integration is great, but how about adding a web dashboard that visualizes profiling results across test runs. Would make it way easier for teams to spot regressions in CPU or memory usage at a glance instead of digging through CI logs.
@kucuksahal10675 Hello! Do you mean profiling report across different firmware iterations? As in, you change the code and you want to see if you are utilizing the CPU better? If so, then yeah, this makes sense, this will get to that stage. Thanks for the input
A CLI that plugs into CI is great, but can you add a way to export test runs as a standardized report like JUnit XML or SARIF. That would make the results drop straight into GitHub Actions or Jenkins without extra glue code and let devs see firmware regressions right next to their other test failures.
@kumsalmnyj Hey! That's actually pretty smart and I didn't think about it. I am not sure what kind of reports do teams make for these things, so I'll do some research. Thanks for the valuable input!
One thing that would really help our team: a way to share and reuse custom fault injection profiles across projects, maybe through a simple registry or versioned config files. Right now we keep recreating the same fault scenarios for each board family, and it gets messy fast.
@rdvantunzwcz1 Hello! That makes sense. I am yet to develop this to a point where teams can share stuff, it's more catered towards individuals right now. In the future however, I will be letting teams handle their testing profiles in collab.
finally a tool that gets how painful firmware testing really is. the fault injection on a live emulation alone is worth checking out.
@ykselhzrer9n0b Hey, thanks man! Firmware testing indeed is painful.