corlabs.dev · Developer Tools
5 items
Generate, rank, and maintain reliable XPath and CSS locators — AI self-healing, versioned, and shared across your team. COR Lens — maintain your locators through their full lifecycle, not just generate them once Most locator tools stop at generation: you inspect an element, get a selector, and you're on your own the moment the page changes. COR Lens covers what happens next. Inspect any element and get a ranked, reliable locator with a health score — then let it self-heal when the page changes, keep a versioned history of what changed and why, and share the fix with your whole team instead of losing it on one person's machine. What it does: • Ranked locators, not guesses. Every candidate — from stable Test IDs down to CSS and XPath — is scored on uniqueness and stability, so the most robust one comes first. • Self-healing that keeps working. When the page changes, COR Lens adapts the locator instead of letting your test go red. • Versioned and shared. A locator fixed once is fixed for the whole team, with history you can trace — not a one-off patch that lives only in your local run. • Handles native widgets and dynamic UI: date pickers, dropdowns, and menus that vanish on click are held open so you can capture inside them, and native inputs give you the exact code to set a value. • Optional natural-language search: describe an element in plain English and COR Lens finds it and writes the locator. • Record captures your whole workflow, not one element at a time. Walk through a real user journey — click, type, select, hover — and COR Lens records a locator for every step in order, so you leave with a full test scenario instead of assembling one by hand. • Copy without leaving the page. Right-click any element for its best locator, the raw selector, its XPath, or its CSS selector — no need to open DevTools first. COR Lens writes correct, working code for the popular automation frameworks, so whichever one your team uses, the syntax is right the first time. Built for QA engineers, SDETs, and developers writing end-to-end UI tests — anyone tired of flaky locators and rewriting the same selector every sprint. Category: Developer Tools
Aug 21, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.