- Home
- Skills
- Secondsky
- Claude Skills
- Mobile App Testing
mobile-app-testing_skill
- TypeScript
52
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill secondsky/claude-skills --skill mobile-app-testing- SKILL.md2.5 KB
Overview
This skill provides a production-ready approach to mobile app testing covering unit tests, UI automation, and performance checks. It includes patterns and examples for React Native, iOS, and Android, plus guidance for test infrastructure and device farms. The focus is practical: reduce flakiness, validate critical user flows, and keep tests maintainable and fast.
How this skill works
The skill maps the testing pyramid to concrete tools: Jest/XCTest/JUnit for unit tests, Detox/Espresso for integration, and Appium/Detox for end-to-end scenarios. It supplies examples for common flows (login, cart calculations) and prescribes mocking, device selection, and CI strategies. Use it to inspect failing tests, configure frameworks, or design a balanced test suite across layers.
When to use it
- Setting up or standardizing test infrastructure for a mobile project
- Adding E2E or UI automation for critical user journeys
- Diagnosing flaky tests or platform-specific test failures
- Planning test coverage and shifting-left testing efforts
- Integrating device farm runs into CI/CD pipelines
Best practices
- Start with unit tests for business logic before automating UI flows
- Mock external dependencies to keep tests deterministic
- Automate only critical user flows in E2E to limit maintenance
- Run tests on a mix of emulators and real devices regularly
- Avoid testing implementation details and hardcoded data
Example use cases
- Write Jest unit tests for a React Native cart service and run in CI
- Create Detox E2E tests for login and checkout flows on iOS and Android
- Use XCTest and Espresso snippets to reproduce platform-specific UI bugs
- Integrate Appium with a device farm for cross-device compatibility checks
- Identify and isolate flaky tests, then add retries or improve selectors
FAQ
Aim for high unit test coverage (60–80%) and keep integration/E2E targeted; overall coverage targets depend on risk but maintain >80% on critical logic where feasible.
How do I reduce flaky UI tests?
Use stable selectors, avoid timing-based assertions, reset app state between tests, mock network where appropriate, and run on real devices to reproduce flakiness.