microsoft / microsoft/react-native-windows
Run Tests Against Direct Debugging Configuration
Open
Nobody has claimed this yet.
Area: Debug Infrastructure
Area: Tests
enhancement
Partner: Microsoft
Workstream: Test Coverage
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
See #8885 for an example of why this is important.
We currently do full app tests against web debugging, Chakra Release, and Hermes Release, but do not test the direct debugger. This would also potentially help to detect issues with Hermes debug builds.
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 comparing how full app tests are configured for web debugging, Chakra Release, and Hermes Release. Add equivalent coverage for the direct debugger and assess whether Hermes debug builds are included; done means the full app tests run against the direct debugging configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100