# Different use cases supported by Drizz

#### Multiapp Testing

Drizz AI enables seamless testing across multiple apps in a single session, ideal for workflows involving interconnected applications.

Key Commands:

• OPEN\_APP: Switch apps during tests.

• MINIMIZE\_APP + TAP: Simulate real-world actions like opening an app via the home screen.

• Example Use Case: Food delivery systems involving a Customer App and a Delivery Agent App.

Benefits:

• Greater flexibility for custom workflows.

• Realistic simulation of user actions.

#### API + Single App Testing

This feature integrates API testing within an app’s workflow to validate real-time data interactions.

• Key Commands:

• EXECUTE\_API: Fetch and validate API responses during a test.

• Example Use Cases:

• Weather apps: Verify API responses against app UI.

• E-commerce apps: Validate location-based offers fetched via APIs.

Benefits:

• Ensures end-to-end functionality.

• Synchronizes app behavior with real-time API data.

#### Mobile App + Web (MWeb) Testing

This feature integrates API testing within an app’s workflow to validate real-time data interactions.

Key Commands:

• EXECUTE\_API: Fetch and validate API responses during a test.

• Example Use Cases:

• Weather apps: Verify API responses against app UI.

• E-commerce apps: Validate location-based offers fetched via APIs.

Benefits:

• Ensures end-to-end functionality.

• Synchronizes app behavior with real-time API data.

#### Location-Based Testing

Drizz AI supports testing for apps relying on geolocation or GPS data.

Key Commands:

• SET\_GPS: Dynamically update the emulator’s location.

• KILL\_APP + OPEN\_APP: Restart apps to reflect updated GPS data.

• Example Use Cases:

• Delivery apps: Validate app behavior based on different user locations.

Benefits:

• Dynamic testing for location-sensitive features.

• Ensures consistency by restarting apps after location updates.


---

# 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.drizz.dev/different-use-cases-supported-by-drizz.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.