'mobile-testing' 검색 결과

Design analytics-driven browser test matrices and execute cross-browser tests. Covers BrowserStack/Sauce Labs configuration, Playwright browser channels, common cross-browser CSS/JS divergences, a known-issues documentation log, and progressive enhancement validation. Use when: "cross-browser," "browser matrix," "BrowserStack," "Safari issues," "browser compatibility," "Edge," "works in Chrome but not Safari." Not for: pixel-level baseline strategy and threshold tuning — use visual-testing; device-farm testing of native/hybrid apps — use mobile-testing. Related: visual-testing, playwright-automation, ci-cd-integration, mobile-testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review mobile test coverage across real devices and simulated screen sizes. Find gaps in automated checks and CI, the workflow that runs project checks, and add Playwright tests for key mobile user flows.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing mobile test coverage in CI
• Adding Playwright tests for mobile user flows
• Planning Android and iOS real-device checks

Create and edit Agent QA tests, test suites, and hooks, then validate their structure and tool-generated IDs before running them. Use MCP, an agent tool connection, or the CLI within a configured workspace.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create and validate a checkout test for staging
• Update an existing test suite
• Check YAML definitions and IDs

Create, edit, validate, and run Agent QA tests, suites, and hooks through MCP or CLI while preserving canonical IDs and schema contracts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test native, React Native, hybrid, and Flutter mobile apps with Appium 3.x, Detox, Maestro, and Patrol. Covers device farm setup (BrowserStack, Sauce Labs), gesture simulation, deep link and cold-start testing, push notifications, biometric (Face ID) auth, offline/poor-network simulation, and iOS/Android permission dialog handling. Use when: "mobile test," "Appium," "Detox," "Maestro," "Patrol," "Flutter test," "iOS test," "Android test," "device farm," "deep link," "biometric," "Face ID," "permission dialog," "React Native test." Not for: device/browser matrix strategy in the abstract — use cross-browser-testing; app startup/memory/battery profiling depth — use performance-testing; mobile screenshot diffing — use visual-testing. Related: ci-cd-integration, cross-browser-testing, performance-testing, test-data-management, test-reliability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Appium is an open-source framework that automates native, hybrid and mobile-web apps on iOS and Android through the WebDriver protocol. Use when the user wants to set up Appium 3, write mobile UI tests in JavaScript (WebdriverIO) or Python, pick capabilities, run gestures, or fix "appium", "XCUITest", "UiAutomator2", "mobile automation" problems. For React Native-only testing, see detox.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Maestro mobile E2E testing - YAML flows, selectors, flow control, environment variables, JavaScript expressions, device interactions, Maestro Studio, Maestro Cloud CI, tags, test suites

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detox E2E gray-box testing for React Native - matchers, actions, expectations, waitFor, device API, synchronization, mocking, artifacts, CI integration

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for any Ionic Vue + Capacitor mobile work: Vue architecture, Composition API, TypeScript, state, env config, shared conventions. Required for every implementation task alongside mobile-testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for all verification: unit, component, E2E, native, and release checks. Required alongside mobile-core for every implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Android/iOS automated testing: device management, app install, performance profiling, log analysis, screenshot comparison, Maestro E2E orchestration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.