> For the complete documentation index, see [llms.txt](https://docs.orbiter.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbiter.finance/developer/testing-integration.md).

# Testing Integration

Run test transactions on mainnets.

**Importance of Running Test Transactions on Mainnets**

1. **Real Environment Validation**

* Mainnets provide the most realistic testing scenarios
* Validates actual fund flows and contract interactions
* Ensures all functionalities work properly in production

2. **Testnet Limitations**

* Most bridges and exchanges have limited testnet support
* Extremely low liquidity makes effective testing difficult
* Testnet environments may differ from mainnet

3. **Mainnet Advantages**

* Full liquidity support
* 100% functionality availability
* Direct validation of actual economic models

4. **Testing Recommendations**

* Start with small amounts for initial verification
* Gradually scale up testing volume
* Monitor all transaction statuses

5. **Important Notes**

* Ensure contracts have been audited
* Set appropriate gas limits
* Maintain complete transaction records

We strongly recommend conducting all integration tests on mainnets as this represents the best practice for ensuring system stability and functional integrity.

{% hint style="info" %}
To minimize costs, we recommend testing on chains with low gas fees. Optimism and other Layer 2 (L2) chains are excellent choices for cost-effective testing.
{% endhint %}


---

# 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://docs.orbiter.finance/developer/testing-integration.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.