> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/different-use-cases-supported-by-drizz/mweb-+-single-app.md).

# MWeb + Single App

Drizz AI enables you to seamlessly test workflows involving both a mobile app and a website. This is particularly useful for scenarios where actions in an app need to be verified or complemented through a web interface.

Let’s explore how to execute such test cases effectively.

#### **Scenario: Verifying an Order on a Website**

Suppose you are testing an e-commerce app where an order is placed via the app, and you need to verify the order details on the corresponding website.

#### **Step-by-Step Workflow**

**Place the Order in the App:**\
Use appropriate commands to log in, browse items, and place the order in the mobile app.

Example:

| TAP Place Order Button |
| ---------------------- |

**Switch to the Browser:**

\
Use the **OPEN\_APP** command to launch the browser for website verification.

| OPEN\_APP:(com.android.chrome) |
| ------------------------------ |

**Navigate to the Website:**\
Enter the website URL and perform the search or navigation.

### **Here is a video that demonstrates its functionality.**

In this video, we showcase how Drizz AI’s MWeb functionality allows for seamless cross-platform data validation. The test case involves checking the price of Bitcoin on an app and validating it against the real-time price shown in a web browser.

Steps Demonstrated:

1. Tap on Bitcoin in the app to view its price.
2. Launch the Chrome browser using the OPEN\_APP command.

 3\. Validate that the Bitcoin price displayed in the app matches the price on the web browser.

4. Terminate the Chrome app session using the KILL\_APP command.

This demonstration highlights the efficiency of Drizz AI in handling complex validation scenarios across apps and browsers.

{% embed url="<https://youtu.be/rmE23fYH6DY>" %}

#### **Validate the Order Details:**

\
Use Drizz validation commands to check the order details on the website.

| validate that the order\_id on [www.example-ecommerce.com](http://www.example-ecommerce.com) matches the order\_id in the app |
| ----------------------------------------------------------------------------------------------------------------------------- |

#### **Key Points to Remember**

* **Dynamic Data Handling:** Use response data from the app to validate fields on the website (e.g., order ID, customer name).
* **Browser Navigation:** Ensure you include the correct sequence of navigation and search steps within the browser.
* **Accurate Validation:** Validate the displayed data on the website using Drizz commands to ensure consistency with the app.

#### **Best Practices**

1. **Combine Commands for Seamless Flow:** Use a mix of action and validation commands to maintain consistency between app and web workflows.
2. **Leverage OPEN\_APP Command:** Ensure smooth transitions between app and browser without restarting the session.
3. **Use Dynamic Inputs:** Populate website search or input fields dynamically using data captured in the app (e.g., order number or user details).
4. **Cross-Platform Validation:** Always compare data between the app and the website to confirm accuracy.

By following this approach, you can confidently test interconnected workflows involving both a mobile app and a web interface, ensuring end-to-end validation of complex user scenarios.