5 Tests I Write Before I Trust a Multi-Agent Workflow in .NET 10

Description and use

Tests for verifying failure paths in .NET 10 multi‑agent workflows

Problem

Ensuring reliability of multi‑agent workflows by testing failure paths before deployment.

Outcome

All tests pass without API keys or network, confirming that the workflow correctly blocks over‑eager refunds, routes security tickets to escalation, and limits model calls.

Workflow

• Build deterministic OfflineTriageChatClient to simulate model responses
• Define TriageRoutingPolicy to route tickets based on category and urgency
• Implement ReplyPolicyGuard to enforce reply constraints
• Write unit tests for specialist over‑eager replies
• Write integration tests for routing and model call counts

Evidence

The full suite is 58 tests (51 unit, 7 integration), and all of them run with no API key and no network.

Source

The bug: a specialist writes something no human would approve.

Source

The routing rules live in a plain TriageRoutingPolicy class, and security or critical urgency goes straight to the escape step, even at low confidence.

Source