mobile-testing
/mobile-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports. Focus on whether the rule is continuously verified, not just documented.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports. Focus on whether the rule is continuously verified, not just documented.
Original author description
Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports. Focus on whether the rule is continuously verified, not just documented.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
SKILL.md preview
--- name: mobile-testing description: "Use when reviewing CI coverage, automated checks, or test strategy related to Test on real mobile devices and viewports. Focus on whether the rule is continuously verified, not just documented." metadata: category: testing priority: high difficulty: intermediate estimatedTime: "20" source: frontendchecklist.io url: https://frontendchecklist.io/rules/testing/mobile-testing --- # Test on real mobile devices and viewports More than 55% of global web traffic comes from mobile devices. Mobile browsers have different rendering engines, different font rendering, limited memory, real touch events that differ from mouse events, and system UI (notch, home indicator, keyboard) that intrudes on your layout. Issues like sticky hover states, touch target sizes, and keyboard layout shifts only appear on real devices. ## Quick Reference - Desktop DevTools device emulation catches layout issues but not real touch behavior - Test on at least one Android (Chrome) and one iOS (Safari) real device - Test common viewport breakpoints: 375px (iPhone SE), 390px (iPhone 14), 768px (iPad) - Use BrowserStack or similar services for testing on devices you don't own ## Check Does this project have any mobile-specific test configurations? Check for Playwright device emulation, mobile viewport tests, or notes about mobile testing. ## Fix Add Playwright tests using mobile device presets to cover key user flows on mobile viewports. ## Explain Explain the difference between DevTools emulation and real device testing, common mobile-specific issues to test for, and how to use Playwright's device emulation. ## Code Review Review tests, CI workflows, and enforcement points related to Test on real mobile devices and viewports. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions. --- For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`. Rule page: https://frontendchecklist.io/rules/testing/mobile-testing
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · thedaviddias/front-end-checklist | 100 | MIT |
| proffesor-for-testing/agentic-qe | 100 | MIT |
| mhmdelgazzar/agentex | 100 | MIT |
| irahardianto/awesome-agv | 100 | MIT |
| arozumenko/sdlc-skills | 91 | MIT |
| j4flmao/agent-skills | 90 | MIT |
Database snapshot: 13.11.2026 · package version 0ce7e8259162 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented. - 100mock-best-practices
Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Focus on whether the rule is continuously verified, not just documented. - 100testing-mobile-apps
Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality". - 100testing-mobile-apps
Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality". - 90testing-mobile-devices
Use when testing mobile devices is required during mobile product work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent. - 100create-test-plan
Create a test plan when the user asks to plan testing, define test cases, create a QA strategy, write a test plan, or prepare for testing a feature