getsentry / getsentry/sentry-javascript
[Flaky CI]: E2E nuxt-3-top-level-import Test - tests/errors.client.test.ts › client-side errors › page is still interactive after client error
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 1.8k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 515
Description
### Flakiness Type
Other / Unknown
### Name of Job
E2E nuxt-3-top-level-import Test
### Name of Test
[chromium] › tests/errors.client.test.ts:61:3 › client-side errors › page is still interactive after client error
### Link to Test Run
https://github.com/getsentry/sentry-javascript/actions/runs/33634993937/job/100265160882
---
_This issue was automatically created._
Contributor guide
Research direction
Start with the E2E nuxt-3-top-level-import job and the linked test run, then inspect tests/errors.client.test.ts at line 61. Reproduce the client-side error test and determine why the page-interactivity assertion flakes. Done means the test reliably passes across repeated CI runs without masking the assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- ci-cd, frontend, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100