> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing the Connect Widget

We offer guides to test the following:

* [Member Connection Statuses with MX Bank](/resources/test-platform/mxbank/)
* [Microdesposits](/products/connectivity/microdeposits#test-scenarios)
* [OAuth in the Connect Widget with MXCU](/resources/test-platform/mxcu/testing-oauth-with-mxcu)
* [OAuth in WebViews](#oauth-in-webviews)

## OAuth in WebViews

To test OAuth in the Connect Widget when it's embedded in a WebView, you must load the financial institution's OAuth window in the device's native browser and properly handle the results. This can be tested in the integrations environment with the MXCU (OAuth) institution (institution code `mxcu_oauth`).

1. When you select **MXCU (OAuth)** from search or load Connect with the `current_institution_code` option set to `mxcu_oauth`, the OAuth requested UI event message will be generated. Capture the `url` from this payload.
2. Load the `url` in the device's native browser.
3. The user logs in and selects accounts.
4. The user selects either **Authorize** or **Deny**.
5. The browser is redirected back to MX.
6. The redirect renders either success or error.
   * Success is indicated by a `200 OK` response code.
   * Error is indicated by a `400 Bad Request` response code. **This includes cases where the user has declined/denied authorization.**
   * If MX doesn't get a response back from the financial institution, then you won't get a response either. This can happen, for example, if the user closes the browser.