A platform team wants CI for a multi-agent repo. Engineers currently only run occasional manual chat trials. Which testing strategy should you specify for integration and release?
Select an answer to reveal the explanation.
Short Explanation
A is the right CI/CD testing mix. The exam expects unit, regression, integration, and automated evaluations for multi-agent solutions—wired into CI before release. Quarterly manual chat is insufficient. Unrelated UI tests do not cover agents. Non-determinism is handled with eval thresholds, seeds, and statistical gates—not by abandoning tests. Specify the full pyramid plus agent evals in the pipeline.
Full Explanation
Correct Answer — A
Testing strategy for multi-agent solutions includes unit tests, regression tests, integration tests, and automated evaluations, integrated into CI/CD. That combination covers tools, orchestration paths, and quality regressions before deploy.
Why B is wrong: Sparse manual chat misses regressions and does not scale.
Why C is wrong: Unrelated UI tests do not validate agent behavior.
Why D is wrong: Non-determinism requires careful eval design, not zero testing.
Exam tip: Unit + integration + regression + automated agent evals in CI/CD.