LWC ShadowPath Generator

Generates JS selector path for LWC Synthetic ShadowDOMs.

What is LWC ShadowPath Generator?

'LWC ShadowPath Generator' is a specialized Chrome extension designed to alleviate the complexities typically associated with generating selector paths within Lightning Web Component's Synthetic Shadow DOM. It mimics Chrome's in-built 'Copy JS Path' functionality, making it easier to replace obsolete Selenium selectors in your testing, thus resulting in more accurate and efficient Java test coding.

Download

Extension stats

By: Salesforce

View on Chrome Web Store

Users: 971 ▼ -25

Rating: 2.50 (6)

Version: 1.3 (Last updated: 2020-01-23)

Creation date: 2020-01-22

Risk impact: Low risk impact

Risk likelihood: Low risk likelihood

Manifest version: 2

Size: 29.80K

Email: ch*****@salesforce.com

URLs: Privacy policy

Ranking

# 30287 ▲ 425

Other rankings

#1018 in Developer Tools #38 in generator keyword 16 ▲ 1 #190 in panel keyword 16 ▼ 3

Other platforms

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Extension summary

Analyze keywords

Chrome Extension to generate Selector paths for elements encapsulated by our LWC components' Synthetic Shadow DOM.
Attempting to reproduce the functionality of Copy > Copy JS Path that Chrome provides for native Shadow DOM

To Use:

Inspect any element to open Element Inspector, and then open up the LWC ShadowRoot panel by clicking '>>' on the far right.
Select the element that the obsolete Selenium selector used to select.
Copy and paste from the panel's jspath field into the console to confirm that it is selecting the desired element (remove the extra surrounding double quotes after pasting).
Copy and paste from the panel's java field into existing java test code to replace the obsolete Selenium selector.

User reviews

This doesn't seem to be working in the currenct Chrome brower version - 92. Will this be resolved. Seem to be working fine in older Chrome versions ? Aprreciate any help on this