Skip to main content
Antithesis generates two types of reports based on your testing. The triage report provides a high-level overview of your most recent test run, and a longer history of Findings. Every time you run a test, Antithesis generates a triage report and emails it to your team. From the triage report, you can request a bug report containing detailed information about a particular issue that Antithesis found. The pages below offer a detailed explanation of the triage and bug reports. We also have a list of common workflows to help you jump right in.

​
The triage report

The main sections of the triage report are:
  1. Findings summarize calls to action based on your test (for most users, this is the most important piece).
  2. Environment, a description of the software that was tested.
  3. Utilization, high-level statistics about the run as a whole.
  4. Properties, individual pass/fail information about each of your test properties.
The pages above are based on our interactive example triage report, which was generated from an actual Antithesis test run. We encourage you to open it in another tab and follow along.

​
The bug report

The main sections of the bug report are:
  1. Context, Instance, and Logs, which show details of the issue you’ve chosen to examine. The rest of the report reacts to the context set here.
  2. Bug likelihood over time, which shows when the behavior was baked in.
  3. Statistical debug information, which shows the areas of code most strongly associated with the bug.
The pages above are based on our interactive example bug report, which was generated from an actual Antithesis test run. We encourage you to open it in another tab and follow along.