AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

react-native-tv-best-practices

Reviews React Native TV apps for focus/D-pad navigation, 10-foot UI layout, TV playback/DRM integration, low-memory TV performance, and TV accessibility. Use when building, debugging, or reviewing react-native-tvos, Expo TV, Amazon Vega/Kepler, or React Native web TV targets where the issue depends on remote input, TV focus, TV packaging, TV hardware, or TV playback constraints.

Original source
callstackincubator
License
MIT
Pinned revision
59e9d17446a248b21d86f078fcd0bd2d36db1ca4

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read callstackincubator--react-native-tv-best-practices at revision 59e9d17446a248b21d86f078fcd0bd2d36db1ca4, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 28

references/test-strategy.md


title: Testing Strategy for React Native TV Apps impact: MEDIUM tags: testing, integration-tests, rntl, focus, remote-input, tv

Testing Strategy for React Native TV Apps

TV testing should prove the remote-controlled paths that break differently from mobile: focus order, Back/Menu behavior, player controls, low-memory carousels, and platform packaging.

Quick Reference

  • Use integration tests for JS-owned focus state, player-control state, and remote event handlers
  • Use E2E tests for native focus engine behavior, app launch, routing, playback startup, and Back/Menu behavior
  • For agent-run accessibility smoke, load the agent-device skill and read agent-device help workflow, then inspect labels, roles, states, and focused elements from the accessibility tree
  • Use real hardware for overscan, remote latency, memory pressure, video decode, DRM, and display/color checks
  • Keep emulators/simulators for fast route, focus, and smoke coverage; do not treat them as final device validation
  • Reuse the same user flows for performance baselines where possible

JS Integration Tests

Prefer a saved or generated app state that includes rows, entitlement state, player state, and modal state:

const snapshot = require('my-state.json');
const { Wrapper } = loadStateFromSnapshot(snapshot);
render(<Wrapper><VideoPlayer /></Wrapper>);
  • Mock native player/focus modules when JS tests cannot load them
  • Mock timers for auto-hide controls, debounce, and "are you still watching" flows
  • Avoid mocking app state in tests that are meant to prove focus restoration or navigation paths

See test-javascript.md for the local tvRemote helper pattern.

CI Scope

  • PR checks: static checks, unit tests, integration tests, and changed-platform build checks
  • Nightly/release checks: E2E on representative TV devices, playback startup, agent-device accessibility-tree smoke, memory-sensitive carousel flows
  • Device matrix: at least one Apple TV target, one Android TV/Fire TV target, and any required Vega/Tizen/webOS target

Related Skills