Emulators vs real devices in Testing Fundamentals - Framework Approaches Compared

Framework Mode - Emulators vs real devices

Folder Structure for Mobile Testing Framework

mobile-testing-framework/
├── config/
│   ├── environments/
│   │   ├── dev.config.json
│   │   ├── staging.config.json
│   │   └── prod.config.json
│   └── devices.config.json
├── tests/
│   ├── emulator/
│   │   ├── login.test.js
│   │   └── navigation.test.js
│   └── real-device/
│       ├── login.test.js
│       └── navigation.test.js
├── pageObjects/
│   ├── LoginPage.js
│   └── HomePage.js
├── utils/
│   ├── deviceManager.js
│   └── testHelpers.js
├── reports/
│   └── latest-report.html
└── config.js
  

Test Framework Layers

• Device Layer: Manages connection to emulators or real devices using deviceManager.js.
• Page Objects: Encapsulate UI elements and actions for screens like LoginPage and HomePage.
• Test Layer: Contains test scripts separated by device type (emulator or real device).
• Utilities: Helper functions for device setup, teardown, and common test actions.
• Configuration: Holds environment settings and device capabilities for emulators and real devices.

Configuration Patterns

• Environment Configs: Separate JSON files for dev, staging, and production environments.
• Device Config: devices.config.json defines emulator types (e.g., Android API level) and real device IDs.
• Dynamic Selection: config.js reads environment variables to select emulator or real device at runtime.
• Credentials: Stored securely outside the repo or injected via environment variables.

Test Reporting and CI/CD Integration

• Reports: Generate HTML or JSON reports saved in the reports/ folder after test runs.
• CI/CD: Integrate with pipelines (e.g., Jenkins, GitHub Actions) to run tests on emulators and real devices automatically.
• Notifications: Configure alerts for test failures via email or messaging tools.
• Device Farm Integration: Optionally connect to cloud device farms for real device testing in CI.

Framework Design Principles

• Separate Tests by Device Type: Keep emulator and real device tests organized to handle differences clearly.
• Use Page Object Model: Abstract UI interactions to reduce duplication and ease maintenance.
• Configurable Device Selection: Allow switching between emulators and real devices without code changes.
• Explicit Waits and Stability: Use waits to handle device performance differences and avoid flaky tests.
• Secure Credential Management: Never hardcode sensitive data; use environment variables or secure vaults.

Self Check

Where in this folder structure would you add a new test for a real device login scenario?

Key Result

Organize tests by device type with configurable device selection and clear separation of concerns.