Testing a mobile app makes sure it works well for users. You can check small pieces of code with unit tests. You can check the whole screen with UI tests. You can also test how different parts work together with integration tests. And you can measure speed and stability with performance testing.
This guide covers tools like Detox, Appium, and XCTest. These tools help you run tests automatically on both iOS and Android devices. Automatic tests save time and catch problems early. Write tests for the most important features first. Keep each test simple and separate from others.
Follow the best practices to avoid common mistakes. Test on real devices, not just simulators. Use meaningful names for your tests. Aim for high test coverage but focus on business logic. This approach leads to a reliable app that users can trust.
Global
mkdir -p ~/.claude/skills/mobile-app-testingProject
mkdir -p .claude/skills/mobile-app-testingSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step