# Transaction Tests

ThousandEyes transaction tests are scripted synthetic user interactions with web-based applications such as e-commerce or online banking. Unlike the page load test, which only checks if the front page responds, a transaction test can traverse multiple pages and user actions. Transaction tests run on ThousandEyes Cloud and Enterprise Agents using a component called BrowserBot, running Google’s Chromium browser.

{% hint style="info" %}
If you need to run a test that solely consists of API calls, and don’t need to emulate a user journey in a browser, use the [API Test Type](https://docs.thousandeyes.com/product-documentation/api-test/).
{% endhint %}

Sections on transaction tests:

* [Getting Started with Transaction Tests](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/getting-started) - Start here if you’re new to transaction tests or browser synthetics. Pages include when to use a transaction test, generating tests scripts, and how you can use transaction test metrics in alerts and dashboards.
* [Transaction Test Development Guide](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/development-guide) - Refer to this section when you’re ready to start tweaking your test scripts or writing custom JavaScript code.
* [Use Cases | Code Examples](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/use-cases) - This section outlines a few of the more common use cases for transaction tests, and describes how to use the ThousandEyes scripting repository to find more examples.


---

# 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.thousandeyes.com/product-documentation/browser-synthetics/transaction-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.