microsoft / microsoft/react-native-windows
Add E2E Snapshot Tests for TouchableHighlight
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Add E2E snapshot tests for the TouchbleHighlight components. Snapshots should dump the contents of the Composition Visual Tree and the Accessibility Tree.
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 TOUCHABLEHIGHLIGHT
| Test Description | Status (Paper) | Status (Fabric) | Notes |
|---|---|---|---|
| Default - Text Child |
|
|
|
| Default - Image Child |
|
|
|
| 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 |
|
|
|
| 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 – overflow |
|
|
|
| Style – backfaceVisibility |
|
|
|
| Accessible |
|
|
|
| Focusable |
|
|
|
| HitSlop |
|
|
|
| NativeID |
|
|
|
| NextFocus* |
|
|
|
| onAccessibilityAction |
|
|
|
| onAccessibilityTab |
|
|
|
| onAccessibilityEscape |
|
|
|
| onLayout |
|
|
|
| onMoveShoudlSetResponder |
|
|
|
| onMoveShouldSetResponderCapture |
|
|
|
| onResponderGrant |
|
|
|
| onResponderMove |
|
|
|
| onResponserReject |
|
|
|
| onResponderRelease |
|
|
|
| onResponderTerminate |
|
|
|
| onResponderTerminationRequest |
|
|
|
| onStartShouldSetResponder |
|
|
|
| onStartShouldSetResponderCatpure |
|
|
|
| pointerEvents |
|
|
|
| removeClippedSubviews |
|
|
|
| needsOffscreenAlphaCompositioning |
|
|
|
| toolTip |
|
|
|
| activeOpacity |
|
|
|
| onHideUnderlay |
|
|
|
| onShowUnderlay |
|
|
|
| underlayColor |
|
|
|
| testOnly_pressed |
|
|
|
| onPress |
|
|
|
| onPressIn |
|
|
|
| onLongPress |
|
|
|
| delayPressIn |
|
|
|
| delayPressOut |
|
|
|
| delayLongPress |
|
|
|
| disabled |
|
|
|
| onFocus |
|
|
|
| onBlur |
|
|
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
The issue names TouchableHighlight, its Paper and Fabric prop-status table, and the Composition Visual Tree and Accessibility Tree snapshots as the scope. Start by locating the existing E2E snapshot-test entry point and the RNTester TouchableHighlight sample. Done means the requested component coverage produces snapshots for both trees and the relevant status entries are completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- accessibility, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100