microsoft / microsoft/react-native-windows
Include and run upstream rntester-e2e tests in our repo
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 already have our own version of the upstream rn-tester package in the form of @react-native/tester with our overrides and our own @react-native-windows/tester with additional Windows examples/pages, and finally our own e2e-test-app for running XAML snapshot tests with wdio/WinAppDriver.
However, upstream RN also has an rn-tester-e2e package which contains a suite of jest tests against the rn-tester app using wido targeting ios and android platforms. We should bring and adapt the upstream rn-tester-e2e package into our repo so we can also run those E2E jest tests but targeting windows instead.
Motivation
We already know how to run wido tests against our e2e-test-app but right now it's only for XAML snapshot testing. If there is a suite of wido tests upstream, already written, it seems like we could greatly expand our test coverage for pretty cheap, while also getting the benefits of checking our platform's behavior against the "expectation" from RN.
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
Compare the upstream rn-tester-e2e package with this repository's @react-native/tester, @react-native-windows/tester, and e2e-test-app. Start by tracing how the existing wdio/WinAppDriver tests are run, then determine how the upstream Jest suite can target Windows. Done means the adapted suite runs against the Windows tester app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- operating-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100