microsoft / microsoft/react-native-gallery
Automate Testing/Validation of Gallery Component Pages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 257
- Forks
- 57
- Avg merge
- 18h 19m
- Merged PRs (30d)
- 10
Description
Currently when we need to validate a release, we update gallery to the latest RNW version and then manually walk through the pages to confirm that all of the components are working and rendering correctly. Instead, it would be great to automate this process by using some kind of UI testing platform - such as Jest - to iterate through the pages and test the controls. We should then add this testing to our pipelines, so we can catch regressions as they come.
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 no files, tests, or pipeline entry points; start by locating the gallery component pages, their existing validation paths, and the repository's CI configuration. Define the UI coverage and testing platform before implementation, with done meaning component controls are automatically validated during the release pipeline and regressions are reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- ci-cd, mobile, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100