microsoft / microsoft/react-native-windows
Add Tests for Flyout and Popup Launch
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Summary
We recently had a regression in the behavior of the Flyout component, where the component fired a RedBox error upon attempt to launch the Flyout. This was found during the manual validation of gallery for the v71 release.
Currently, we do not have automated testing to check that Popups and Flyout can successfully launch. These should be added to our test set.
Motivation
Prevent behavior regressions.
Basic Example
No response
Open Questions
No response
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 by locating the existing automated test set for the Flyout and Popup components and review how launch behavior is validated. Add coverage showing that both components launch successfully without the reported RedBox error, then run the relevant test suite to confirm the regression is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100