Antithesis Docs Home

Welcome to Antithesis

Antithesis is an autonomous testing platform that finds the bugs in your software, with perfect reproducibility to help you fix them. It supplements or replaces your existing testing tools and lives alongside your normal CI workflow.

Our platform integrates property-based testing, fuzzing, and deterministic simulation into a single testing tool.

Combining these approaches offers three key benefits:

1. You can test better by spending more compute time, not more developer time.
2. It finds bugs that you don’t know you have to look for.
3. It finds really hard bugs.

Using Antithesis

1. The first thing you’ll do is upload your software to a private container registry.
2. You’ll also upload a test template to exercise it.
3. From here, everything will run in our deterministic testing environment. Kick off a test with a simple webhook, and a few hours later…
4. You’ll get an email with the results for your team to triage.
5. If there are any bugs, we have a time machine that will help you fix them.

A word of encouragement

Antithesis is fundamentally self-service, but right now it’s also a little opaque.

Setup is done via CLI. You communicate with the platform using webhooks, and receive debugging artifacts in return. The one actual UI in the system is our fully reactive debugging tool, the Antithesis Notebook.

We’ll be adding better interfaces soon, but even now, you’re not alone!

If you run into trouble, or have a particularly complex system to bring under test, or simply want to make sure your testing is as thorough as possible, our Solutions Engineering team would be happy to help – the best way to reach us is to join our Discord.

We’re confident that however you integrate Antithesis into your DevOps cycle, it will empower your team to move faster and build fearlessly, knowing that you’ll find and fix issues before they actually become problems.

What next?

To learn more about how Antithesis works, start here, or just follow the table of contents.

If you’re ready to get started, contact us to request a container registry and credentials. Once you have those, you can go through our tutorials or dive right in.