Select a live element and review what Studio found.
Windows desktop · Selenium authoring · Optional AI review
Browser automation built from evidence, not guesswork.
WebElemate Studio turns real browser work into automation your team can see, run, and own. Inspect a live page, compare locator suggestions, verify each candidate with JS Test, and run a draft step in the browser beside its generated code. Or press Record to capture supported interactions as editable steps with visible locators, waits, recovery, and browser context. Review the flow, replay it with actionable diagnostics, and export readable Selenium source. Optional AI can propose loops, conditions, or repairs for your approval—it never silently rewrites the flow and is never required.
Compare locator suggestions and select the one you trust.
Test one action or replay the complete reviewed flow.
Generate readable source for the language and framework your team uses.
Designed to work with your existing stack
ChromeEdgeFirefoxSelenium 4.x targetsC# · Java · Python codeFramework-specific assertions
Record → review → run → own
Record the journey once. Shape it into automation your team can own.
Recording is the fastest way to create a transparent first draft—not a black box. WebElemate turns supported browser activity into an ordered flow you can inspect, correct, replay, and convert into maintainable source.
RECORD
Use the browser naturally.
Choose Record, then type, select, check, click, navigate, use meaningful keys, or move through supported tabs, windows, and frames. WebElemate adds each captured action to the flow in observed order.
REVIEW
Turn the capture into an intentional test.
Stop recording and inspect every row. Insert manual steps, reorder or duplicate actions, select better locators, tune waits and recovery, map data, and keep browser context explicit.
RUN & GENERATE
Prove the flow, then generate the source.
Replay the same reviewed sequence in Chrome, Edge, or Firefox with preflight checks and actionable Results. Generate readable Selenium code for a supported language and framework profile without rebuilding the automation.
OPTIONAL AI
Add richer logic without giving up control.
Share only selected, redacted context with a provider you configure. Ask for a second look or a proposal such as a bounded loop or condition, review and edit it, then transfer only what you approve.
No black-box recording. No rewrite between capture, playback, and export.One visible flow connects what the tester did, what the browser will run, and what the development team can reuse.
Optional, user-controlled AI
Bring in AI for a second look. Keep the workflow yours.
Inspection, flow authoring, browser execution, diagnostics, and code export all work without AI. When it is useful, preview and share only selected, redacted context with a provider you configure for analysis or reviewable step-logic proposals—including loops and conditions. Review every proposal, then transfer only what you approve.
Provider selected by you · Context previewed before sending · No silent flow changes
AI review agentILLUSTRATIVE REVIEW
Proposal ready
Redacted contextProposal onlyYou approve transfer
Why WebElemate
Turn a real browser journey into clear, reusable automation.
WebElemate keeps the inspected element, chosen locator, action, run result, and generated code together. Anyone reviewing the flow can see what the test does, how it finds each element, and where a failure occurred.
Turn observation into a structured step
Inspect the rendered page, understand the element’s role and state, choose a compatible action, and carry the selected locator and alternatives into the flow.
Replace fragile selectors with explainable choices
Locator Intelligence creates and validates several candidates, then compares uniqueness, readability, and likely stability. Selectors built from generated classes, session values, or other unstable page details are clearly downgraded.
Bring manual and recorded work into one flow
Add a precise step by hand or record a browser journey at the selected insertion point. Both become editable rows in the ordered Automation grid.
Make browser context explicit
Navigation, opening or switching tabs and windows, and entering frames become visible steps. Studio keeps these context changes in the flow so they can be reviewed and replayed in the intended order.
Catch problems before the browser moves
Preflight checks the run range, required parameters, locators, waits, data columns, row availability, browser state, and context settings before execution.
Debug the step that actually failed
Run one draft action, step through the grid, execute a range, or repeat data-driven runs. Results identify the step, outcome, timing, evidence, and practical next checks.
Generate code that fits the destination team
Choose plain Selenium or a supported test-framework profile for C#, Java, or Python. Framework-specific assertions and dependencies are generated for the selected target.
Keep AI optional and reviewable
The deterministic product works without AI. When Copilot is configured, users choose the provider, the exact context to send, and whether to apply any proposed change.
Product capabilities
Everything needed to move from a live page to reviewed automation.
The main workflow moves through Inspect, Automation, Code, and Results. Recording, test data, preflight checks, browser and version guidance, workspace recovery, and optional AI review support that workflow when needed.
01
INSPECT
Understand the element before automating it.
See the element's purpose, visible text or value, page context, important attributes, accessibility information, and current state. Compatible actions and required inputs appear beside the element so the next step is clear.
- Live page selection
- Manual Find & select
- Action-aware parameter fields
- Single-step code and execution
02
LOCATORS
Keep alternatives, not just one selector.
Compare active and recommended candidates, use JS Test to query supported locators in the live page without triggering the action, and retain alternatives for later repair.
03
AUTOMATION
Edit the whole journey in one place.
Insert, record, reorder, duplicate, move, and run the visible sequence without rebuilding it elsewhere. Mark a row No run when playback should skip it while code generation, reusable handoff, and AI review continue to include it.
04
DATA & PREFLIGHT
Repeat runs with confidence.
Use CSV, JSON, XLSX, or XLSM data. Validate required columns, row counts, locators, parameters, and browser context before playback starts.
05
CODE
Export readable source for the stack you own.
Generate C#, Java, or Python with supported assertion frameworks. Review and edit the source, then preview the exact destination before saving.
06
RESULTS
Know what happened and what to check next.
See which run and step executed, how long it took, the outcome, returned values, and practical guidance for investigating a failure.
07
WORKSPACES
Resume authoring without rebuilding the flow.
Save the authoring choices needed to continue a flow later. Studio can also help recover interrupted unsaved work, while deliberate workspace copies remain the safest backup.
08
WAIT, SCROLL & RECOVERY
Make timing and failure behavior visible.
Build an ordered wait plan, optionally center and verify the target before interaction, and choose typed exception handling that either stops the flow or continues with an amber HANDLED result.
09
KEYBOARD
Model meaningful keys—not just text.
Add Enter, Tab, Shift+Tab, Escape, arrows, function keys, modifiers, or another supported shortcut to a selected element or to the browser's active element.
10
REUSABLE CODE
Hand developers a compact copy kit.
Create a reviewable reference for integrating the current flow into the destination project without changing the Automation grid.
11
AI COPILOT
Ask for review without surrendering control.
Choose the context to share, preview it before sending, review the response, and apply a proposal only when you decide it belongs in the flow.
One connected path
From first click to maintainable code.
A clear path for first-time users, with enough evidence and control for experienced automation engineers.
Open
Choose an installed Chrome, Edge, or Firefox browser and navigate to an authorized test environment.
Inspect
Select an element, review its semantics and locator candidates, then choose the action that matches the control.
Build or record
Add the step exactly where it belongs, or capture the rest of the journey into the same Automation grid.
Control timing and recovery
Arrange condition-based waits, enable scrolling when a target may be obscured, and define what each expected exception should do.
Validate and run
Set data, range, and repeat count. Preflight checks the visible flow before the browser begins, then Results separates passed, failed, and handled outcomes.
Review and export
Generate flow code or a reusable developer reference, optionally ask AI for a reviewed proposal, then safely save C#, Java, or Python for the destination project.
Value for the team
One workflow that the whole team can understand and use.
People are not limited to one role in WebElemate. Anyone can inspect, build, record, run, debug, review, or export a flow according to the work they need to complete.
The inspected element, locator choices, ordered steps, waits, data, Results, and generated code remain easy to review together.
Live locator validation, JS Test, preflight checks, and single-step execution catch common problems before a full run or code handoff.
Readable C#, Java, or Python code follows the selected framework’s structure, dependencies, setup, cleanup, and assertion style.
Teams choose browser settings, data, run range, export destination, update behavior, AI provider, shared context, and whether to apply proposed changes.
Guided product tutorial
Learn each workflow through exact controls, steps, outcomes, and first checks.
The guidance is intentionally text-first, using stable control names, ordered actions, expected results, and troubleshooting checks so it remains useful as the interface evolves.
Open the complete documentation tutorial →Open the first-party Automation Practice Lab →Confirm the browser context, element evidence, step order, policies, and Results before changing code.
Check readiness, locator, frame or tab context, interception, and page state before increasing a timeout.
Generated and AI-assisted source remains developer-owned code and must fit the destination repository.
FIRST RUN
Build and verify a useful flow in minutes
- Navigate to the test page.Enter an authorized HTTP or HTTPS address and choose Navigate. If the browser session ended, the button changes to Restart & navigate.
- Choose Inspect.Click the element you want in the automated browser. Studio loads its details, compatible actions, and locator evidence.
- Prepare the action.Choose the action, enter any required value, and select the locator you want the step to use.
- Test or add the step.Run step validates the draft immediately. Add step places it into the shared Automation flow; testing first is optional.
- Build the journey.Set Insert at, start recording, complete the remaining browser actions, and stop recording. Manual and recorded steps appear together.
- Run and review.Choose From, To, Runs, and any data settings. Run flow performs preflight, executes the range, and opens Results.
- Generate the destination source.Select a Framework profile, choose Code, review the output, and use Save to preview the file action before writing.
- Save the workspace.Use File > Save workspace as… to keep the authoring document for review and later work.
Expected resultThe selected tutorial link appears in Selected element, Locator Intelligence shows validated choices, Run step tests the click without adding a row, and Add step creates one reviewable Automation row.
Check first if the draft failsConfirm the active Browser Tab / Window, frame or shadow context, locator match, and operation type before increasing a timeout.
Question: does Run step add the row?No. Run step tests the Inspect draft. Add step is the deliberate authoring action.
FILE & WORKSPACE
Save the authoring state, not a live browser session
New workspace · Ctrl+NStarts a clean untitled authoring session after offering to save unsaved work.
Open workspace… · Ctrl+OOpens a saved WebElemate workspace so you can continue authoring.
Save workspace · Ctrl+SWrites the current workspace to its existing path.
Save workspace as… · Ctrl+Shift+SChooses a new file path. Use this for a portable copy or a new scenario.
Check for Studio updatesReports whether an approved update is available. Installing an update remains your choice.
Exit · Alt+F4Closes Studio after the unsaved-work decision.
Workspace name and dotThe name beside File is informational. A dot means the current workspace has unsaved changes.
RecoveryStudio can help recover interrupted authoring work, but regularly saving remains the safest practice.
Workspace contentsA workspace keeps the authoring choices needed to continue the flow. Reopen the target page before resuming browser work.
Check first after reopeningUse Navigate or Restart & navigate, then re-establish any required page state.
Question: is recovery a backup?No. Keep deliberate workspace copies and exported code in approved storage.
APPLICATION HEADER
Control the browser, generation target, and product help
Back / Forward / RefreshMoves browser history or reloads the page. The matching browser action is added to Automation.
Browser Tab / WindowLists the available automated pages and switches Inspect or recording to the one you choose.
Address boxAccepts a complete URL and suggests saved addresses while typing. Ordinary website addresses without a scheme are normalized to HTTPS.
Save URL / Manage URLsSaves, adds, updates, or removes per-user address suggestions without navigating or adding a step.
Open & navigate / Restart & navigateUses the current tab, or starts a fresh browser session when Studio is offline.
Maximize on runThe square toggle beside navigation is on for a new workspace. When checked, flow playback normally maximizes the browser without hiding its tabs, address bar, or Windows taskbar. It does not resize the browser immediately.
BrowserSelects an installed Chrome, Edge, or Firefox family. Studio does not install or uninstall the browser.
Browser statusShows starting, online, busy, or offline state.
Inspect / Stop inspectStarts or stops element selection across the automated tabs and windows.
Framework profileChooses the exported language and optional assertion framework. It does not change Studio playback.
Selenium APIChooses the Selenium version targeted by generated source.
Version guideShows compatibility information and practical next steps when a browser cannot start.
Implicit wait msSets the general element lookup wait for the flow.
Explicit wait msProvides a starting wait suggestion for new eligible rows. You can still adjust each row individually.
Help / F1Opens searchable, task-oriented guidance inside Studio.
AI Copilot / Disconnect AIOpens the optional Copilot window or ends the current connection.
Update availableAppears when a newer compatible release is available.
Tabs and windowsBrowser Tab / Window changes the active page. Tabs / Windows refreshes the list without adding a step. Use Browser action when a tab, window, navigation, history, refresh, close, or keyboard action belongs in the flow.
Expected resultThe selected browser opens the requested address, the status changes to ready, and deliberate browser actions appear as reviewable flow rows.
Check first when the header says offlineConfirm the selected browser is installed and use Restart & navigate for a new session.
Question: when does Maximize apply?It applies when flow playback starts. It does not immediately resize the browser while authoring.
INSPECT
Understand the target and create the right step
Inspect / Stop inspectChoose Inspect once, then click an element in any automated tab or window. Studio intercepts the selection click instead of sending it to the page.
Selected elementShows identity, classified type, role, accessible name, text or value, state, attributes, page context, and available options where relevant.
ShowFilters operations by category, including actions, state reads, assertions, waits, information, groups, and advanced behavior.
ActionLists only operations compatible with the selected element. A native select, checkbox, file input, text input, and button receive different choices.
Parameter fieldsAppear only when required—for example text, expected value, timeout, option text or value, index, file, or output variable.
CodeOpens a closable single-step source preview. It never replaces the full-flow code workspace.
Run stepExecutes the displayed draft against the live browser and opens Results.
Add stepAdds the current action, values, active locator, and retained alternatives at the selected insertion point. Blue is untested, green passed, and red failed.
Find & selectSearches by visible text or an entered CSS, XPath, ID, name, role, or test identifier, highlights the strongest visible match, and loads it into Inspect.
Copyable valuesDisplayed attributes and select-option values can be copied. Do not put real credentials in a workspace intended for sharing.
Expected resultAfter selecting a page element, Studio reports its type, role, visibility, enabled state, interaction target, and supported actions. Choosing an action reveals only the values that action needs.
Check first when Inspect cannot selectChoose the intended Browser Tab / Window, close blocking native dialogs, and verify the target is in an accessible frame or open shadow root.
Question: why are some values protected?Credentials and sensitive fields are deliberately unavailable for copying, diagnostics, and shared workspace evidence.
LOCATOR INTELLIGENCE
Compare candidates and keep the reasoning
WebElemate offers several ways to identify the selected element, checks them against the live page, and explains which choices are likely to be easier to maintain.
TypeIdentifies the locator strategy.
LocatorShows the value. Right-click to copy the value alone or with its type.
Score / GradeSummarizes ranking confidence; it is guidance, not a guarantee that a website will never change.
StatusReports live validation, match count, uniqueness, and relevant warnings.
JS TestChecks supported locator types against the current page without triggering the target action.
InsightExplains strengths, stability concerns, and validation findings in plain language.
Select a rowClick a candidate to make it active. Blue marks the active locator; green marks the strongest validated recommendation.
Sort a columnClick a column title to sort. Clicking a row selects it; row clicks do not change the sort order.
Copy allCopies every candidate displayed in Inspect.
Automation retentionWhen a target becomes a step, Studio keeps a concise set of useful alternatives while preserving your selected locator.
About JS TestJS Test checks a supported locator without performing the element's action or changing the page.
Strong choicesPrefer clear, stable page identifiers and meaningful accessibility information over temporary visual or session-specific details.
Expected resultStudio recommends a validated locator with an explanation, keeps the active choice clear, and lets you copy or retain useful alternatives.
Check first when the match count changesRe-inspect the live element, verify the correct tab or frame, then compare the retained alternatives.
Question: is the score a guarantee?No. It is guidance; websites can still change and locator choices should be reviewed.
AUTOMATION
Edit, arrange, and control the complete flow
CodeGenerates every Automation row, including rows marked No run, into the persistent Flow code workspace.
ReusableBuilds a separate read-only developer copy kit with shared helpers and one ordered Step block.
From / ToSelects an inclusive playback range. To = End continues through the final row.
Run / StopPerforms preflight and executes the selected range. While active, Stop requests cancellation between browser commands.
Insert atSets the exact step number for the next manual or recorded action.
InspectReturns to Inspect and starts selection when a browser is available.
Record / StopCaptures supported browser interactions at the selected insertion point.
Browser actionAdds Navigate, Open new tab/window, Switch or Close tab/window, Close browser, Back, Forward, Refresh, or a browser keyboard action. Navigate/Open accept an optional URL; blank remains blank.
DeleteEnters row-selection mode so several checked steps can be removed in one confirmed action.
Step ◀ / Step ▶Executes the highlighted runnable row and moves the debug cursor to the previous or next runnable row.
Undo / RedoEach click restores exactly one user action, with up to 100 flow-grid actions retained.
Move to… / Up / Down / dragMoves one row or a multi-row selection while preserving relative order.
Copy / DuplicateCopies a review-friendly description or inserts independent copies after the last selected row.
ClearRemoves the entire flow after confirmation and resets From to 1 and To to End.
Editable grid fields
No run skips a row during playback without removing it from the workspace. Each row keeps its waits, scrolling, recovery choice, data, locator choices, and other authoring details. The grid scrolls horizontally so every field remains reachable.
The grid is the visible execution planRow order and policy switches make the intended flow reviewable before playback or export.
Expected resultThe grid shows each action in execution order with the information needed to review and maintain it.
Check first when a row runs unexpectedlyConfirm From/To, No run, the selected row, and the global Wait and Scroll switches.
Question: does Clear remove code files?No. It clears the flow after confirmation; it does not delete exported files.
WAIT, SCROLL & RECOVERY
Make every timing and recovery decision reviewable
Explicit wait msSeeds the visible Suggested wait on new eligible steps. Once a row's plan is saved manually, later header changes do not overwrite it.
WaitOpens the ordered plan. Add, remove, reorder, and edit Sleep, readiness, DOM, visibility, clickability, hidden, text, attribute, property, value, or URL conditions.
Suggested waitsA new step may begin with one operation-aware suggestion, such as Clickable for an interaction or Present in DOM for a read. It is ordinary editable data.
Wait ON/OFF titleGlobally includes or omits saved wait plans in both Run and generated code without deleting their configuration.
Scroll to viewResolves the target, centers it, waits for stable geometry, and for pointer actions checks that a sticky header or overlay does not cover the hit point.
Scroll ON/OFF titleGlobally includes or omits checked row scrolling while preserving each row's setting.
ExceptionOpens an ordered list of typed catches for common Selenium and browser-context failures. Put the most specific catch first; Any must be last.
After catchContinue marks the row amber HANDLED and proceeds. Stop reports failure and ends the current flow execution.
Results messageAdds diagnostic text to Results and generated logs. It is never executed as code.
Finally reportAdds an optional always-run cleanup message after the operation or catch outcome.
Execution orderFor each element row, Studio performs enabled Wait items, enabled Scroll to view, the Operation, then matching exception handling. The same visible order is emitted in generated source.
Expected resultSaved waits run in their listed order, scrolling centers and verifies the target before interaction, and a matching Continue policy reports amber HANDLED while Stop ends the flow with clear evidence.
Check first when a click is interceptedLook for a cookie banner, modal, loading layer, or sticky header at the hit point; then use the readiness signal tied to that blocker.
Question: should Wait or Scroll run first?Wait runs first, Scroll to view second, then the operation. This keeps target resolution and readiness ahead of viewport positioning.
RECORDING & CONTEXT
Capture browser work without hiding the result
- Set Insert at.Choose where captured actions belong in the existing flow.
- Choose Record.The control changes to Stop. Supported typing, meaningful keys, selection, checking, clicking, navigation, and history events enter the grid in observed order.
- Move through tabs and windows normally.A blank tab opened with the browser's + button records Open new tab and stays selected; the internal New Tab page is ignored. A real address entered there records a separate Navigate step. Native tab selection or Browser Tab / Window records an indexed Switch step without forcing Studio back to another tab.
- Close the intended context.Closing one tab records one Close tab/window step and continues in the nearest remaining tab. Closing the browser records one Close browser step rather than several synthetic tab closes.
- Work inside frames when needed.Frame context is recorded for targets inside iframes. Studio returns to the top document only when the next step requires it.
- Choose Stop.The captured rows are already part of the shared flow and can be edited, moved, generated, or run like manual steps.
How replay finds the right tab or windowStudio waits until the recorded number of tabs or windows exists, then switches to the saved position—for example, context 0 for the original tab and context 1 for the next one opened. It does not search every tab by URL, reducing flicker and avoiding accidental navigation.
Check first when a switch is missingConfirm Browser Tab / Window changed to the selected context before performing the next action. Use its dropdown as the deterministic fallback.
Question: should a blank new tab add Navigate?No. Open new tab is recorded first; Navigate is added only after a real URL is entered or another user navigation occurs.
SEMANTIC KEYBOARD ACTIONS
Record or author the key that changes the page
Press key / shortcutFor a selected element, choose the action and enter Enter, Tab, Shift+Tab, Escape, Space, arrows, Home, End, PageUp, PageDown, Delete, F1–F12, or a Control/Alt/Shift shortcut.
Press browser key / shortcutFrom Browser action, send the key to the browser's currently active element when no saved locator should own it.
Plain typingUse Enter text or Append text for ordinary text. Use the keyboard action for navigation keys, semantic submission, function keys, and shortcuts.
Plus keyWrite Plus when the + key is part of a shortcut—for example Control+Plus—so it is not confused with the shortcut separator.
RecordingNormal typing stays one text row. A meaningful key such as Enter becomes its own action; navigation it triggers is not duplicated as an unrelated Navigate row.
Generated codeThe selected key or shortcut is preserved in generated C#, Java, and Python and in the reusable copy kit.
Check first when Enter does not submitConfirm the row is Press key/shortcut with value Enter, the correct target or active element has focus, and the destination page has a semantic submit handler.
Question: when should I use a browser key?Use it when the current active element should receive the shortcut and no saved element locator should own the action.
DATA & PREFLIGHT
Repeat a verified range with external test data
RunsRepeats the selected From/To range from 1 through 10,000.
Browser close On/OffControls whether the browser stays open after each run or closes before the next run starts.
Data fileSelects CSV, JSON, XLSX, or XLSM input. The button changes color when a file is selected; hover shows its path.
Clear data fileRemoves the file association without deleting the source file.
Use data fileEnables row substitution. When off, steps use the values shown in the grid.
Data variableNames reusable input or output state.
Data columnMaps an input to an external-data header.
What preflight checks
Before the browser moves, preflight validates the requested range, supported operations, required locators, locator types and values, parameters, waits, data file, row count, required columns, tab/window indexes, and settings required by the chosen browser. Blocking rows turn red and do not run partially.
Expected resultWith Use data file on, each requested record supplies its mapped columns for one run. With it off, the file remains associated but every step uses the hardcoded Value shown in the grid.
Check first when preflight blocks the runRead the exact row and field named in the message. Verify required data columns and available records before changing the browser flow.
Question: what happens when Use data file is off?The file remains associated, but playback deliberately uses the hardcoded values displayed in the grid.
RUN & RESULTS
Debug at the right level and keep the evidence
Run stepTests the current Inspect draft against the live browser.
Step ◀ / Step ▶Runs the selected grid row and advances the debug cursor without launching an unrelated new flow.
RunRuns the selected range for the requested iterations after preflight succeeds.
ResultsShows the run, step, duration, outcome, returned values, and practical next checks.
Run GuidanceGroups common problems—such as readiness, locator, page context, blocked clicks, assertions, uploads, scripts, or browser state—so you know where to start.
Privacy-aware evidenceFailure reports intentionally limit and redact page details. They do not collect passwords or full page contents.
ClearClears only the visible Results report. It does not remove flow rows, workspace history, code, or files.
Row colorsPassing rows become green, handled failures amber, and failed or invalid rows red; the current selection remains distinct.
Closed browser behaviorSingle-step debugging never silently restarts a closed browser. Use Restart & navigate so the active start page and session are explicit.
Check first after a FAILClassify it first: readiness, locator, frame/tab context, interception, stale element, assertion, script, upload, or browser session.
Question: is HANDLED successful?No. Amber HANDLED means the configured Continue policy absorbed a known failure and moved to the next step.
CODE & EXPORT
Generate source for the destination project—not a demo snippet
Framework profileChoose a supported C#, Java, or Python profile for the destination project.
Selenium APIChooses the source target and matching dependency guidance.
CodeGenerates the complete included Automation flow. The Code tab also keeps a separate preview for one Inspect action.
Line numbersCode surfaces display line numbers for easier review.
Find / Ctrl+FSearches the visible code.
Minimize / Restore Code / ResultsCollapses or restores the right workspace to give the Automation grid more room.
Undo / RedoMoves through recent direct editor changes.
CopyCopies the source currently visible in the editor.
Save…Choose a destination and review the proposed file action before it is applied.
Replace approvalA different existing file requires explicit approval before replacement.
ClearClears editor text only. It does not delete Automation rows.
Generated / Edited exportGenerated code reflects the current Automation grid. Direct editor changes remain an export draft until you deliberately apply them.
Profile and playbackThe selected profile shapes exported source. Studio playback and destination-project execution remain separate, so exported code should be reviewed and tested in the project that will own it.
Expected resultCode regenerates a readable flow for the selected profile, Results reports the Studio run, and Copy or Save exports only after you review the source.
Check first before exportCompare the generated sequence with the grid, review dependencies, and test the saved source in the destination project.
Question: does editing Flow code change the grid?No. Direct editor text remains an export draft unless you deliberately apply a supported proposal to a step.
REUSABLE DEVELOPER CODE
Create a compact handoff without changing the flow
- Build or record the complete flow.Reusable code reflects the current Automation sequence and its authoring choices.
- Select the destination profile.Choose the supported C#, Java, or Python profile that matches the destination project.
- Choose Reusable.Studio opens a separate read-only reference; it does not replace Flow code or change the grid.
- Review the handoff.Confirm that the readable structure, locators, data, and ordered steps match the current flow.
- Search, copy, or save.Use Find or Ctrl+F, then move the useful parts into the destination project.
- Regenerate after changes.Generate a fresh copy after changing the flow, policies, profile, or Selenium target.
Deliberate AI attachmentReusable code is shared with Copilot only when you explicitly select it and approve the preview.
Expected resultYou receive a compact, readable reference for deliberate integration into the destination project.
Check first when something is missingConfirm the current flow still uses it, then regenerate the handoff.
Question: does Reusable change Automation?No. It is a separate, read-only reference for review and integration.
VERSION GUIDE
Understand browser and Selenium compatibility
Refresh local checkRepeats the compatibility check for the selected browser and source target.
Reload settingsApplies approved environment changes made by an administrator.
Copy dependencyCopies destination-project dependency guidance for the selected profile.
Copy startup codeCopies optional startup guidance for the destination project.
Browser downloadOpens the official browser vendor page. WebElemate does not download a browser.
Driver sourceOpens official compatibility guidance.
Selenium releasesOpens the official Selenium release page.
CloseReturns to Studio.
For individual and managed environments
Most users can rely on the guided setup. Organizations with managed devices can follow their approved browser, network, and software policies.
Expected resultRefresh local check reports what Studio found and offers practical compatibility guidance without installing or updating the browser itself.
Check first when a browser cannot startConfirm the browser is installed and current, then review the guidance shown by Version guide or contact your administrator.
Question: does WebElemate install browsers?No. It controls an installed browser and links to official vendor sources when installation or updates are required.
OPTIONAL AI COPILOT
Send only the context you choose and review every proposal
AI CopilotOpens a separate review window. It stays offline until you choose and test a connection.
ProviderSelects one of the connections you have configured.
Connections…Opens connection setup, help, saved choices, and connection testing.
Context checkboxesChoose exactly which element, locator, flow, code, or result information may be included.
Privacy previewShows the limited, redacted material before transmission.
Verify elementRequests a review of the currently inspected target.
Improve locatorRequests alternatives and rationale from the selected locator evidence.
Diagnose failureReviews the last redacted execution result.
Review generated codeRequests language- and framework-aware code review.
Implement custom codeRequests a reviewed proposal for logic that ordinary row fields cannot express.
Transfer proposalOpens a chooser so you can preview and approve only the parts you want to apply.
Translate with AIPrepares a request from Flow code. It does not send or change Automation automatically.
Send / Cancel / Clear chatSends the previewed request, cancels a supported request, or clears only the visible conversation.
Connection controlsCreate, save, test, update, forget, or delete a connection.
Remember on this deviceLets you choose whether a credential remains available after the current session.
Disconnect AIEnds the active AI session.
A safe review workflow
- Attach only necessary context.Leave unrelated context unchecked and verify the Privacy preview before Send.
- Ask for one bounded change.Describe the specific outcome you need and the limits the proposal must respect.
- Review the proposal.Check the behavior, values, locator choices, and failure handling before applying anything.
- Transfer deliberately.Preview each proposed change and approve only the parts you want.
- Confirm the affected steps.Review the updated rows and keep or restore each proposal as needed.
- Run the smallest range.Test the affected step or range first, then expand the run after it behaves as expected.
“Propose a safe step that clicks the first usable match when one exists and reports a clear failure otherwise.”
“Propose a loop with a clear maximum and exit condition. Do not add hidden retries or sleeps.”
“Propose a step that enters the existing value only when the intended input is available.”
Expected resultOnly context you enable appears in Privacy preview and is sent. A proposal remains separate until you review and approve it.
Control stays localStudio does not silently rewrite a flow or execute code inside Copilot. Approved changes run later through the normal Automation workflow.
Reject these patternsUnbounded loops, hidden retries, unnecessary waits, credentials, new browser sessions, or changes that lack clear evidence.
Question: does a translated result change Automation?No. Translations remain review, copy, and export artifacts until you deliberately apply a supported proposal.
Verified scope
Clear support boundaries build buyer confidence.
WebElemate is a focused Windows desktop authoring and playback product. It complements the engineering stack around it.
Browser and execution
Windows desktopChromeEdgeFirefoxLocal authoringLocal playback
Studio works with an installed supported browser. It does not install the browser or act as a hosted execution service.
Generated source and assertions
C# plainNUnitxUnitMSTestJava plainJUnit 5TestNGPython plainpytestunittest
The selected profile changes test structure, imports and dependencies, setup and cleanup, assertions, and failure APIs. Generated source must still be reviewed, compiled, tested, and integrated in the destination repository.
Test data
CSVJSONXLSXXLSMNamed variablesColumn mapping
Map inputs to data columns, choose the run range and count, and let preflight verify the file, required columns, and available rows before the browser moves.
Browser context
TabsWindowsFramesOpen shadow rootsRecorded context switches
Opening and switching contexts remain visible operations. Replay waits for the required tab or window position and restores frame context only when a step needs it.
Clear product boundaries
WebElemate focuses on authorized browser-test authoring and playback. Teams still own target permission, destination-code review, security policy, provider terms, and production approval.
Designed for responsible use
Deterministic by default. Optional services stay explicit.
Inspection, recording, playback, diagnostics, and code generation work without an AI connection.
Users select locators, actions, waits, data, ranges, export destinations, and whether to apply proposals.
Diagnostics and optional AI context limit and redact sensitive information.
Managed environments can apply approved browser, network, update, and optional AI policies.
Product leadership
“I created WebElemate Studio to make reliable browser automation easier to build, review, and improve—without taking control away from the people who own the tests.”
Dhaval Parikh is the creator and lead architect of WebElemate Studio. The product direction is practical: keep browser evidence visible, make automation decisions understandable, produce code teams can review, and ensure execution, data, diagnostics, exports, and optional AI assistance remain under user control.
Dhaval ParikhCreator & Lead Architect · WebElemate Studio
Frequently asked questions
Important answers before evaluation.
Who is WebElemate Studio for?
It is for anyone responsible for understanding, building, reviewing, or maintaining browser tests—including testers, developers, automation engineers, analysts, domain experts, accessibility specialists, reviewers, and technical leaders. The same person can use any part of the workflow; WebElemate does not restrict features by job title.
Does Studio execute Java or Python inside the product?
No. Java and Python profiles generate destination source that should be reviewed and run in the project or CI system that will own it.
Does the current Studio export JavaScript?
No. The current interface exposes supported C#, Java, and Python profiles.
Does WebElemate install a browser?
No. It works with an installed supported browser and provides compatibility guidance when the browser cannot start.
Why retain several locators for one step?
Websites change. Keeping validated alternatives preserves the original reasoning and allows repair without repeating the entire authoring journey.
What does JS Test do?
JS Test checks a supported locator against the current live page without performing the target action. It reports matches and whether the intended element was found; it is not JavaScript code export.
How are tabs and windows handled?
Open and Switch are separate visible operations. Studio records the chosen browser context so replay can return to the intended tab or window before the next action.
What is the difference between Implicit wait and a row Wait plan?
Implicit wait is a general lookup setting. A row Wait plan contains the ordered readiness conditions for that specific step and can be adjusted without changing other rows.
What happens when an exception policy continues?
The matching row is marked amber HANDLED, its optional diagnostic message is included, and execution continues with the next step. It is not counted or colored as a pass. A Stop rule reports failure and ends that flow execution.
What is Reusable code?
It is a read-only, compact reference for integrating the current flow into a destination project. It does not replace Flow code or change Automation.
Will saving generated code overwrite a file automatically?
No. Save opens a review-first export preview. A different existing file is a Conflict and requires explicit Replace approval. If the file changes after preview, the stale plan stops before writing.
Is AI required?
No. The core product is deterministic and works with AI offline. Copilot is an optional review assistant that receives only the context categories selected by the user after privacy preview and redaction.
Does AI output run automatically?
No. Copilot is a review surface. A proposal remains separate until you preview and deliberately approve a supported change, which is then tested through the ordinary Automation workflow.
Does WebElemate replace our repository or CI/CD platform?
No. Your repository, test framework, builds, code review, and CI remain the source of truth. WebElemate improves browser-based authoring, validation, debugging, and code handoff.
Does generated code still need review?
Yes. Generated source must be reviewed, compiled, tested, and integrated in the destination repository. Framework and Selenium selections shape the output but do not replace engineering review.
What does a framework profile change?
It shapes the generated test structure, dependencies, setup and cleanup, assertions, and failure reporting for the selected C#, Java, or Python destination.
Where are the privacy, license, and third-party details?
The product website includes the current Privacy Policy, Terms of Use, End-User License Agreement, and license, dependency, notice, and SBOM information.
Available for Windows
Turn a browser journey into automation your team can review, run, and own.
Install WebElemate Studio from Microsoft Store, then follow the five-minute tutorial to build your first reviewable flow.