> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/v5.x-1/testing/testing-coldbox-applications/integration-testing/the-execute-method.md).

# The execute() Method

The `execute()` method is your way of making requests in to your ColdBox application. It can take the following parameters:

| Parameter Name        | Parameter Type | Required | Default Value | Description                                                                                                                                                               |
| --------------------- | -------------- | -------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| event                 | string         | `false`  | `""`          | The event name to execute. e.g., `"Main.index"`. Either an event or a route must be provided.                                                                             |
| route                 | string         | `false`  | `""`          | The route to execute. e.g., `"/login"`. The route parameter appends to your default SES Base Url set in `config/routes.cfm`. Either an event or a route must be provided. |
| queryString           | string         | `false`  | `""`          | Any parameters to be passed as a query string. These will be added to the Request Context for the test request.                                                           |
| private               | boolean        | `false`  | `false`       | If `true`, sets the event execution as private.                                                                                                                           |
| prePostExempt         | boolean        | `false`  | `false`       | If `true`, skips the pre- and post- interceptors. e.g., `preEvent`, `postHandler`, etc.                                                                                   |
| eventArguments        | struct         | `false`  | `{}`          | A collection of arguments to passthrough to the calling event handler method.                                                                                             |
| renderResults         | struct         | `false`  | `false`       | If true, then it will try to do the normal rendering procedures and store the rendered content in the RC as `cbox_rendered_content`.                                      |
| withExceptionHandling | boolean        | `false`  | `false`       | If true, then ColdBox will process any errors through the exception handling framework instead of just throwing the error.                                                |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox.ortusbooks.com/v5.x-1/testing/testing-coldbox-applications/integration-testing/the-execute-method.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.