Microsoft/react-native-windows

Add Functional Tests for Pressable Component

Open

#12,461 opened on Nov 29, 2023

View on GitHub
 (1 comment) (1 reaction) (1 assignee)C# (544 forks)batch import
Area: FabricArea: PressableArea: TestsNew ArchitectureWorkstream: Test Coverageenhancementgood first issue

Repository metrics

Stars
 (6,114 stars)
PR merge metrics
 (Avg merge 4d 14h) (45 merged PRs in 30d)

Description

Test cases should be added to the E2E test app (Fabric) to validate the following functionality scenarios.

### Tasks
- [ ] Pressable should update border styling upon fast refresh.
- [ ] Pressable should update children upon fast refresh.
- [ ] Pressable should update disabled styling upon fast refresh.
- [x] Pressable should update applicable styling upon hover.
- [x] Pressable should update applicable styling upon press.
- [x] Pressable should perform action upon press.
- [x] Pressable should be able to track number of clicks.
- [x] Pressable should perform action upon onPressIn.
- [x] Pressable should perform action upon onPressOut.
- [ ] Pressable should perform action upon onLongPress.
- [x] Pressable should not perform action upon press when disabled.
- [ ] Pressable behavior should change upon delayLongPress adjustment.
- [ ] Pressable should register onPress action when hit within hitSlop range.

Contributor guide

Research direction
Focus on the unchecked tasks: Pressable should update border styling upon fast refresh, update children upon fast refresh, update disabled styling upon fast refresh, perform action upon onLongPress, behavior change upon delayLongPress adjustment, and register onPress action when hit within hitSlop range. Familiarize yourself with the E2E test setup for Fabric in react native windows and how to add test cases for Pressable component.
Tech stack
javascripttypescriptreactreact native
Domain
desktoptesting
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNode.jsReact Native Windows development setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65