⚡ Advanced Maestro Testing: Event Validation & AI-Powered Test Generation

Building reliable, scalable, and intelligent test automation for Android apps.

🧭 Introduction

In Part 1, we explored test structure, mocking, and authentication in Maestro. Now, we’re leveling up with advanced techniques that push your testing to production-grade reliability and speed:

✅ Validating analytics events with precision 🤖 Using AI-powered test generation for 10x faster test creation

Why it matters: Accurate event tracking means data-driven decisions. AI-powered test creation means faster, smarter testing workflows.

🎯 Part 1: Event Testing — Validating Analytics

💡 Why Test Events?

Every modern app fires analytics events to track user behavior — from product clicks to completed checkouts. When those events break, data gets corrupted → decisions go wrong → and yes, revenue suffers.

Without Event Testing:

Product clicked → Event fires? → Analytics Dashboard
                           ↓
                    ❌ Event missing
                    ❌ Wrong parameters
                    ❌ Incorrect values

With Event Testing:

Product clicked → Event fires → Test validates → ✅ Correct data

The impact of this approach goes beyond testing — it directly enhances how teams understand their users and products. With accurate marketing attribution, every campaign’s effectiveness becomes clearer, enabling better product decisions backed by real data. Precise revenue tracking ensures that business performance is measured correctly, while fewer blind spots in analytics lead to a more complete and trustworthy picture of user behavior.

🕵️ The Challenge: Events Are Invisible

UI tests are visual. You can tap and assert. But events? They’re network calls — invisible to the eye.

That’s where event capture infrastructure comes in 👇

┌─────────────┐
│     App     │
└──────┬──────┘
       │
       │ Fires event
       ▼
┌──────────────────┐
│ Analytics SDK    │
└──────┬───────────┘
       │
       │ Sends to network
       ▼
┌──────────────────┐
│ Event Interceptor│  ◄── Custom service captures events
│ (Local Service)  │
└──────┬───────────┘
       │
       │ Stores for validation
       ▼
┌──────────────────┐
│  Maestro Test    │  ◄── Custom commands query events
└──────────────────┘

App → Analytics SDK → Event Interceptor (Local Service) → Maestro Test

The system is composed of three main components: an event capture service running on localhost, a set of custom Maestro commands designed to assert and verify events, and a temporary storage layer that holds captured data for validation. Together, these components create a feedback loop that ensures events are accurately detected, validated, and analyzed during automated test runs.

Note: Infrastructure setup is project-specific. Patterns below show the testing approach.

🧱 Event Test Structure

appId: ${APP_ID}
tags:
  - event
  - product

appId: ${APP_ID}
tags:
  - event
  - product

onFlowStart:
  - runScript: "../../../base/constants/users/*Users.js"
  - runFlow:
      file: "../../../base/baseTest.yaml"
      env:
        MOCK_ENABLE: "true"
        MOCK_DOMAIN: "browsing"
        LOGIN: "true"
        LOGIN_EMAIL: "${output.testUsers.default.email}"
        LOGIN_PASSWORD: "${output.testUsers.default.password}"

onFlowComplete:
  - stopApp

# Clear previous events
- clearEvents: true

# Trigger the action
- tapOn: "Product Card"

# Validate the event
- assertEvent:
    label: "Product click fires with correct data"
    eventName: "product_click"
    parameters:
      - product_id
      - product_name
      - price
      - action
    rules:
      - product_id is string
      - product_name is string
      - price is string
      - action == "click"

Tip: Always clearEvents: true before asserting to avoid false positives.

🧩 Event Validation Patterns

• Dynamic Values → IDs, timestamps → product_id is string
• Static Values → Predictable values → action == "click"
• Partial Matches → URLs, categories → deeplink contains "myapp://product"

🔄 Event Sequence Testing

- clearEvents: true

# Product impression
- scrollUntilVisible:
    element: "Product Card"
- assertEvent:
    eventName: "product_impression"

# Product click
- tapOn: "Product Card"
- assertEvent:
    eventName: "product_click"

# Add to cart
- tapOn: "Add to Cart"
- assertEvent:
    eventName: "add_to_cart"

Effective event testing relies on a few key best practices. Always start by clearing existing events to avoid false positives, and use descriptive labels so each event’s purpose is immediately clear. It’s important to validate not only that events are fired, but also that their structure and count are correct. Test entire sequences rather than isolated actions to ensure logical event flow, and when possible, mock events to maintain consistency and eliminate external dependencies.

🤖 Part 2: AI-Powered Test Generation

🧱 The Manual Bottleneck

70 minutes per test × 100 tests = 117 hours (~15 days)

Manual testing is slow, repetitive, and error-prone.

🚀 Enter Cursor AI

Cursor AI is an intelligent code editor that seamlessly integrates with your existing test framework — reading your structure, learning your patterns, and generating consistent, high-quality tests in your own style. Beyond automation, Cursor refines tests interactively, allowing you to collaborate with AI as if it were a team member who truly understands your codebase.

⚙️ Setting Up AI Test Generation

Step 1: Create .cursorrules — The AI’s Instruction Manual

# In your maestro/ directory
touch .cursorrules

Inside .cursorrules, document your patterns and examples:

# Maestro Testing Rules

## Test Structure
1. appId: ${APP_ID}
2. tags (test type and domain)
3. onFlowStart (initialization)
4. onFlowComplete (cleanup)
5. --- separator
6. Test steps

## File Naming Convention
Pattern: test_{feature}_{scenario}.yaml
Examples:
- test_login_validCredentials.yaml
- test_browsing_singleItem.yaml
- test_search_filterByPrice.yaml

Event Testing Patterns:

- clearEvents: true
- tapOn: "Button"
- assertEvent:
    label: "Descriptive label"
    eventName: "event_name"
    parameters:
      - param_id
      - param_action
    rules:
      - param_id is string
      - param_action == "click"

Step 2: Train AI with Examples

You:

“Read test_login_validCredentials.yaml and test_browsing_singleItem.yaml. Use these patterns.”

Cursor AI: ✅ Analyzed 2 tests. Ready to generate similar ones.

Step 3: Generate Your First Test

# test_login_validCredentials.yaml
appId: ${APP_ID}
tags:
  - smoke
  - account

onFlowStart:
  - runScript: "../../../base/constants/users/*Users.js"
  - runFlow:
      file: "../../../base/baseTest.yaml"
      env:
        MOCK_ENABLE: "true"
        MOCK_DOMAIN: "account"
        LOGIN: "false"

onFlowComplete:
  - stopApp

---
- tapOn: "Login"
- tapOn: id: emailInput
- inputText: "${output.testUsers.default.email}"
- tapOn: id: passwordInput
- inputText: "${output.testUsers.default.password}"
- tapOn: id: loginButton
- waitForAnimationToEnd
- assertVisible: "My Account"
- assertVisible: "${output.testUsers.default.name}"

Time saved: 70 minutes → 3 minutes (95% faster!)

🧠 Batch Generation & Event Tests Creation

Cursor AI can generate multiple tests or complex event tests in minutes, e.g., a browsing flow with 11 parameters:

# test_event_browsingCompleted.yaml
appId: ${APP_ID}
tags:
  - event
  - browsing

onFlowStart:
  - runScript: "../../../base/constants/users/*Users.js"
  - runFlow:
      file: "../../../base/baseTest.yaml"
      env:
        MOCK_ENABLE: "true"
        MOCK_DOMAIN: "browsing"
        LOGIN: "true"
        LOGIN_EMAIL: "${output.testUsers.default.email}"
        LOGIN_PASSWORD: "${output.testUsers.default.password}"

onFlowComplete:
  - stopApp

---

- clearEvents: true
- tapOn: "Cart"
- tapOn: "Browsing"
- tapOn: "Complete Search"
- waitForAnimationToEnd
- assertEvent:
    label: "Browsing completed event with all required data"
    eventName: "browsing_completed"
    parameters:
      - order_id
      - total_amount
      - item_count
      - payment_method
      - shipping_method
      - currency
      - user_id
      - tax_amount
      - discount_amount
      - timestamp
    rules:
      - order_id is string
      - user_id is string
      - total_amount is string
      - item_count is string
      - tax_amount is string
      - discount_amount is string
      - currency == "USD"
      - shipping_method is string
      - payment_method is string
      - timestamp is string
- assertEventCount:
    eventName: "browsing_completed"
    count: 1

Time saved: 45 minutes → 2 minutes (96% faster!)

🧭 Best Practices for AI Test Generation

Building reliable AI-generated tests isn’t just about speed — it’s about structure and iteration. Start with clear rules in your .cursorrules file to give the AI a strong foundation. Then follow an iterative workflow: Generate → Review → Refine. Treat it as a collaboration rather than automation. As you work, document emerging patterns so future generations stay aligned, and batch similar tests to maximize efficiency. And most importantly, never skip human review — it’s what keeps automation intelligent and trustworthy.

💥 Combining Event Testing with AI

When you bring event testing and AI generation together, the results are transformative. You can generate an entire set of 20 browsing flow event tests in under 30 minutes — a process that would otherwise take nearly a full day of manual effort. The outcome? Consistent validation patterns, accurate parameter checks, complete coverage, and massive time savings. This combination doesn’t just scale your testing workflow — it reshapes it, allowing teams to focus on innovation instead of repetition.

🧩 Conclusion

In conclusion, event testing is the backbone of trustworthy analytics and data-driven product decisions. It ensures every user interaction is tracked accurately, turning insights into reliable action. When paired with AI-powered test generation, the impact multiplies — tests are created up to ten times faster, patterns stay consistent, and human error is minimized.

The key is balance: always clear events before assertions, validate with both static and dynamic rules, and let AI amplify your productivity rather than replace your judgment. By documenting your patterns in .cursorrules and keeping human review at the core, you build not just faster tests, but a smarter, more maintainable testing ecosystem

Resources

• Cursor AI
• Maestro Documentation
• Part 1: Test Structure & Mocking

This guide is based on maintaining 1,000+ tests with event validation and AI-assisted generation in production Android apps.

About Us

We’re building a team of the brightest minds in our industry. Interested in joining us? Visit the pages below to learn more about our open positions.

**Home — Trendyol Careers**