# Testing Integration **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: 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.orbiter.finance/developer/testing-integration.md?ask= ``` 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.