-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
Package: nextjsIssues related to the Sentry Nextjs SDKIssues related to the Sentry Nextjs SDKType: ImprovementType: Tests
Description
Problem Statement
NextJS integration tests are definitely our most flaky set of tests, and they are also much harder to debug since they don't use jest under the hood.
https://sentry.io/organizations/sentry/dashboard/24245/?project=5899451&statsPeriod=3d
We should update these tests!
Solution Brainstorm
These probably involves a couple of changes:
- Instead of using puppeteer, use playwright like our browser and remix integration tests. This is as puppeteer causes some problems for fresh installations, which was ran into by @drguthals here. -> test(nextjs): Migrate Next SDK's client side tests to Playwright. #6718
- Use jest for the node integration tests, like our remix integration tests do. This should make things much more consistent -> test(nextjs): Refactor server-side integration tests #6909
- Figure out how to make session tests less flaky
- Rewrite main test script in TS rather than bash
- Run most recent node version integration test on Windows
Metadata
Metadata
Assignees
Labels
Package: nextjsIssues related to the Sentry Nextjs SDKIssues related to the Sentry Nextjs SDKType: ImprovementType: Tests