microsoft / microsoft/react-native-windows
Add Thread Affinity Tests
Open
Nobody has claimed this yet.
Area: Native Modules
Area: Tests
enhancement
Workstream: Component Parity
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
We should add tests to make sure that we crash when thread-affined objects we own are accessed on the wrong thread. E.g. that we do not allow UI-thread objects on the NM thread, and that we do allow JS thread affined APIs on the NM thread.
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
No file or existing test entry point is named. Search for the thread-affinity checks and tests using the issue’s UI, NM, and JS thread terms; done means tests cover crashing for an owned UI-thread object on the NM thread and allowing JS-thread-affined APIs on the NM thread.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100