-
Notifications
You must be signed in to change notification settings - Fork 1
Selenium
The Selenium GitHub page is a key spot for people working on automating web tasks or testing websites. Made by lots of contributors, this free project gives tools to help users control web browsers automatically, which is perfect for testing how websites work in different browsers or on different devices. It's great for people who make websites, test them, or ensure they work right, offering support in many coding languages like Java, Python, and C#. The page has lots of guides, tips, and examples, making it easy for new folks to get started and super helpful for experts. I've also used it a bunch for my own projects to do tasks automatically and check my websites.
- Its README page is well written and welcoming for newcomers. It is easy to start using the library using the installation and usage guides there.
- Wiki page is very well built. It is easy to find your way in the wiki. Side menu is well categorized.
- There are many external links in the wiki so you can reach the external sources easily from one list.
- I love using Selenium :D
- Although there are links to the external websites, documentation is not directly on the Wiki. Wiki is organized mainly for the contributors, not the final users of the library. This might be a good distinction but I personally wish they were together.
- Issue labels are not very easy to understand for an outsider. There are no label descriptions and they are not used effectively. Some labels like "bug" are not labels but written into the issue title. This also might be practical but not really the good practice for GitHub.
The Selenium GitHub page is a great place for anyone interested in making websites work better through testing and automation. It's easy for beginners to get started and has lots of helpful info. I really like using Selenium for my projects. But, I think they could make their guides and labels clearer for everyone to understand better. Overall, Selenium is super useful and a big help for web developers and testers.
prepared by Dağhan Erdönmez
🏠Home
- Third Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Use Case Diagram
- Class Diagrams
- Scenarios
- User Scenario
- User Manual
- System Manual
- Third Customer Milestone Report
- Second Customer Milestone Report
- First Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Scenarios
- Use Case Diagram
- Class Diagrams
- Software Quality Plan
- Milestone1 Presentation Scenarios
- Post Creation Page
- User Scenario
- Meeting Notes 10 - Dec 10
- Meeting Notes 9 - Dec 3
- Meeting Notes 8 - Nov 17
- Meeting Notes 7 - Nov 12
- Meeting Notes 6 - Nov 5
- Optional Meeting Notes 1 ‐ Oct 21
- Meeting Notes 5 - Oct 15
- Meeting Notes 4 - Oct 8
- Meeting Notes 3 - Oct 3
- Meeting Notes 2 - Oct 1
- Meeting Notes 1 - Sep 24
- Deniz Ulaş Poyraz
- Eren Donmez
- Ersel Çanakçılı
- Oğuz Kağnıcı
- Onur Çerli
- Yekta Ercul
- Ali Alperen Sönmez
- Huseyin Turker Erdem
- Mehmet Tuluyhan Sozen
352 Material
- Final Milestone Report
- Milestone 2 Report
- RAM
- Use Case Diagram
- Sequence Diagrams
- Class Diagrams
- Requirements
- Elicitation Questions
- Mockups
- Scenarios
- Milestone 1 Report
- Our Favourite Repositories
- Linked Data and SPARQL
- Web Application Development
- API Development and Utilization
- Wikidata and Wikidata API
- Mobile Application Development
- Android Studio
- Git
- Meeting Notes 10 ‐ May 10th
- Meeting Notes 9 ‐ Apr 25th
- Meeting Notes 8 ‐ Apr 21st
- Meeting Notes 7 ‐ Apr 12th
- Meeting Notes 6 ‐ Mar 14th
- Meeting Notes 5 ‐ Mar 11th
- Meeting Notes 4 - Mar 7th
- Meeting Notes 3 - Mar 3rd
- Meeting Notes 2 - Feb 22nd
- Meeting Notes 1 - Feb 18th