mobile-verification

Automate repeated mobile test runs with Pass@k verification across unit, UI, and Compose tests.

61|17|Updated Feb 2, 2026

Search Tags:#android #compose #flaky-tests #mobile-testing #testing-workflow #pass-at-k

Ready to run

npx skills add https://github.com/ahmed3elshaer/everything-claude-code-mobile --skill mobile-verification

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a comprehensive automated testing workflow with Pass@k metrics to identify flaky tests and unreliable mobile test results, helping teams improve reliability across Android, Compose, and UI testing.

Core Features & Use Cases

Pass@k verification levels (Quick, Standard, Thorough, Release) to quantify test reliability over multiple iterations.
Coverage across Unit tests, UI tests (Espresso), and Compose tests to guide Android app quality decisions.
Real-world workflows: detect flaky tests, apply fixes, and stabilize CI/CD with a structured verification process.

Quick Start

Use the mobile-verify command to run verification with a chosen k value, e.g. /mobile-verify --k=3, to validate your mobile test suite.

Frequently Asked Questions about mobile-verification

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

FAQPage Schema

How do I detect flaky tests in my Android mobile test suite?▼

Flaky tests are unreliable tests that pass and fail inconsistently. Use Pass@k verification to run your unit, UI, and Compose tests multiple times across Quick, Standard, Thorough, and Release levels, quantifying test reliability and revealing intermittent failures that single runs miss.

What's the best way to identify unreliable mobile tests before release?▼

Run repeated test iterations using Pass@k metrics at escalating verification levels. The mobile-verify command with a specified k value runs your Android and Compose test suite multiple times, exposing flaky behavior and guiding release-readiness decisions with structured diagnostics.

Can I use Pass@k verification for unit tests, UI tests, and Compose tests together?▼

Yes. Pass@k verification covers unit tests, Espresso UI tests, and Compose tests in a single workflow, applying consistent reliability metrics across all three test types to comprehensively assess Android app quality.

How do I stabilize CI/CD pipelines when mobile tests fail intermittently?▼

Apply the structured verification workflow: run Pass@k diagnostics to isolate flaky tests, apply fix strategies based on detected patterns, then re-verify with mobile-verify across Quick through Release levels until tests stabilize reliably.

What verification levels should I use for my Android testing workflow?▼

Four structured levels guide increasing rigor: Quick for fast feedback, Standard for routine checks, Thorough for comprehensive validation, and Release for final gate decisions. Each level applies Pass@k metrics to quantify test reliability at that rigor tier.