pwa-device-testing

Test Progressive Web Apps and device features on Android emulators with Playwright and Appium.

2|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/flavordrake/mobissh --skill pwa-device-testing-flavordrake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pwa-device-testing
Source: https://github.com/flavordrake/mobissh/tree/main/.claude/skills/pwa-device-testing
Command: npx skills add https://github.com/flavordrake/mobissh --skill pwa-device-testing-flavordrake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the critical need to test Progressive Web Apps (PWAs) and specific device-dependent features that cannot be accurately validated using headless browser testing alone.

Core Features & Use Cases

  • Real Device/Emulator Testing: Run tests on actual Android emulators to catch issues missed by headless browsers.
  • Device-Specific Feature Validation: Crucial for testing features like Chrome password manager integration, WebAuthn biometrics, PWA installation, touch gestures, and safe-area insets on notched devices.
  • Use Case: Ensure your PWA's biometric login flow works flawlessly on an Android device, or verify that the "Add to Home Screen" prompt appears correctly and functions as expected.

Quick Start

Use the pwa-device-testing skill to set up and run tests on an Android emulator.

Frequently Asked Questions about pwa-device-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test PWA installation and biometric authentication on an Android emulator?

To test PWA installation and biometric authentication on an Android emulator, you can use this Skill to run Playwright and Appium tests. It validates device-specific features like WebAuthn biometrics and "Add to Home Screen" prompts that headless browsers cannot reliably access.

What is the best way to test Chrome autofill and touch gestures in a Progressive Web App?

The best way to test Chrome autofill and touch gestures in a Progressive Web App is by running tests on actual Android emulators. This approach captures real device interactions and password manager integrations that headless testing environments miss entirely.

Do I need Android SDK and ADB forwarding to test PWA features with Playwright?

Yes, you need Android SDK and ADB forwarding to test PWA features with Playwright. This Skill requires setting up AVDs and establishing ADB forwarding to enable Chrome DevTools Protocol connectivity for validating device-specific interactions.

Can I use Appium to validate safe-area insets on notched Android devices?

Yes, you can use Appium to validate safe-area insets on notched Android devices. This Skill enables testing these specific device-dependent PWA layouts on Android emulators to ensure visual elements adapt correctly to physical screen constraints.

Why does headless browser testing fail to validate WebAuthn biometrics in my PWA?

Headless browser testing fails to validate WebAuthn biometrics because it lacks the hardware and OS-level integrations required for device-specific features. This Skill solves the problem by running tests on Android emulators to accurately assess biometric authentication flows.