Boundary tests for conversational agents stop guessing: conditions pulled from replies lift explicitly valid tests to 62.7%–83.3%
Boundary testing of conversational agents gets a new route: instead of inferring expected behavior from workflow-graph nodes and edges, statements describing one policy condition and the behavior expected when it holds are extracted from the agent's replies in exploratory conversations, then paired with test transformation instructions. Across four domains, 62.7% to 83.3% of tests are valid boundary tests whose expected behavior is explicitly defined by the prompt, tool code, or knowledge base, above the 47.7% to 68.1% of prior AgentEval suites; transformed tests add 13 to 46 explicit boundaries.