The expected flow of app information to Distributional for run creation within a project
Distributional testing requires more information than standard deterministic testing to address the motivating bullets (nondeterminism, nonstationarity, interactions) described earlier. Each time you want to measure the behavior of the app, Distributional wants you to:
1. Record outcomes at all of the app’s components, and
2. Push a distribution of inputs through the app to study behavior across the full spectrum of possible app usage.
The inputs, outputs, and outcomes associated with a single app usage are grouped in a **Result**, with each value in a result described as a **Column**. The group of results that are used to measure app behavior is called a **Run**. To determine if an app is behaving as expected, you create a **Test**, which involves statistical analysis on one or more runs. When you apply your tests to the runs that you want to study, you create a **Test Session**, which is a permanent record of the behavior of an app at a given time.
---
# 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.21.x/learning-about-distributional/the-distributional-framework.md?ask=
```
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.
