# Before All

### Overview

The **Before All Component** initializes the test suite by sending signals to all test components in the flow, allowing them to reset their state before execution begins.

### Usage

This component ensures that all test-related components are in a clean state before running a test workflow, preventing unexpected results due to lingering state data.

#### Input Ports

| Port | Description                                             |
| ---- | ------------------------------------------------------- |
| `in` | Receives the trigger signal to start the test workflow. |

#### Output Ports

| Port  | Description                                                           |
| ----- | --------------------------------------------------------------------- |
| `out` | Emits a signal after all test components have acknowledged the reset. |

#### Processing Logic

1. **Receives Test Trigger**: Captures the initial test signal.
2. **Sends Reset Signal**: Notifies all connected test components to reset their state.
3. **Waits for Acknowledgment**: Ensures all components respond before proceeding.
4. **Outputs Start Signal**: Once all components confirm reset, it emits a signal to start the test flow.

### Notes

* **Ensures Clean Test Execution**: Resets all test-related components before execution.
* **Prevents State Issues**: Avoids leftover data affecting test results.
* **Works with Other Test Components**: Required in workflows utilizing components like `AfterAll` or `Assert`.

This component is essential for structuring test workflows by ensuring that every test begins in a predictable and controlled environment.


---

# 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.appmixer.com/connector-configuration/utils/test/beforeall.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.