microsoft / microsoft/react-native-windows
Separate IntegrationTests Native Project from IntegrationTests JS target
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 a project in vnext called IntegrationTests. This name is the same as RN's JS for IntegrationTests, which is one of our JS build targets. This means the same folder has source and targets, making it awkward to clean the JS or discover what bits are unique source.
The name of the JS should ideally match upstream RN, like other JS targets. We should consider moving the native project. This could potentially happen with upcoming changes to the desktop test runner.
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 inspecting the vnext IntegrationTests project and the IntegrationTests JS build target, then review the desktop test runner changes mentioned in the issue. Determine how the native project can be separated from the JS target. Done means they have distinct names or locations, and the JS source and target contents are easier to clean and distinguish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100