qa-mobile

Automate exploratory mobile QA testing on iOS and Android apps with Appium.

Updated Mar 11, 2026

Search Tags:#testing #qa #mobile #regression #bug-tracking #appium #exploratory-testing

Ready to run

npx skills add https://github.com/jkhowland/jkhowland --skill qa-mobile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-mobile
Source: https://github.com/jkhowland/jkhowland/tree/main/.claude/skills/qa-mobile
Command: npx skills add https://github.com/jkhowland/jkhowland --skill qa-mobile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mobile QA teams spend excessive time manually exploring apps to find defects and verify fixes. qa-mobile automates exploratory testing with Appium MCP to surface bugs, capture evidence, and generate regression-ready reports.

Core Features & Use Cases

Exploratory testing: Navigate the app like a real user to discover issues not covered by predefined checklists.
Evidence-backed reports: Produce health-scored reports with before/after screenshots and page sources.
Regression-ready artifacts: Generate structured outputs and regression tests for future validation.

Quick Start

Ask the agent to qa the app and start a session using the default platform.

Frequently Asked Questions about qa-mobile

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

FAQPage Schema

How do I automate exploratory mobile testing to find regressions?▼

Automated exploratory mobile testing uses Appium to navigate apps like a real user, uncovering regressions and capturing before/after evidence to generate structured health-scored reports.

What is exploratory mobile QA and how does it capture bug evidence?▼

Exploratory mobile QA navigates apps dynamically to discover defects outside predefined checklists, capturing before and after screenshots and page sources to produce regression-ready artifacts.

Do I need an Appium workflow to run automated mobile app testing?▼

Yes, an Appium-based workflow is required to run automated exploratory mobile testing, along with an initial clean working tree and baseline session setup for iOS and Android apps.

Can I use exploratory testing for both iOS and Android apps post-merge?▼

Yes, exploratory testing applies during feature development or post-merge cycles on both iOS and Android apps to uncover regressions and generate a navigation map with structured reports.

What's the best way to generate health-scored reports for mobile app bugs?▼

Health-scored reports are generated by running automated exploratory mobile QA sessions that capture screenshots, page sources, and a navigation map to verify fixes and prove regressions.

Why does automated mobile QA require a clean working tree before starting?▼

A clean working tree ensures the baseline session setup accurately reflects the app state, allowing the exploratory testing workflow to isolate newly uncovered bugs and prove fixes effectively.