Oprex Test Recorder — Chrome extension

Install in 2 minutes

1. Download oprex-test-recorder.zip (button above) and extract it to a folder.
2. Open chrome://extensions → enable Developer mode (top right) → Load unpacked → pick the extracted folder.
3. Click the Oprex icon → Settings: API URL https://api.oprex.id, an API key with write scope (create one at member.oprex.id → API Keys), optional Project ID → Save & connect. Green dot = connected.

A Chrome Web Store listing follows after the trial period; until then the manual (side-load) install above is the official path.

Recording a test case

1. Open the page of the app under test.
2. Oprex icon → ● Start recording. A red "Oprex recording" badge appears on the page.
3. Do the scenario like a normal user: click, type, pick from dropdowns, tick boxes, press Enter. Consecutive typing collapses into one step.
4. ■ Stop & save → a new test case appears in your project (tags otp, recorded) with final evidence.

Replaying

Oprex icon → Load list → pick a test case → ▶ Run in the active tab. Per-step results + screenshots are in Oprex → Test Runs. Your AI agent (Claude Code, Cursor, Kilo) can trigger the same via the MCP tool oprex_otp_run.

Privacy & permissions

• Why "all sites"? The extension must read buttons and fields on whatever app you test. It only acts when you press Record or Run.
• What leaves the browser? Only element locators, non-sensitive field values, page URLs and screenshots — sent to your own Oprex tenant (api.oprex.id) with your API key.
• What never leaves: password fields, card numbers, national IDs, PINs, OTP codes — masked in the browser into {{secret_N}} variables you supply at run time.
• Source is open in the kinexa-oprex/otp-extension repo.