Skip to main content
Our SDKs allow you to define test properties — either in your test template or in your actual software. These properties are expressed as assertions and resemble the programming assertions that you’re likely familiar with. But unlike those, failed Antithesis assertions do not cause your program to exit. This is useful in test, because we may be able to escalate an assertion failure into a more severe bug. It also reduces the friction to running the exact same code in test and production. You can read more about how Antithesis evaluates these properties in the language-specific SDK documentation. Assertion cataloging is a required step to use Antithesis assertions. Read the relevant instructions in the language-specific SDK documentation. Properties you define using the SDKs will appear in your triage report and will be flagged as passing or failing in each of your test runs. Antithesis automatically collects detailed information based on properties you define and creates debugging artifacts at the moments when these assertions are evaluated.