OTP · UI TESTING

OTP — Oprex Test Protocol

Kinexa's open protocol that turns a tester's clicks into test cases, replayed by a runner or an AI agent — with a screenshot at every step.

Click, type, select — and it becomes a test case

OTP (Oprex Test Protocol) is Kinexa's open protocol for running and recording UI tests per object: press a button, open a dropdown, type into a textbox/textarea, tick a checkbox, wait, then assert. Every result — per-step status, duration, the locator that matched, and a screenshot — lands in the Oprex test case and test run.

Two ways to run

Chrome extension

For human testers (students, QA). Install, click Record, walk through the scenario, click Stop & save — a test case with machine steps is written for you. Passwords, cards and national IDs are masked in the browser before anything leaves your computer.

Download the extension →

Headless runner

For scheduled regression and AI agents. A Playwright container connected to Oprex runs the same test cases unattended — from the panel, REST, or the MCP tool oprex_otp_run.

Open Test Runs →

Locators that survive redesigns

Each step stores several locator candidates in order: data-testid → ARIA role + name (button "Save") → label/placeholder → text → CSS. When the UI changes, the next candidate is tried — and the report says which one matched.

What you can check

  • Actions: navigate, click, dblclick, type (with per-key delay), press, select, check/uncheck, hover, scroll, upload, wait, screenshot.
  • Asserts: visible/hidden, enabled/disabled, checked, text, value, count, url, title, attribute — with equals/contains/matches/gt/lt.
  • Security: per-project origin allowlist, eval only on the runner, evidence stored in your tenant's Asset Bucket (15-minute signed URLs).

Built for campuses and small teams

Students don't have to learn a test framework first: install the extension and click through the app. Test documentation — steps, evidence, results — is produced while testing. Progress. Not Perfection.