Getting started
Smart Locator Inspector helps turn a webpage element into evaluated locator options and reusable automation code. Start on the page you are authorized to test, then open the extension from your browser toolbar.
- Open the target page. Navigate to the state containing the element you want to automate.
- Start inspection. Open Smart Locator Inspector and activate its element inspection control.
- Select an element. Choose the button, field, link, menu, table cell, or other UI element on the page.
- Review and test. Compare the generated recommendations and use Live Selector Test to confirm the selected strategy matches the intended element.
- Copy or build. Copy a locator, create a reusable method, or use the recommendation in generated automation code.
Inspect an element and review recommendations
After you select an element, review its displayed HTML, attributes, and DOM context. Smart Locator Inspector may recommend Role, Label, Placeholder, Text, CSS, or an appropriate XPath strategy. The recommendation score helps you compare options; it does not replace testing the selector in the real page state.
Enable Production Mode when you want to focus on higher-rated strategies. A locator should describe the element clearly, remain unique in the relevant page state, and avoid coupling to layout details that change frequently.
Generate, test, and copy locators
- Choose the framework syntax you need: Playwright, Selenium, or Cypress.
- Run the Live Selector Test and verify both the match count and the highlighted element.
- Prefer user-facing roles, names, and labels when they uniquely express the element’s purpose.
- Copy the chosen locator or download generated files where the relevant feature provides that option.
Use Smart Method Builder
Smart Method Builder turns repeated navigation and interaction patterns into parameterized methods. Select the pattern that matches the UI—such as key-value content, menus and tabs, lists, tables, grids, dropdowns, nested menu navigation, or row actions—then review the parameters and generated method before using it in your project.
For actions such as Assign, Edit, Manage, Delete, or View, confirm that the generated row scope identifies the intended record and that the action locator is unique within that row.
Record interactions and use runtime data
Start recording before performing the browser interactions you want to capture. When finished, review the recorded steps and generated Page Objects, test files, assertions, and reusable actions. Replace eligible literal input values with runtime test-data or environment-variable references when the value should be configurable.
Troubleshooting
The element is unavailable
Confirm the page is fully loaded, the element is visible, and you have entered the correct frame or open component state. Reopen the extension after navigating or refreshing.
The locator matches multiple elements
Choose a more specific role and accessible name, add stable context, or scope the locator to a meaningful container. Avoid positional selectors unless order is an intentional part of the UI.
The locator stops working
Check whether labels, generated IDs, classes, DOM nesting, or component states changed. Reinspect the element and prefer a strategy tied to user-visible meaning.
Generated code needs changes
Confirm the selected framework, language conventions, imports, async handling, and test runner configuration. Adapt the output to your project’s fixtures and Page Object structure.
A recorded step is missing
Verify recording was active before the interaction. Repeat the action slowly after the target is visible and enabled, then review the recorded flow before export.
Saved work is not visible
Check that you are using the same browser profile and have not cleared extension data. Local workspace information does not automatically follow you to another profile or device.
Contact support
If the guidance above does not resolve the issue, email akshayjain599@gmail.com or contact the developer through the LinkedIn profile. Include the extension version, browser version, target framework, a concise description of what you expected, and reproduction steps. Do not send passwords, access tokens, private page content, or sensitive test data.