microsoft / microsoft/react-native-windows
Add UIA Verification of Successful New App Launch to Init Tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
We have runtime tests against several flavors in prebuilt projects, but do not do runtime validation that a newly created template app works successfully. We instead currently just test publish, build, and deploy.
https://github.com/facebook/react-native/pull/31652 adds a distinct testID to the new app screen so that we can validate via UIA that a new application has launched successfully. Our UIA testing tooling is now decoupled from E2ETest, which should make it pretty easy to extend existing init tests to add the runtime validation.
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 reading the existing init tests and the UIA testing tooling mentioned in the issue. Extend the init test coverage to launch a newly created template app and verify its successful launch through UIA, using the new app screen testID described in the linked React Native pull request; done means runtime validation runs alongside publish, build, and deploy checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- desktop, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100