shadow-automation-selenium
Shadow DOM automation tool
A Selenium plugin for automating shadow DOM elements and custom HTML tags in web applications built with Polymer.
This project focuses on automation of multi-level shadow root dom using java selenium. You can embed this plugin in your java selenium project.
111 stars
14 watching
33 forks
Language: Java
last commit: over 2 years agoLinked from 1 awesome list
automationcustom-elementscustom-tagpolymerseleniumselenium-javaselenium-webdrivershadow-domtesting-tools
Related projects:
| Repository | Description | Stars |
|---|---|---|
| A tool to easily select elements in web page shadows even when you don't know the path through nested shadow roots. | 249 | |
| Enables encapsulation of styles and markup in a Shadow DOM root within Ember components. | 30 | |
| A tool for automating browser interactions using container orchestration and automated management of web browsers | 225 | |
| An in-depth guide to Shadow DOM, including its purpose, terminology, browser support, and implementation details. | 232 | |
| A PowerShell module for automating browser interaction using the Selenium API | 467 | |
| A library that injects React components into 3rd-party sites using ShadowDOM | 49 | |
| Automation of Tor Browser using Selenium WebDriver | 558 | |
| Automates recording and generation of Selenium WebDriver page tests and keyword-driven frameworks | 39 | |
| A library that enables style encapsulation in React applications using Shadow DOM. | 1,321 | |
| A Vue directive for adding colorful shadows to images using the cosha library | 81 | |
| An Eclipse plugin that extends SeleniumPlus functionality | 4 | |
| Enables Shadow DOM support in web page testing tools | 14 | |
| Simplifies the management of Selenium Grid Nodes and stabilizes test environments after builds. | 536 | |
| A Python-based testing framework for web UI automation with an intuitive API and built-in features to simplify test writing | 697 | |
| A library that provides a clean API to access an object's variables and methods through introspection and metaprogramming | 28 |