DevQAExpert Solution Pvt. Ltd.

Menu

Free Chrome extension by DevQAExpert

FindMyLocator: Find Locators, Record Tests and Write Test Cases from Chrome

Click any element for its Playwright, XPath and CSS locators, record a flow as Playwright, Cypress or Selenium code, and let QAEverest write test cases from the page you are on. It also checks links and load times, fills forms with test data and captures screenshots for bug reports.

Add to Chrome – It’s Free

Version 1.13.0 for Google Chrome. Locators, recording and code export need no account.

6
Tabs in One Extension
3
Test Frameworks for Code
5
Programming Languages

What Is FindMyLocator?

FindMyLocator is a product conceived and built by DevQAExpert Solution Pvt. Ltd. It finds a unique locator for any element in a web page’s DOM in a single click, and it has grown into a toolkit for the rest of a tester’s day.

  • Built by testers, for testersOur own testing team built it to end the daily hunt for locators that are unique and stay unique.
  • Free on the Chrome Web StoreLocators, recording, code export, network checks, test data and screenshots need no account.
  • Locators for every frameworkPlaywright, XPath and CSS, with code in TypeScript, JavaScript, Python, Java and C#.
  • In the popup or the side panelOpen it from the toolbar, or keep it in Chrome’s side panel next to the page you are testing.
  • Private by designNo tracking built in; nothing leaves the browser until you ask.
  • Connected to QAEverestHand a recording to QAEverest, or let it write test cases from the page with your QAEverest API key.
FindMyLocator logo

What’s New in FindMyLocator

Playwright locators, a locator tester, a page object builder and AI test cases, alongside the tools testers already use every day.

Playwright Locators

Locators by role, label, placeholder or test id for the element you click, kept only when they find that element alone.

Test a Locator

Paste CSS, XPath or a Playwright locator and see whether it finds nothing, one element or several, outlined on the page.

Page Object Builder

Collect up to 100 picked elements into one page object class for Playwright, Selenium or Cypress.

AI Test Cases

QAEverest writes test cases from the page you are on, a user story or your recording, in Gherkin or step by step.

Generated ID Warning

When an id or class looks generated, such as mui-17, you are warned that it can change on the next page load or release.

Shadow DOM Picking

Elements inside open shadow DOM are picked directly, with paths for Playwright, Selenium and Cypress.

Test Next to Copy

Every locator row now has a Test button beside Copy, so you can check a locator on the page before using it.

Stable Recordings

Each recorded step keeps a Playwright locator by role, label or test id where one exists, and the exported code uses it.

Everything a Tester Reaches For, in One Extension

Six tabs, in the toolbar popup or in Chrome’s side panel. Jump to one:

Locator tab

Playwright, XPath and CSS Locators in One Click

  • Playwright locatorsBy role, label, placeholder or test id, kept only when they find this element alone, in JS / TS, Python, Java or C#.
  • Unique XPath and CSSThe shortest unique XPath and CSS, a Text Locator, and an Iframe Locator for elements inside frames, plus a suggested variable name.
  • Relative XPathWhen an element has nothing unique of its own, the XPath is built from a unique parent, sibling or ancestor.
  • Specific attributeName an attribute such as data-test-id and the XPath and CSS use it first. Disabled elements work with right-click › Find My Locator.
FindMyLocator side panel showing the Playwright, CSS, XPath and text locators for a Place order button
FindMyLocator warning that the id mui-17 looks generated and may change, with Playwright locators suggested instead

Locator tab

Know Which Locators Will Break

  • Generated-ID warningIds and classes that a framework generates, such as mui-17, are flagged, because they can change on the next page load or release.
  • A better choice offeredThe warning points you to the Playwright locators above it, which keep working when ids, classes and layout change.
  • Shadow DOMElements inside open shadow DOM are picked directly, with paths for Playwright, Selenium and Cypress.
  • On the page or in the side panelShow locators in a window on the page, or in the side panel, where the last element picked stays ready to copy.

Locator tab

Test Any Locator Before It Goes into a Test

  • Reads every formatCSS, XPath and Playwright locators written in JS / TS, Python, Java or C#, including getByRole, getByLabel, getByText and getByTestId.
  • A clear answerIt tells you whether the locator finds nothing, exactly one element, or several, which would fail Playwright’s strict mode.
  • See every matchMatches are outlined on the page, with ‹ Prev and Next › to step through them, including inside iframes and shadow DOM.
Test a locator in FindMyLocator: a Playwright locator matches 7 fields, outlined on the page, flagged as not unique
FindMyLocator Page Object builder showing a Playwright TypeScript CheckoutPage class with three elements

Locator tab

Build a Page Object from the Elements You Pick

  • Add as you goAdd to Page Object collects up to 100 elements, from one page or several, with readable names such as placeOrderButton.
  • Your frameworkCopy or download the class for Playwright, Selenium or Cypress, in TypeScript, JavaScript, Python, Java or C#.
  • Best locator firstEach element uses its Playwright locator where one exists, so the class starts out stable.

Recording tab

Record a Flow, Then Export It as Code

  • Plain-English stepsPress Record and use the site as you normally would; the recording follows you into new tabs, iframes and open shadow roots.
  • Everyday actionsClicks, double-clicks, typing, dropdowns, checkboxes, radio buttons, file choices and the Enter and Escape keys, plus visibility checks you add with a click.
  • Secrets stay outPassword, OTP, card and API key fields are never recorded; exported code reads them from environment variables.
  • Export or hand overExport as Playwright, Cypress or Selenium code, or as Chrome Recorder JSON. Or press Open in QAEverest and the recording becomes a UI test case.
FindMyLocator Recording tab with seven recorded steps, Open in QAEverest, and Playwright TypeScript export
FindMyLocator Test cases tab showing the page text it read, with Type and Format options before generating

Test cases tab

QAEverest Writes Test Cases from the Page You Are On

  • Three starting pointsThis page (its headings, form fields, buttons and links, never what is typed into them), a user story in your words, or the steps from the Recording tab.
  • You choose the outputFunctional, System, Integration, Security or Performance, as Gherkin (BDD) or step by step, each with preconditions, steps and expected results.
  • Take them anywhereCopy them, or download a Gherkin .feature file, a CSV or JSON.
  • You see what is sentRead and edit the text first; nothing is sent until you press Generate. It uses your QAEverest API key and credits.

Network tab

Check Links, Load Time, Headers and Requests

  • LinksCheck every link on the page and see what is broken, redirected or OK, with each link marked on the page and a CSV to download.
  • Load timeFirst byte, DOM ready, first paint and largest paint, with an optional timer on the toolbar icon.
  • HeadersSet or remove request and response headers, on every site or only the ones you list.
  • RequestsLog one tab’s page loads and API calls, send a new request with any method, and copy it as cURL.
FindMyLocator link check: one broken link, one redirect and two working links, each marked on the page
FindMyLocator filling a checkout form with made-up Indian test data: name, phone, address, city and PIN code

Test data tab

Fill Forms with Realistic Test Data

  • Data that fits the marketMade-up names, phone numbers and postcodes from India, the United States or the United Kingdom.
  • Boundary valuesFill with valid values, the longest or highest allowed, the shortest or lowest allowed, or invalid values.
  • Bulk dataGenerate up to 1,000 rows across 24 field types as CSV or JSON.
  • Safe by defaultEmails use reserved example domains, card numbers are published test numbers, and Clear site gives you a clean slate in one click.

Report tab

Screenshots for Bug Reports

  • Capture what mattersThe visible area, the full page (scrolled and stitched), an area you select, or a single element.
  • Mark it upAdd arrows, boxes, text and blur, plus the address bar and the page details: browser, window size, capture time and tester.
  • Save it your wayPNG, JPEG, WebP or PDF, or copy the image straight into the ticket.
  • Check the textUnderline spelling and grammar mistakes on the page with Chrome’s own proofreader, where Chrome offers it.
FindMyLocator Report tab with Visible area, Full page, Select an area and An element screenshot options

Your Pages Stay in Your Browser

FindMyLocator has no tracking built in. Nothing from your pages leaves the browser until you ask it to check links, send a request, write test cases or open a recording in QAEverest.

Secrets Never Recorded

Password, OTP, CVV, card number and API key fields are recorded empty, and secret-looking parts of an address are hidden.

Recordings Live in Memory

A recording is kept for the browser session only and is gone when Chrome closes, unless you export it.

You See What Is Sent

The Test cases tab sends only the text in its box, which you can read and edit first, and only when you press Generate.

Your Key Stays Here

Your QAEverest API key is kept in this browser and goes only to QAEverest. Forget the key removes it.

How to Use FindMyLocator

From install to your first locator takes about a minute.

  1. Add to Chrome

    Add FindMyLocator from the Chrome Web Store and pin it to the toolbar.

  2. Reload open tabs

    Pages that were already open need a reload before the extension can work on them.

  3. Switch it on

    Open the popup or the side panel and switch the Locator tab ON.

  4. Pick an element

    Click any element on the page, then Test or Copy its locators.

  5. Record a flow

    Record what you do, then export it as code or open it in QAEverest.

  6. Write test cases

    Add your QAEverest API key to have test cases written from the page.

Watch the installation video

Frameworks, Languages & Integrations

Export code for

Playwright
TypeScriptJavaScriptPythonJavaC#
Cypress
JavaScriptTypeScript
Selenium
JavaPythonC#JavaScript
Chrome Recorder
JSON

Recordings export to all four. Page objects export to Playwright, Cypress and Selenium.

Locators

Playwright locatorsXPathCSS selectorsText locatorIframe locatorShadow DOM paths

Works with

Chrome popupChrome side panelQAEverest

Ready to Find Your Next Locator in One Click?

Add to Chrome

Need a team to build and run your test automation? Talk to DevQAExpert