microsoft / microsoft/react-native-windows
Add E2E automated test for auto-linking
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Currently, we are manually verifying that auto-linking a native module into an app works correctly. Recent upgrades have broken this workflow after publish, which has been a pain point for us.
This task is tracking creating a sample native module, and a test that runs in the CI loop to exercise auto-linking. Perhaps the test should create an app and auto-link the sample module... whatever most effectively covers the scenario our customers use.
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 reviewing the CI loop and the existing app and native-module test setup, then determine how to create a sample native module and exercise auto-linking after publish. The work is complete when an end-to-end test creates or uses an app, auto-links the sample module, and runs reliably in CI to cover the customer workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100