> For the complete documentation index, see [llms.txt](https://docs.sharelogic.com/unifi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharelogic.com/unifi/4.4/test/test-scenarios.md).

# Test Scenario

An Integration Test Scenario represents a Transaction on a Bond. Each contains the relevant Test Scenario Data objects for the particular Scenario.

## Fields

![](/files/2pz9YQDmJ8Qce0j7RTMX)

The following table describes the fields which are visible on the Integration Test Scenario record.

| Field            | Type      | Description                                                                                                            |
| ---------------- | --------- | ---------------------------------------------------------------------------------------------------------------------- |
| Name             | String    | The name of the Test Scenario. Automatically populated from the Transaction and the Message used to generate the test. |
| Integration test | Reference | The Integration Test this Test Scenario belongs to.                                                                    |
| Type             | Choice    | Automatically populated. Choices include: Inbound Async, Inbound Sync, Outbound Async, Outbound Sync                   |
| Order            | Integer   | The order in which each Test Scenario is run (defaulted to match the order of Transactions on the originating Bond).   |
| Description      | String    | Use this to enter a description for your Test Scenario.                                                                |

## Related Lists

The 'Integration Test Scenario Data' related list is also visible on the Integration Test Scenario record.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sharelogic.com/unifi/4.4/test/test-scenarios.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.