What is Antithesis? How we're different Problems we solve Security approach Demo Fintech Blockchain Customer stories Working with Antithesis Contact us Backstory Leadership Careers Brand

Product FAQs

1. How can I validate my setup?

You can manually validate your setup by running docker-compose up locally and verifying that all services are running as expected. If this happens, you should be able to call basic_test webhook successfully.

To streamline this process, you can automate it using a GitHub Action. The example workflow includes steps to build the project, validate the local setup, run and validate test commands, and finally call the basic_test endpoint.

We recommend setting up either this or a similar workflow in your CI pipeline.

2. How can I validate test composer commands locally?

To validate your test composer commands locally:

  • Run docker-compose up to bring up your system.
  • Run the individual test commands using docker exec <container_with_command> path/to/test-file/. <container_name> is the container containing the test command.

If the test commands run successfully then you’re good to kick off an actual test. This page has more details.

3. How often should we test?

Most Antithesis customers run tests nightly to catch bugs and regressions as early in development as possible, and some also run shorter tests on every commit to help reduce the feedback cycle for active development.

  • Nightly tests:

    • Run for 6-8hrs.
    • Uncover bugs that are hard to find. The longer a test runs, the more states are explored.
  • Short tests:

    • Run on a commit to the main development branch.
    • Run for ~30min - 1hr.
    • Catch simple bugs that slipped through conventional unit and end-to-end tests.

4. Is there a way to bias test runs? If I believe there’s a bug in subsystem X can I get Antithesis to apply more effort to a subset of our tests?

Yes, there are several ways to focus on a particular subsystem:

5. Which S3 mocks do you support?

We support MinIO and Localstack services. This page has more details, and a long list of mocks for other dependencies.

6. Why isn’t MY question covered here?

Probably because we don’t know about it! Please drop us a line at support@antithesis.com or ask us on Discord.

  • Introduction
  • How Antithesis Works
  • Tutorial
  • Testing with Antithesis
  • Build and run an etcd cluster
  • Meet the Test Composer
  • User manual
  • Setup guide
  • Properties and Assertions
  • Properties in Antithesis
  • Assertions in Antithesis
  • Sometimes Assertions
  • Properties to Test For
  • Test Composer
  • Test Composer Basics
  • Test Composer Reference
  • Principles of Test Composition
  • Checking Test Templates Locally
  • Webhooks
  • Launching a test
  • Retrieving logs
  • Launching a debugging session
  • Webhook API
  • Reports
  • The triage report
  • Findings
  • Environment
  • Utilization
  • Properties
  • The bug report
  • Context, Instance, & Logs
  • Bug likelihood over time
  • Statistical debug information
  • Search dashboard & multiverse map
  • Multiverse debugging
  • Overview
  • The Antithesis multiverse
  • Querying with event sets
  • The Environment and its utilities
  • Using the Antithesis Notebook
  • Cookbook
  • Antithesis' testing environment
  • The Antithesis Environment
  • Fault Injection
  • CPUID
  • Reference
  • Handling External Dependencies
  • SDK reference
  • Go
  • Tutorial
  • Instrumentor
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Java
  • Tutorial
  • Instrumentation
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • C
  • C++
  • Tutorial
  • C/C++ Instrumentation
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • JavaScript
  • Python
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Rust
  • Tutorial
  • Instrumentation
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • .NET
  • Languages not listed above
  • Assert (reference)
  • Lifecycle (reference)
  • Tooling integrations
  • CI integration
  • Discord and Slack integrations
  • Configuring Antithesis
  • Instrumentation
  • User management
  • Sizing your deployment
  • Best practices
  • Docker best practices
  • Is Antithesis working?
  • Optimizing for Antithesis
  • Finding more bugs
  • FAQ
  • About Antithesis POCs
  • Product FAQs
  • Release notes
  • Release notes