A diagnostic device’s output is stochastic: the same specimen can yield different outcomes — from the biological sample, the reagent chemistry, the electronics, or a firmware change. Conventional pass/fail testing misses this. An open-source, Rust-native framework, feotest makes device performance testable and monitorable: establish a statistically defined baseline, then continuously verify functional and temporal conformance with confidence intervals and auditable verdicts. A runnable medical-device example shows the whole loop, against the 2026 QMSR and EUDAMED evidence environment.
Probabilistic testing, native to Rust. A non-deterministic service is treated as a stochastic service: establish a statistical baseline, then verify the service still meets it — with confidence intervals, latency distributions, and auditable verdicts.
The frameworks, the websites, the GitHub org and the Maven coordinates have all moved from javai to mavai. Nothing breaks: old URLs 301-redirect, GitHub repo transfers forward automatically, and the final javai Maven artifacts carry relocation POMs. Here is what changed and what, if anything, you need to do.
The thing a punit author implements gets a more honest name. UseCase carried too many readings — UML, regulatory, generic product talk — and told an author nothing about what the artefact does in the probabilistic-testing context. ServiceContract names it for what it is.
First cut of a new authoring surface for punit. Test configuration moves from parameterised annotations into typed builder calls inside the test method body. Statistical early termination and the wider feasibility-gate audit are deferred from this alpha.
AI systems are increasingly subject to regulatory scrutiny, yet the testing tools available to most teams were designed for a deterministic world. Mavai is here to change that.
