I'm using Antithesis (@AntithesisHQ - the presenting sponsor of the podcast) more to better understand how they test deterministically to find bugs. For one, they have a test infra that can run hours worth of testing in minutes. Eg it ran 24 hours of testing (!!) in 33 minutes:
Positive users praise Antithesis's deterministic bug detection for compressing 24 hours of testing into 33 minutes, while negative users criticize the offputting demo booking and nontrivial setup required to try the service.
Antithesis wraps the system you are testing (the "system under test" or SUT) into a hostile testing environment, which is as extreme version of chaos engineering, and injecting faults.
In this specific case, ran code that has a one-in-a-million probability bug - and it reproduced it!
On how this platform works, behind the scenes: https://antithesis.com/docs/introduction/how_antithesis_works/
I'm using Antithesis (@AntithesisHQ - the presenting sponsor of the podcast) more to better understand how they test deterministically to find bugs. For one, they have a test infra that can run hours worth of testing in minutes. Eg it ran 24 hours of testing (!!) in 33 minutes:
Did a deepdive on Antithesis back in 2024, and their multiverse debugger that took years to build. It's now a free article (was paid): https://newsletter.pragmaticengineer.com/p/antithesis
Antithesis wraps the system you are testing (the "system under test" or SUT) into a hostile testing environment, which is as extreme version of chaos engineering, and injecting faults.
In this specific case, ran code that has a one-in-a-million probability bug - and it reproduced it!
On how this platform works, behind the scenes: https://antithesis.com/docs/introduction/how_antithesis_works/
@jgilbertson47 @AntithesisHQ yes! Did a deepdive two years ago on their multiverse debugger, but I'm only trying out the system now. That deepdive:
https://newsletter.pragmaticengineer.com/p/antithesis
@GergelyOrosz @AntithesisHQ I wish they made it easier to use their services instead of booking a demo first
@GergelyOrosz @AntithesisHQ This is cool. Are you going to dive deeper in a post?
@GergelyOrosz @AntithesisHQ try the multiverse debugger next, it blew my mind
@gbjuuuuggggf @AntithesisHQ yes. There's a nontrivial amount of setup to go thru first to wrap your own service to be tested, and a bunch of custom infra to test everything. I agree btw that the "book a demo" is offputting as a dev.