Zelector — Robot Framework Recorder

Record a flow or pick any element — shadow DOM included — and get a Robot Framework suite with locators that survive a redeploy.

Record what you do on a page. Get a Robot Framework suite that runs. Most recorders hand you Sleep 2 and nth-child selectors, and you rewrite them before they can be committed. Zelector works on the two things that decide whether a recorded test survives. WAITS — inferred from what the page actually did after each step. A spinner that comes and goes becomes Wait Until Element Is Not Visible on it. A route change becomes Wait Until Location Contains. Timeouts come from the time the page took. Every guess shows its reason and can be edited before you export. LOCATORS — every candidate scored, every point lost explained. Classes generated by a build tool, ids regenerated on every render, classes that name a state rather than an element: marked, not handed over as though they were stable. When nothing durable exists, the panel says so while you can still ask for a data-testid. Closed shadow roots, iframes, alerts, drag and drop, hover menus and rich text editors are handled — each one a recording that otherwise replays as nothing. One permission: storage. No servers, no account, no analytics, no network requests of any kind. MIT, and the source is public.