microsoft / microsoft/react-native-windows

Add Functional Tests for Touchable Highlight

Open
#12,465 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Fabric 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

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

### Tasks
- [ ] TouchableHighlight should update style upon fast refresh.
- [ ] TouchableHighlight should update underlayColor upon fast refresh.
- [ ] TouchableHighlight should update activeOpacity upon fast refresh.
- [x] TouchableHighlight should fire action upon press.
- [x] TouchableHighlight should fire action upon onPressIn.
- [x] TouchableHighlight should fire action upon onPressOut.
- [ ] TouchableHighlight should fire action upon onLongPress.
- [ ] TouchableHighlight should register press in clicked within hitSlop range.
- [x] TouchableHighlight should not be interactable when disabled. 

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the E2E test app (Fabric) and review how TouchableHighlight scenarios are organized. Add coverage for the unchecked fast-refresh, onLongPress, and hitSlop cases, then run the relevant E2E tests. Done means each listed scenario passes while the already checked behaviors remain covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native
Domain
mobile-dev, testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.