microsoft / microsoft/react-native-windows
Detect IntegrationTest Shutdown Crashes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Should we add shutting down the intergratoin test app to see if there might be issues during shutdown?
Originally posted by @dannyvv in https://github.com/microsoft/react-native-windows/pull/6087#discussion_r494416703
We already collect crash dumps for these. We could maybe just add a step to shutdown, then fail CI if we see any crash dumps were recorded.
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 tracing how the integration test app is shut down and where existing crash dumps are collected. Determine how CI can detect a dump after shutdown and fail the job when one is present; done means shutdown runs and crash-dump detection is enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100