Skip to content

test(e2e): Decode gzipped envelopes in E2E tests #8926

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 1, 2023

Conversation

lforst
Copy link
Contributor

@lforst lforst commented Aug 31, 2023

This PR makes our E2E test proxy decode gzipped envelopes.

This change is motivated by Next.js compressing requests in dev mode 🤷‍♂️. It also lets us re-enable a few tests I thought were just broken.

@@ -41,3 +41,5 @@ next-env.d.ts
.sentryclirc

.vscode

test-results
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If tests fail locally traces are dumped here

@@ -19,7 +19,7 @@
"@types/node": "18.11.17",
"@types/react": "18.0.26",
"@types/react-dom": "18.0.9",
"next": "13.2.4",
"next": "13.4.19",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests are actually failing in this version because of this. Only noticed because of our canary tests.

@lforst lforst marked this pull request as ready for review August 31, 2023 21:30
@lforst lforst requested a review from AbhiPrasad August 31, 2023 21:30
Copy link
Member

@Lms24 Lms24 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Side note: At some point we should really think about a dev-utils package. We have a similar decompression logic in the browser-integration-tests package due to replay envelopes being compressed.

@lforst lforst merged commit 13b4729 into develop Sep 1, 2023
@lforst lforst deleted the lforst-decode-gzip-envelopes branch September 1, 2023 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants