wsbaser:generate-selectors

Generate robust web selectors by reading component markup and applying XCSS priority rules to derive a named list of stable element selectors. This process targets available aria attributes first to ensure selectors remain valid as interfaces evolve.

CSS selectors break when markup changes because they rely on unstable structural attributes. Validate current selectors against the DOM and migrate them to higher-priority types like aria attributes to improve selector stability across UI updates.

The best way to validate existing selectors is to check their syntax, priority, and uniqueness against the current DOM. This ensures your XCSS selectors accurately target elements without conflicts in the web component markup.

Migrate selectors to use aria attributes by analyzing the updated web component markup and upgrading existing selectors to higher-priority types. This migration aligns selectors with accessibility priorities to prevent test breakage during interface evolution.

Yes, you need to provide the markup source path and specify the target elements to generate or validate XCSS selectors. The tool reads this markup to apply priority rules and output a named list of accurate selectors.

Upgrade web element selectors when the interface evolves but the core components remain. Migrating existing selectors to higher-priority XCSS types like aria attributes maintains test coverage while improving selector robustness against DOM changes.