MetaMask / MetaMask/metamask-extension
Add E2E test to errors.spec.js to cover the case of sending Error messages after MetaMetrics is toggled
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
In #20132 we made it such that sentry defaults to not tracking sessions when MetaMetrics is disabled, and we added a test case to ensure that the session packet is not sent. We also have a test for ensuring sentry data is sent when MetaMetrics is enabled. We need test cases for when the state of MetaMetrics changes during app run time in order to prevent accidental breakages.
Contributor guide
Research direction
Start in errors.spec.js by reading the existing E2E cases for MetaMetrics-enabled and disabled Sentry data. Add coverage for changing the MetaMetrics state during app runtime, verifying Error messages follow the expected tracking behavior after the toggle. Run the relevant E2E tests and confirm the new cases pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100