Providing a reference implementation?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
The specs are great. What I think is missing, is a reference implementation that:
- Keeps things very simple, and actual code minimal
- It's an actual implementation of JUST the standard, exactly as documented
- It's well documented
I happen to have written exactly that: https://github.com/mercmobily/best-webdriver . Documentation is here too: https://mercmobily.github.io/best-webdriver/index.html
I was wondering if you (as in the W3c) would be interested in making this project as part of the w3c umbrella, or under the webdriver project/repo. I would be happy to turn over copyright for the source code, or give the W3C unlimited rights, or whatever is required. I would only ask to stay as the main maintainer, since I know the codebase well.
I think a clean, crisp, strict-to-the-specs implementation was needed -- and that's why I wrote it. I now think that more people would benefit from this work if it became W3C's. So, here I am.
Please let me know if you are interested.
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 proposed best-webdriver repository and its linked documentation. Compare its scope with the WebDriver standard and repository goals; done would be a maintainer decision on whether and how to bring it under the W3C/WebDriver project, with ownership and maintainer expectations resolved.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100