https://github.com/dgp1130/webdriver-devtools-extension

Attempts to use WebDriver to test a Chrome extension in a DevTools panel.
https://github.com/dgp1130/webdriver-devtools-extension

Last synced: 13 days ago
JSON representation

Attempts to use WebDriver to test a Chrome extension in a DevTools panel.

• Host: GitHub
• URL: https://github.com/dgp1130/webdriver-devtools-extension
• Owner: dgp1130
• Created: 2020-09-29T00:49:45.000Z (about 4 years ago)
• Default Branch: main
• Last Pushed: 2020-09-29T00:50:38.000Z (about 4 years ago)
• Last Synced: 2024-10-06T02:01:43.790Z (about 1 month ago)
• Language: Java
• Size: 5.01 MB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# WebDriver DevTools Extension

This attempts to use WebDriver to access a Chrome extension loaded in the

DevTools panel. This is necessary because DevTools panels have special APIs to

interact with the underlying page, such as accessing the network requests made.

These APIs cannot be easily simulated on a plain HTML page.

## Results

I tried hacking WebDriver to use the new `Driver#getDevTools()` method in 4.0,

but this doesn't appear to do what I want it to. Instead, it seems to refer to

"Chrome DevTools Protocol (CDP)". I was able to open DevTools but failed to

actually interact with it in any way.

## Alternatives

If you want to run an end-to-end test on a Chrome DevTools panel, I think your

best option right now would be to use

[Puppeteer](https://github.com/puppeteer/puppeteer) and hack a reference to the

extension frame. See

[this issue](https://github.com/puppeteer/puppeteer/issues/4247) for more info.