Skip to main content
Free Chrome extensionWorks with QAEverest

Find the locator. Record the test. Check the page.

FindMyLocator is a free Chrome extension from the QAEverest team. Click an 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 marks up screenshots for bug reports.

Add to Chrome, it's free

Version 1.13.0. Locators, recording and exports need no account; test cases use your QAEverest API key.

One popup
6
Tabs for everyday testing
Locator, Recording, Network, Test data, Report and Test cases, in the toolbar popup or in Chrome's side panel.
Code
3
Test frameworks to write for
Recordings and page objects for Playwright, Cypress or Selenium, in TypeScript, JavaScript, Python, Java or C#.
QAEverest
1
Click to hand a recording over
Open in QAEverest takes the recording to the By Recording page, where it becomes a UI test case.
Six tabs

What a tester reaches for, in one popup

Open it from the toolbar, or keep it in Chrome's side panel next to the page you are testing.

Locator tabNew: Playwright locators

Click an element, get Playwright, XPath and CSS locators

Switch the Locator tab on and click anything on the page. FindMyLocator shows Playwright's own locators for it, and the shortest unique XPath and CSS, each ready to test or copy.

  • Playwright locators by role, label, placeholder or test id, kept only when they find this element alone, in JS / TS, Python, Java or C#.
  • Unique XPath and CSS, a Without Index version, a Text Locator and an Iframe Locator, plus a suggested variable name.
  • A warning when an id or class looks generated, so you know which locators may break on the next release.
  • Elements inside open shadow DOM are picked directly, with paths for Playwright, Selenium and Cypress.
  • Name a Specific attribute such as data-test-id and the XPath and CSS use it first. Disabled elements work with right-click > Find My Locator.
  • Show locators On the page, or In the side panel, where the last element picked stays ready to copy.
Locator tabNew

Test any locator, then build a Page Object

Paste a locator and see what it finds on the page before it goes into a test. Then collect the elements you need into one page object class.

  • Test a locator reads CSS, XPath and Playwright locators written in JS / TS, Python, Java or C#: getByRole, getByLabel, getByText, getByTestId and more.
  • It says whether the locator finds nothing, exactly one element, or several, which would fail Playwright's strict mode.
  • Matches are outlined on the page, with ‹ Prev and Next › to step through them, including inside iframes, and inside open shadow DOM for Playwright locators.
  • In the popup and side panel, every Playwright, CSS and XPath row has a Test button next to Copy.
  • Add to Page Object collects up to 100 elements, from one page or several, with readable names such as placeOrderButton.
  • Copy or download the class for Playwright, Selenium or Cypress, in TypeScript, JavaScript, Python, Java or C#.
Recording tab

Record a flow, then export it or send it to QAEverest

Press Record and use the site as you normally would. Every step is written in plain English, and the recording follows you into new tabs, iframes and open shadow roots.

  • Clicks, double-clicks, typing, dropdowns, checkboxes, radio buttons, file choices and the Enter and Escape keys.
  • Add checks: click an element while recording to check that it is visible.
  • Each step keeps a Playwright locator by role, label or test id where one exists, and the export uses it.
  • Password, OTP, card and API key fields are never recorded. Exported code reads them from environment variables.
  • Export as Playwright, Cypress or Selenium code, or as Chrome Recorder JSON. Or press Open in QAEverest and the recording becomes a UI test case.
Network tab

Check links, load time, headers and requests

Four quick checks on the page in front of you, each on its own sub-tab.

  • Links: check every link on the page, see what is broken, redirected or OK, with each link marked on the page and a CSV to download.
  • Load time: first byte, DOM ready, first paint and largest paint, a timer on the toolbar icon that turns red above your limit, and a CSV of the last 100 pages.
  • Headers: set or remove request and response headers, on every site or only the ones you list.
  • Requests: log one tab's page loads and API calls, send a New request (GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS), and Copy as cURL.
Test data tab

Fill forms and generate test data

Made-up data from India, the United States or the United Kingdom, so names, phone numbers and postcodes look right for the market you are testing.

  • Fill form with Valid values, Longest / highest allowed, Shortest / lowest allowed or Invalid values.
  • Each field is read from its type, label, placeholder, length limits and pattern, and a confirm email or confirm password field gets a matching value.
  • Generate up to 1,000 rows across 24 field types, from names and emails to test card numbers, as CSV or JSON.
  • Safe values: emails at example.com, published test card numbers, and fields that look like a government ID left empty.
  • Clear site: cookies, storage, service workers and cache for the site, then a fresh reload.
Report tab

Screenshots for bug reports, and a spelling check

Capture what you see, mark it up and drop it into the ticket. Then check the page's English text for spelling and grammar.

  • Visible area, Full page (scrolled and stitched), Select an area, or An element.
  • Add arrows, boxes, text and blur, plus the address bar and the page details: browser, window size, capture time and who tested it.
  • Save as PNG, JPEG, WebP or PDF, or copy the image.
  • Check text underlines mistakes on the page, red for spelling and blue for grammar. QAEverest checks it with your API key and credits, or, where Chrome offers it, Chrome's own proofreader does it on this computer.
  • Download every finding as a CSV.
Test cases tabNew

QAEverest writes test cases from the page you are on

Connect your QAEverest API key once. Then choose what to write from, read the text that will be sent, change it if you like, and press Generate.

  • This page: the page's headings, form fields, buttons, tabs and links, never what is typed into the fields.
  • A story: a user story, a feature or a requirement, in your words. The recording: the steps from the Recording tab.
  • Type: Functional, System, Integration, Security or Performance. Format: Gherkin (BDD) or Step by step.
  • Each test case comes back with its preconditions, steps and expected results.
  • Copy them, or download a Gherkin .feature file, a CSV or JSON.
  • Uses your QAEverest credits. Nothing is sent until you press Generate.
After you press Stop

One recording, two ways forward

Hand the recording to QAEverest to review and run as a test case, or export it as code for the framework your team already uses.

Open in QAEverest

A UI test case your team reviews

Press Open in QAEverest and the recording lands on the By Recording page, ready to review.

  • The steps arrive in plain English, grouped by page, with a warning on any step worth a second look.
  • Add the expected result and save it as a UI test case in a new or existing suite, Traditional or BDD.
  • Passwords are never recorded: the step reads Enter "<password>" and you add the value as test data.
  • Run it with QAEverest's UI automation, its self-healing locators and run reports.
  • Importing a recording uses no credits.
Export

A test file for your own framework

Pick a Format and a Language, then Download or Copy. Each step keeps a plain-English comment above its code.

PlaywrightTypeScriptJavaScriptPythonJavaC#
CypressJavaScriptTypeScript
SeleniumJavaPythonC#JavaScript
JSONChrome Recorder

Each export is one test file with its runner set up: @playwright/test, pytest, JUnit 5, NUnit, mocha or Cypress. A visibility check becomes toBeVisible(), should('be.visible') or an explicit wait.

Want written test cases instead? Pick The recording in the Test cases tab and QAEverest writes them from your steps.

Privacy

Your pages stay in your browser

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

Secrets are never recorded

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

Recordings live in memory

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

A one-time hand-off

Open in QAEverest passes the recording straight to the QAEverest tab, which turns it into steps and keeps nothing until you save. The link works once and expires after 30 minutes.

You see what is sent

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

Your API key stays here

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

Screenshots stay local

The editor and the PDF export run on your computer, and only your five newest captures are kept.

Get started

From install to your first locator, in four steps

01

Add to Chrome

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

02

Reload your tabs

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

03

Pick a tab

Open the popup or the side panel and choose Locator, Recording, Network, Test data, Report or Test cases.

04

Connect QAEverest

Add your QAEverest API key to write test cases or check text, and sign in to QAEverest to open a recording there. Locators, recording, exports and test data need no account.

Add FindMyLocator to Chrome. It's free.

Get Playwright locators in one click, record your next regression flow, and let QAEverest turn it into test cases your team can run.

Add to Chrome