robotframework / robotframework/SeleniumLibrary
Discuss/Consider support for Chrome DevTools Protocol
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
There has been added support for Chrome DevTools Protocol to Selenium 4. This effort is in part a "stop gap" or temporary way of incorporating what will eventually be the WebDriver Bidi or Bi-Directional Protocol.
[This issue is an initial place holder. I see it would be helpful to provide a thorough background information which I will add here by 26 May, 2023]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Selenium 4 Chrome DevTools Protocol support and the intended relationship to WebDriver BiDi. Use the issue's promised background information to define the scope, affected interfaces, and acceptance criteria; the current placeholder does not identify files, tests, or a completed outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100