# Tests

Tests are the key tool within DBNL for asserting the behavior and consistency of Runs. Possible goals during testing can include:

* Asserting that your application, holistically or for a chosen column, behaves consistently compared to a baseline.
* Asserting that a chosen column meets its minimum desired behavior (e.g., inference throughput);
* Asserting that a chosen column has a distribution that roughly matches a baseline reference;

By default, your Project will be pre-populated with a test for the first goal above. This is the "App [Similarity Index](/v0.23.x/using-distributional/tests/reviewing-tests.md#similarity-indexes)" test which gives you a quick understanding of whether your application's behavior has significantly deviated from a selected baseline.

## What's in a Test?

At a high level, a Test is a statistic and an [assertion](/v0.23.x/using-distributional/tests/creating-tests/defining-assertions.md). Generally, the statistic aggregates the data in a column or columns, and the assertion tests some truth about that aggregation. This assertion may check the values from a single Run, or it may check how the values in a Run have changed compared to a baseline. Some basic examples:

1. Assert the `95th percentile` of `app_latency_ms` is less than or equal to `180`

<details>

<summary>Test Spec JSON</summary>

<pre class="language-json"><code class="lang-json"><strong>{
</strong>    "name": "p95_app_latency_ms",
    "description": "Test the 95th percentile of latency in miliseconds",
    "statistic_name": "percentile",
    "statistic_params": {"percentage": 0.95},
    "assertion": {
        "name": "less_than_or_equal_to",
        "params": {
            "other": 180.0,
        },
    },
    "statistic_inputs": [
        {
            "select_query_template": {
                "select": "{EXPERIMENT}.app_latency_ms"
            }
        },
    ],
}
</code></pre>

</details>

<figure><img src="/files/J7N6Muf9bYkJ2I879XWC" alt=""><figcaption></figcaption></figure>

2. Assert the `absolute difference of median` of `positive_sentiment_score` against the baseline is close to `0`

<details>

<summary>Test Spec JSON</summary>

```json
{
    "name": "median_sentiment_similar",
    "description": "Test the absolute difference of median on sentiment",
    "statistic_name": "abs_diff_median",
    "statistic_params": {},
    "assertion": {
        "name": "close_to",
        "params": {
            "other": 0.0,
            "tolerance": 0.01,
        },
    },
    "statistic_inputs": [
        {
            "select_query_template": {
                "select": "{EXPERIMENT}.positive_sentiment_score"
            }
        },
        {
            "select_query_template": {
                "select": "{BASELINE}.positive_sentiment_score"
            }
        },
    ],
}
```

</details>

<figure><img src="/files/2MQWjK1z3lvMCTO1Y5ph" alt=""><figcaption></figcaption></figure>

In the next sections, we will explore the objects required for testing alongside the methods for creating tests, running tests, reviewing/analyzing tests, and some best practices.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dbnl.com/v0.23.x/using-distributional/tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.