-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Feature Req: chrome context menu testing #5001
Comments
Like to see it. |
1 similar comment
Like to see it. |
I am waiting for an update on this issue. I need this too. |
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
@ImBIOS |
There is currently no plans to support testing extension actions as the backend support is missing. You can still test extensions if you load them as a standalone page or using the --load-extension argument for the Chromium binary. You should be able to connect to the background extension pages using Puppeteer. |
I am developing a Chrome extension that makes extensive use of the context menu. Currently I am unable to test that with Puppeteer.
And Puppeteer is supposed to be an all-round solution for chrome testing, right?
So.. can we add this (and more generally - extension testing overall) to the roadmap?
The text was updated successfully, but these errors were encountered: