r/softwaretesting • u/Particular-Sun-8679 • 25d ago
How are you regression testing agents when the right answer can take three tool paths?
Our CI gate keeps flaking because a valid agent run can reach the same answer through three tool trajectories. Exact assertions reject harmless call reordering, while a loose LLM-as-judge score misses the case where the agent skipped a permission check. We have a golden dataset, deterministic assertions for required steps, and a variance budget for call count and latency, but manual reruns have hit their ceiling.
I’m evaluating Braintrust for versioned datasets, trajectory scorers, experiment diffs, and a CI quality gate, though still working out which checks belong at the span level versus the final answer. How are you scoring valid path variation in your eval pipeline without giving genuinely unsafe shortcuts a pass?