microsoft / microsoft/react-native-windows
Add E2E Snapshot Tests for Pressable
Open
Nobody has claimed this yet.
Area: Fabric
Area: Pressable
Area: Tests
enhancement
good first issue
New Architecture
Workstream: Test Coverage
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Add E2E Snapshot tests for the Pressable component. We should take snapshots of the composition and accessibility tree for each example.
STATUS TYPES
| Status | Description |
|---|---|
| Not Implemented | Prop is not implemented for given architecture. |
| Not Completed | No test or sample exists for the prop. |
| Sample Completed | Sample exists for the prop, but sample is not run in a Jest Snapshot Test. |
| Completed | Sample and Snapshot test exists for the prop. |
PROPS STATUS FOR PRESSABLE
| Test Description | Status (Paper) | Status (Fabric) | Notes |
|---|---|---|---|
| Default |
|
|
|
| AccessibilityHint |
|
|
|
| AccessibilityLabel |
|
|
|
| AccessibilityActions |
|
|
|
| AccessibilityRole |
|
|
|
| AccessibilityValue |
|
|
|
| AccessibilityPosInSet |
|
|
|
| AccessibilitySetSize |
|
|
|
| AccessibilityLiveRegion |
|
|
|
| ImportantforAccessibility – no-hide-descendants |
|
|
|
| testID |
|
|
|
| Style – backgroundColor |
|
|
|
| Style – borderBottomColor | Not Implemented |
|
|
| Style – borderBottomEndRadius |
|
|
|
| Style –borderBottomLeftRadius |
|
|
|
| Style – borderBottomRightRadius |
|
|
|
| Style – borderBottomStartRadius |
|
|
|
| Style – borderBottomWidth |
|
|
|
| Style – borderColor |
|
|
|
| Style – borderEndColor | Not Implemented |
|
|
| Style – borderLeftColor | Not Implemented |
|
|
| Style – borderLeftWidth |
|
|
|
| Style – borderRadius |
|
|
|
| Style – borderRightColor | Not Implemented |
|
|
| Style – borderStartColor | Not Implemented |
|
|
| Style – borderStyle | Not Implemented |
|
|
| Style – borderTopColor | Not Implemented |
|
|
| Style – borderTopEndRadius |
|
|
|
| Style – borderTopLeftRadius |
|
|
|
| Style – borderTopRightRadius |
|
|
|
| Style – borderTopStartRadius |
|
|
|
| Style – borderTopWidth |
|
|
|
| Style – borderWidth |
|
|
|
| Style – elevation | Not Implemented |
|
|
| Style – opacity |
|
|
|
| Style – height |
|
|
|
| Style – width |
|
|
|
| Style – backfaceVisibility |
|
|
|
| Accessible |
|
|
|
| Focusable |
|
|
|
| HitSlop |
|
|
|
| NativeID |
|
|
|
| NextFocus* | Not Implemented |
|
|
| onAccessibilityAction |
|
|
|
| onAccessibilityTab |
|
|
|
| onAccessibilityEscape |
|
|
|
| onLayout |
|
|
|
| onMoveShoudlSetResponder |
|
|
|
| onMoveShouldSetResponderCapture |
|
|
|
| onResponderGrant |
|
|
|
| onResponderMove |
|
|
|
| onResponserReject |
|
|
|
| onResponderRelease |
|
|
|
| onResponderTerminate |
|
|
|
| onResponderTerminationRequest |
|
|
|
| onStartShouldSetResponder |
|
|
|
| onStartShouldSetResponderCatpure |
|
|
|
| pointerEvents |
|
|
|
| removeClippedSubviews |
|
|
|
| needsOffscreenAlphaCompositioning |
|
|
|
| toolTip |
|
|
|
| children |
|
|
|
| unstable_pressDelay |
|
|
|
| delayLongPress |
|
|
|
| onLongPress |
|
|
|
| onPress |
|
|
|
| onPressIn |
|
|
|
| onPressOut |
|
|
|
| pressRetentionOffset |
|
|
|
| testOnly_pressed |
|
|
|
| Disabled |
|
|
|
| {pressed} |
|
|
|
| onHoverIn |
|
|
|
| onHoverOut |
|
|
|
| onFocus |
|
|
|
| onBlur |
|
|
|
| onKeyUp |
|
|
|
| onKeyDown |
|
|
|
| onKeyDownCapture |
|
|
|
| keyDownEvents |
|
|
|
| aria-label |
|
|
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Pressable examples in RNTester and review the existing E2E snapshot-test pattern used by the project. Cover the examples and props marked Not Completed in the status table, capturing both composition and accessibility-tree snapshots. Done means the relevant Paper and Fabric entries have snapshot coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- desktop, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100