awesome-mobile-testing-agent-skills

Expert guidance on detecting mobile performance regressions — startup time, frame jank, scroll performance, binary size — with baselines and noise-aware thresholds. Use when setting up perf gates in CI or when a release is suspected of regressing.

Measure code coverage honestly across mobile stacks — JaCoCo (JVM), llvm-cov (iOS), lcov (Flutter), Jest (RN) — and report it to Codecov / Coveralls without chasing meaningless numbers. Use when setting up coverage or when asked to raise a coverage gate.

Expert guidance on running mobile test suites in CI — matrix design, caching, sharding, artifacts, required checks — without paying for slow, flaky runs. Use when configuring GitHub Actions, GitLab CI, Bitrise, or Codemagic for mobile testing.

Expert guidance on automated and manual accessibility testing for mobile apps — Espresso AccessibilityChecks, XCTest accessibility audits, Flutter a11y guidelines, RN a11y assertions. Use when adding a11y coverage or when asked how to catch accessibility regressions in CI.

Expert guidance on snapshot / golden image testing across mobile stacks — Paparazzi (Android), swift-snapshot-testing (iOS), golden_toolkit (Flutter), and RN snapshot tests. Use when asked to lock down UI visuals or catch unintended rendering regressions.

Compare and apply UI test tooling across mobile — Espresso, XCUITest, flutter_test / integration_test, Detox, and Maestro. Use when deciding which UI test layer fits a feature and how to structure selectors, waits, and page objects.

Expert guidance on writing fast, deterministic unit tests for mobile codebases across Kotlin, Swift, Dart, and TypeScript. Use when asked to structure unit tests, pick a runner, or apply the AAA pattern.

Guidance on choosing between fakes, stubs, and mocking libraries (MockK, Mockito, mocktail, ts-jest, Swift test doubles) for mobile unit tests. Use when asked to mock a collaborator or to decide which double to use.

Expert guidance on adding property-based tests to mobile codebases using kotest-property, SwiftCheck, glados (Dart), and fast-check (TS). Use when example-based tests feel incomplete or when testing parsers, serializers, and state machines.

Patterns for producing test data cleanly — builders, fixtures, and object mothers — across Kotlin, Swift, Dart, and TypeScript. Use when tests have noisy setup or when multiple tests drift on the "same" entity shape.

Root-cause and eliminate flaky tests in mobile suites. Use when a test passes sometimes and fails sometimes, when CI reruns are masking real bugs, or when a suite's flake rate is above budget.

Expert guidance on sharding and parallelizing mobile test suites across runners and devices with an eye on cost, flake, and debuggability. Use when the suite wall-clock is too long, or when device-farm bills are getting out of hand.

Expert guidance on scoping test automation investments, assigning ownership, choosing quality metrics, and keeping a mobile test suite economically viable. Use when asked "what should our test strategy be?" or when the test suite is becoming a cost center.

Expert guidance on running mobile tests on Firebase Test Lab, AWS Device Farm, BrowserStack App Automate, and Sauce Labs. Use when asked to set up device-farm coverage, design a device matrix, or compare vendors.

Decide when end-to-end tests pay off, how to budget flake, and how to split smoke vs full regression suites. Use when asked "should we add an E2E test for this?" or when an E2E suite has grown too slow or too flaky to trust.

Expert guidance on writing, running, and parallelizing Maestro YAML flows for cross-platform mobile E2E testing. Use when adding Maestro coverage, wiring Maestro to CI, or moving off Detox/Appium for smoke flows.

Expert guidance on consumer-driven contract tests for mobile apps using Pact. Use when mobile clients depend on backend APIs that evolve independently and staging smoke tests are slow or flaky.

Expert guidance on testing persistence layers (Room, SQLite, SQLDelight, Core Data, Drift, WatermelonDB) using in-memory databases and migration tests. Use when asked to test a DAO, a query, or a schema migration.

Expert guidance on integration tests that exercise the seams between layers (repo → network → DB → mapper) without the UI. Use when unit tests pass but a feature still breaks, or when a bug is only visible when multiple collaborators interact.

Expert guidance on stress-testing backends from a mobile client's point of view — throttled networks, realistic request patterns, and client-side behavior under load. Use when asked how the app behaves on bad networks or under backend slowdowns.