SaaSHub helps you find the best software and product alternatives Learn more →
Madness Alternatives
Similar projects and alternatives to madness
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
QEMU
Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are disabled. Please only use release tarballs from the QEMU website.
-
-
tigerbeetle
The financial transactions database designed for mission critical safety and performance.
-
-
-
-
-
promptfoo
Test your prompts, agents, and RAGs. Red teaming/pentesting/vulnerability scanning for AI. Compare performance of GPT, Claude, Gemini, DeepSeek, and more. Simple declarative configs with command line and CI/CD integration. Used by OpenAI and Anthropic.
-
-
-
-
instant
Instant is the best backend for AI-coded apps. You get auth, permissions, storage, presence, and streams — everything you need to ship apps your users will love.
-
cadence
Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
-
-
bufstream-demo
Discontinued A demo of Bufstream, a drop-in replacement for Apache Kafka that's 8x less expensive to operate and brings broker-side schema awareness to Kafka [GET https://api.github.com/repos/bufbuild/bufstream-demo: 404 - Not Found // See: https://docs.github.com/rest]
-
-
madness discussion
madness reviews and mentions
-
Inside the XRPL AI Red Team: What We've Found and Fixed
Antithesis (fault-injection testing). We use Antithesis, a continuous fault-injection platform, to run rippled under adversarial conditions - exploring behaviors that only emerge under concurrent load, partial failures, or unusual transaction ordering. This catches a different class of bug than static analysis: timing-dependent crashes and assertion failures that only appear when the system is under stress. Antithesis has already caught real bugs that we have shipped fixes for in production releases.
-
Should QA Exist
> Isolated QA should not exist because anything a QA engineer can do manually can be automated.
I almost entirely agree. You'd certainly want a majority of QA responsibilities to fall to devs since that keeps the feedback loop tight. Also with the amount of compute we have you can trivially outpace a typical QA team with a single dev working on fuzz tests and property based tests. If you really still feel the need to outsource then there are cool tools like Antithesis [1] which let you trade money for compute in their complicated fuzz testing suite.
Where that falls apart imo is when your software interacts with hardware in any non-trivial way. Fuzz testing doesn't really work when your system is spinning big and heavy things for example. Real hardware that interacts with the world will always create this gap where the devs don't know how to fully test it. Your systems engineers are best equipped to handle this and ensure certain controls follow the right curves, but they typically don't have the bandwidth or are very inexperienced with software. I think a QA organization _can_ fill this gap and deliver value. But I'd almost always prefer hiring another 1 or 2 system engineers who can work towards this problem full time instead. It's much easier to train someone in software than it is to train them in motor control or sealed systems.
[1] https://antithesis.com/
-
Testing Postgres race conditions with synchronization barriers
Loom does exhaustive search, with clever methods to prune it. On real world programs, you have to set a limit to that because it obviously grows extremely quickly even with the pruning.
I've built something similar to Loom, except it's more focused on extensively modeling the C++11/Rust memory model (https://github.com/reitzensteinm/temper). My experience is that fairly shallow random concurrent fuzzing yields the vast majority of all concurrency bugs.
Antithesis (https://antithesis.com/) are probably the leaders of the pack in going deeper.
- In Praise Of –Dry-Run
-
GenAI for Engineers, What's Real, What's Not and What's Coming
Antithesis: Runs containers to catch edge-case bugs in staging.
-
Testing is better than Data Structures and Algorithms
https://antithesis.com/ was made to deal with this. You can think of its as a fuzzing but it has overall determinism for the whole system, so there is a time travel and interactive debugging.
-
Zig Devlog: Self-Hosted x86 Back End Is Now Default in Debug Mode
Im pretty sure valgrind and friends can be used in zig.
Zig is still not 1.0, theres not much stability guarantees, making something like Frama-C, even tho it is possible is simply going to be soo much pain due to constant breakages as compared to something like C.
But it is not impossible and there have been demos of refinement type checkers https://github.com/ityonemo/clr
Beyond that, tools like antithesis https://antithesis.com/ exist that can be used for checking bugs. [ I dont have any experience with it. ]
-
Jepsen: Amazon RDS for PostgreSQL 17.4
Aphyr didn’t test foundation himself, but the foundation team did their own Jepsen testing which they reported passing. All of this was a long time ago, before Foundation was bought by Apple and open sourced.
Now members of the original Foundation team have started Antithesis (https://antithesis.com/) to make it easier for other systems to adopt this sort of testing.
-
XRPL Stability and Scalability Efforts
We leverage an autonomous testing platform called Antithesis to find bugs in our code. We provide the platform with workloads that test certain functionality, and the platform then performs fuzzing to try to make these tests fail. Antithesis helps us find the gnarly application bugs that we cannot otherwise detect easily when unintended but practical situations occur, such as a node crashing, the application is starved of cpu/memory, or a rare deadlock occurs.
-
The Evolution of SRE at Google
> Put another way, automated tests don’t go far enough. We need yet another higher layer of abstraction. Computers are better at deciding what tests to run and when, and are also better at interpreting the results.
Sounds like you might be interested in https://antithesis.com/ (no affiliation).
-
A note from our sponsor - SaaSHub
www.saashub.com | 9 Jun 2026
Stats
antithesishq/madness is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of madness is Nix.