robotframework / robotframework/SeleniumLibrary
Review Selenium capabilities versus existing SeleniumLibrary functionality
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
As part of the v6.2.0 milestone and beyond which is starting to add Selenium 4 capabilities I was just curious as to how many Selenium Python methods are used within the SeleniumLibrary and maybe what functionality we might be missing. I was thinking that rough comparison of methods and then the usage within the SeleniumLibrary code might show this difference of available versus implemented.
Thinking this would consist of two tasks
- Review Selenium Python methods versus what exist within SeleniumLibrary code
- Review Selenium Changelog since v4.0.0
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
Compare the Selenium Python methods with functionality currently present in SeleniumLibrary, then review the Selenium changelog from v4.0.0 onward. Complete both checklist items by recording the differences between available and implemented functionality; the issue names no files or tests to start from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100