01Why not the live agent
- A refund it is talked into is paid. A discount is honoured. Goods ship.
- A data-fishing test against real records could reveal a real customer’s details.
- Hundreds of hostile conversations would mix with real ones in your logs and reports.
02What a test copy needs
- The same model and version, instructions and tools as the live agent.
- Test modes of your payment, refund and order systems, so actions are recorded but nothing moves.
- Made-up customers, orders, discount codes and invoices, with your real rules and prices.
- Its own address and keys, so it cannot be confused with production.
Duelpoint accepts only agents you confirm are test or staging copies, and changing the address cancels that confirmation. Details in connect your agent.
03Keeping results true to live
A test result describes the version tested. Record the model, instructions and tool versions with each result, and re-test when any of them changes, including when your model provider updates the model. More in the enterprise guide.
Questions
Does a test on a copy tell me how the live agent behaves?
Yes, if the copy runs the same model, instructions, tools and policy data as the live agent. Re-test whenever any of them changes, because the result describes the version tested.
What if we only have a production agent?
Do not run adversarial tests against it. Set up a staging copy connected to test systems first, using the test or sandbox modes of your payment and order systems where they have them.
See where your agent leaks money. Tested against your own rules, with the money at stake.