The triage report

The triage report provides a high-level overview of your most recent test run, and a longer history of Findings. Every time you launch a test, Antithesis generates a triage report and emails it to your team.

The pages below offer a detailed explanation of the triage report. We also have a list of common workflows to help you jump right in.

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.

For a given failure that you see in the Properties section, you can generate a causality analysis report, which gives you more information about the timing of events that trigger that bug.

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.

  • Introduction
  • How Antithesis works
  • Using Antithesis with AI
  • Get started
  • Setup guide
  • For Docker Compose users
  • For Kubernetes users
  • Test an example system
  • With Docker Compose
  • Build and run an etcd cluster
  • Add a test template
  • With Kubernetes
  • Build and run an etcd cluster
  • Add a test template
  • Product
  • Test templates
  • Creating test templates
  • Test commands
  • How to check a test template locally
  • How to port tests to Antithesis
  • Test launchers
  • The triage report
  • Findings
  • Environment
  • Utilization
  • Properties
  • Logs Explorer & multiverse map
  • Debugging
  • Causality analysis
  • Multiverse debugging
  • Advanced mode
  • The Antithesis multiverse
  • Querying with event sets
  • Environment utilities
  • Using the Antithesis Notebook
  • Cookbook
  • Tooling integrations
  • CI integration
  • Discord and Slack integrations
  • Issue tracker integration - BETA
  • Configuration
  • Access and authentication
  • The Antithesis environment
  • Best practices
  • Docker best practices
  • Kubernetes best practices
  • Optimizing for testing
  • Concepts
  • Properties and Assertions
  • Properties in Antithesis
  • Assertions in Antithesis
  • Sometimes Assertions
  • Properties to test for
  • Fault injection
  • Reference
  • Webhooks
  • Launching a test
  • Launching a debugging session
  • Webhook parameters
  • SDK reference
  • Define test properties
  • Generate randomness
  • Manage test lifecycle
  • Assertion catalog
  • Coverage instrumentation
  • Go
  • Instrumentor
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Java
  • Using the SDK
  • Building your software
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • C
  • C++
  • C/C++ Instrumentation
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • JavaScript
  • Python
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Rust
  • Instrumentation
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • .NET
  • Instrumentation
  • Tutorial
  • Assert (reference)
  • Lifecycle (reference)
  • Random (reference)
  • Languages not listed above
  • Assert (reference)
  • Lifecycle (reference)
  • Assertion Schema
  • Handling external dependencies
  • FAQ
  • Product FAQs
  • About Antithesis POCs
  • Release notes
  • Release notes
  • General reliability resources
  • Reliability glossary
  • Techniques for better software testing
  • Autonomous testing
  • Deterministic simulation testing
  • Property-based testing
  • White paper — How much does an outage cost?
  • Catalog of reliability properties for key-value datastores
  • Catalog of reliability properties for blockchains
  • Test ACID compliance with a ring test