Deployment Test
After you push a deployment, use Deployment Test in Workbench to exercise the same closed loop as production scoring without leaving the deployment editor.
Runtime Dashboard tests whatever campaign is active on a Runtime JVM. Deployment Test targets one Workbench deployment (project + deployment + version) through the Workbench backend and the runtime path configured on that deployment.
Where to open it
- Open the project and deployment you pushed.
- Open Deployment Test (phone-frame UI on the deployment).
Phone frame
- Edit the
POST /invocationsJSON body in the phone preview (customer, channel,numberoffers,paramsas a JSON string, and other fields your deployment expects). - Invoke to score. Ranked rows appear in the frame.
- Select a row and Accept to close the loop. Workbench calls
POST /deployments/test-response, which forwards feedback as RuntimePOST /response(singular) using that row’suuidandoffer_name.
For the full invoke/response contract see Quick Start — closed loop and Deployment endpoints.
Integrate tab
The Integrate tab copies ready-made client snippets for the same invoke/accept flow:
| Stack | Snippet |
|---|---|
| TypeScript / JavaScript | Fetch or axios-style examples |
| Python | Requests example |
| React | Component hook pattern |
| Vue | Composition-friendly example |
Use these when embedding scoring in an app; keep params a string and send POST /response after accept.
Related testing paths
| Goal | Surface |
|---|---|
| Single deployment, operator UI | Deployment Test (this page) |
| Any active Runtime campaign | Runtime Dashboard |
| Volume / options-store analytics | Simulations |
| Isolated business evidence for one deployment | Runtime Testing (/runtime-testing) |
| Plugin-level Cucumber | Runtime POST /test/campaign (Campaign Testing) |
Last updated on