[dotnet-port-fixes] Add checkpoint identity workflow tests - #806
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Note
This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.
Parity Review: ✅ ApprovedThis PR adds regression test coverage to The new tests port upstream .NET regression coverage from microsoft/agent-framework#7415 for checkpoint-resume identity stability of hosted agents. The Go runtime behavior was already aligned; this PR locks it in with tests. Scope: Test-only — no public API surface changed.
|
|
Copilot resolve the merge conflicts in this pull request |
Co-authored-by: gdams <20224954+gdams@users.noreply.github.com>
Resolved the merge conflicts by merging latest |
Summary
Adds regression coverage for workflow-as-agent checkpoint resume when the inner hosted agents are reconstructed. The new Go tests lock in that resume succeeds when the hosted agent keeps a stable identity and fails when the hosted agent ID or configured name changes, matching the upstream .NET regression coverage from microsoft/agent-framework#7415 and commit 6a3d5352042959eb276dc52e1e7f69a6fe5e4e8a.
Ported .NET PRs
Breaking Changes
No.
Tests and Examples
go test ./workflow/agentworkflow -run 'TestNew_SerializedSession(ResumesHostedAgentCheckpointAcrossReconstruction|FailsAcrossReconstructionWithoutStableHostedAgentID|FailsAcrossReconstructionWhenHostedAgentNameChanges|ResumesFromCheckpoint|ResumesApprovalRequestFromCheckpoint)$'workflow/agentworkflow/workflow_test.goNotes
The Go runtime behavior was already aligned; this PR ports the upstream regression coverage so future changes do not break checkpoint compatibility for reconstructed hosted agents. No docs update was needed because the feature status did not change.
Closes #776