Skip to content
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

MV3: Metrics / Sentry Test Cases #16692

Open
2 tasks
hilvmason opened this issue Nov 25, 2022 · 2 comments
Open
2 tasks

MV3: Metrics / Sentry Test Cases #16692

hilvmason opened this issue Nov 25, 2022 · 2 comments

Comments

@hilvmason
Copy link
Contributor

hilvmason commented Nov 25, 2022

  • Ensure pending segment events are not lost after service worker re-start
  • Ensure Sentry continues to work after service worker re-start
@danjm danjm changed the title Metrics / Sentry Test Cases MV3: Metrics / Sentry Test Cases Feb 24, 2023
@danjm
Copy link
Contributor

danjm commented Apr 25, 2023

@gauthierpetetin
Copy link
Contributor

gauthierpetetin commented Nov 28, 2023

This ticket may no longer be required as if all goes well, we won't have to re-start service worker.
Google said service workers will not have to be restarted but this needs to be confirmed.
We'll keep this ticket open until we have more info about service worker persistence.
In case there are edge cases, where service workers get disconnected, we'll have to refine this ticket more, and test Extension behaviour when we kill the service worker manually.

We'll have more info once our E2E tests work with MV3: #21496

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants