Solution · API Testing
API and UI — one scenario, one extension
Progon intercepts network traffic via the Chrome DevTools Protocol directly during a recording session. Turn real requests into API checks — no Postman, no separate tool.
Problem
UI tests and API tests live in separate tools
- Postman in one tab, Selenium in another — manual synchronization
- A failed API response is invisible in a UI test
- You duplicate environments for each tool
- Bugs at the UI/API boundary are the hardest to find
How it works
How traffic capture works
Enable network capture
Before recording a scenario, enable network capture — Progon starts listening via CDP.
Record the scenario
Click through the UI as usual. Progon captures both user actions and every API call.
Select requests
After recording, review the captured traffic and pick which requests to turn into API checks.
Run together
During scenario playback, Progon checks both UI and API responses — in a single run.
Capabilities
Key capabilities
CDP network capture
Progon uses the Chrome DevTools Protocol to intercept HTTP requests during a session. No proxy, no app changes — just the extension.
Captured requests → API checks
Turn real requests from the session into checks on status code, headers, and response body. No need to compose requests manually — Progon already saw them.
API + UI in one scenario
One scenario contains both UI steps and API assertions. An API call failed mid-flow — Progon shows exactly where.
Response assertions
Assert on status codes, keys in the JSON body, headers, and response time. Write expectations in plain language — AI helps compose the check.