Mobile app testing with unit tests, UI automation, performance testing. Use for test infrastructure, E2E tests, testing standards, or encountering test framework setup, device farms, flaky tests, platform-specific test errors.
89
86%
Does it follow best practices?
Impact
93%
1.09xAverage score across 3 eval scenarios
Passed
No known issues
React Native test suite structure
Jest for unit tests
100%
100%
Detox for E2E
0%
100%
reloadReactNative in beforeEach
0%
100%
by.id element selectors
0%
100%
Mocked external dependencies
100%
100%
Success and failure paths
100%
100%
No hardcoded test data
50%
25%
Independent tests
100%
100%
Unit test count ratio
100%
100%
Business logic tested first
100%
100%
Error case not skipped
100%
100%
No implementation detail tests
50%
50%
Android Espresso UI testing patterns
Espresso onView pattern
100%
100%
perform() for actions
100%
100%
check(matches()) for assertions
100%
100%
Success path covered
100%
100%
Failure path covered
100%
100%
Critical user flow automated
100%
100%
Independent test isolation
100%
100%
No hardcoded test data
100%
100%
No implementation detail assertions
100%
100%
Error case not skipped
100%
100%
R.id references used
100%
100%
iOS XCTest and test coverage strategy
XCUIApplication usage
100%
100%
Accessibility identifier selectors
100%
100%
XCTAssert for verification
100%
100%
Unit tests present
100%
100%
Unit tests outnumber UI tests
100%
100%
Coverage target documented
0%
0%
Success path tested
100%
100%
Failure path tested
100%
100%
Error case not skipped in unit tests
100%
100%
Real device note
100%
100%
Mocked dependencies in unit tests
100%
100%
No skipped error tests
83%
50%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.