What problem does it solve?
It removes the repetitive, error-prone work of hand-coding Page Object Model (POM) view classes for the Decentraland Explorer UI by giving you a consistent way to define locators and typed interactions for every screen, panel, dialog, and overlay.
Core Features & Use Cases
- Creates and updates POM views for Explorer UI test automation, including full screens, standalone panels, dialogs, and overlays.
- Builds panel tab/section views using the
BaseSection pattern so tests can switch and interact with sub-areas cleanly.
- Defines typed element fields (
Locatable, Readable, Clickable, Writable) and adds helper methods with Allure steps for higher-level actions.
- Supports nested sub-views for repeated UI structures (like grid items or slot collections) using
BaseClickableView and parent-passed locators.
- Chooses stable locator strategies (prefers
By.ID, then By.NAME, then By.PATH) and can request locator discovery from the running instrumented Explorer.
Quick Start
Trigger the view-writer skill and tell it which Explorer UI area you need (e.g., panel + tab) plus any known element names/IDs you already have.