microsoft / microsoft/react-native-windows
Re-enable AppVerifer for E2E tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
As part of https://github.com/microsoft/react-native-windows/pull/6318, AppVerifier was turned off to address test instability.
The theory is that this put too much pressure on the under-powered VMs we're currently using from the MSFT hosted agent pool.
Once we get the CI loop moved over to better hardware we should try re-enabling this. See https://github.com/microsoft/react-native-windows/issues/6226
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
Read PR 6318 and issue 6226 first to understand why AppVerifier was disabled and what hardware change is required. Then inspect the E2E test CI configuration and hosted-agent setup. Done means AppVerifier is re-enabled after the CI loop moves to better hardware and the tests remain stable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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