.NET: Split DurableTask/AzureFunctions integration tests into dedicated CI job

[giles17]

Motivation and Context

DurableTask and AzureFunctions integration tests require emulator setup and only run on ubuntu/net10.0. Splitting them into a dedicated job enables path-based filtering (skip when unrelated code changes) and removes emulator overhead from the main dotnet-test job.

Description

• Add -TestProjectNameExclude parameter to New-FilteredSolution.ps1
• Add functions and core path filters to the paths-filter job
• Exclude DurableTask/AzureFunctions projects from the main dotnet-test job
• Remove emulator setup step from dotnet-test (no longer needed)
• Add new dotnet-test-functions job (ubuntu/net10.0 only, path-conditional)
• Update merge gate and report job to include dotnet-test-functions

Testing

• YAML validated with yaml.safe_load
• -TestProjectNameExclude tested locally: DurableTask and AzureFunctions correctly excluded from filtered solution

[github-actions]

Automated Code Review

Reviewers: 4 | Confidence: 91%

✓ Correctness

The PR correctly splits DurableTask/AzureFunctions integration tests into a dedicated CI job. The path filters, conditional logic, merge gate updates, and PowerShell script changes are all properly implemented. The new TestProjectNameExclude parameter correctly iterates over patterns and is applied after TestProjectNameFilter. The merge gate handles skipped jobs correctly since 'skipped' results don't trigger the failure/cancelled checks. The report job's artifact download pattern correctly matches the new artifact name.

✓ Security Reliability

This PR is a clean CI refactoring that splits DurableTask/AzureFunctions integration tests into a dedicated job. The merge gate correctly handles skipped jobs (result='skipped' doesn't match 'failure' or 'cancelled' checks), the PowerShell exclusion parameter is properly implemented, secrets are used consistently with existing patterns, and path filters appropriately trigger the new job when core dependencies change. No security or reliability issues identified.

✓ Test Coverage

This PR is a CI infrastructure change that splits DurableTask/AzureFunctions integration tests into a dedicated job and adds a -TestProjectNameExclude parameter to New-FilteredSolution.ps1. The new parameter has implicit functional coverage through the CI workflow (the filtered solution is used by dotnet test, so failures would surface). However, there are no dedicated unit tests (Pester tests) for the script — this is a pre-existing gap, not introduced by this PR. The existing parameters (e.g., -TestProjectNameFilter) also lack isolated tests. The workflow logic is sound: path filters, merge gate inclusion, and artifact naming all align correctly.

✗ Design Approach

The split-job approach is mostly sound, but the new path gating for dotnet-test-functions misses part of the DurableTask/AzureFunctions dependency chain. As written, a change limited to Microsoft.Agents.AI.Workflows.Generators can alter those integration-test binaries while causing the dedicated functions job to skip, and the main dotnet-test job now excludes those same integration tests.

Flagged Issues

• The new core path filter in .github/workflows/dotnet-build-and-test.yml omits dotnet/src/Microsoft.Agents.AI.Workflows.Generators/**, even though DurableTask depends on Microsoft.Agents.AI.Workflows (dotnet/src/Microsoft.Agents.AI.DurableTask/Microsoft.Agents.AI.DurableTask.csproj:30) and Microsoft.Agents.AI.Workflows includes Microsoft.Agents.AI.Workflows.Generators.csproj as analyzer (dotnet/src/Microsoft.Agents.AI.Workflows/Microsoft.Agents.AI.Workflows.csproj:34-39). With the new exclusion of DurableTask/AzureFunctions ITs from the main job, generator-only changes can now skip all affected integration tests.

Suggestions

• Expand the core paths-filter block to include dotnet/src/Microsoft.Agents.AI.Workflows.Generators/** source-generator changes still trigger dotnet-test-functions for the DurableTask/AzureFunctions dependency chain.

---

Automated review by giles17's agents

[Copilot]

Pull request overview

Splits the DurableTask and Azure Functions integration tests out of the main .github/workflows/dotnet-build-and-test.yml dotnet-test job into a dedicated CI job to avoid emulator setup overhead in the primary test matrix and to enable more granular path-based job triggering.

Changes:

• Added -TestProjectNameExclude support to dotnet/eng/scripts/New-FilteredSolution.ps1 to remove specific test projects after applying -TestProjectNameFilter.
• Extended paths-filter with functions and core filters and used them to conditionally run a new dotnet-test-functions job (ubuntu/net10.0 only).
• Excluded DurableTask/AzureFunctions integration test projects from the main integration-test solution generation and removed the emulator setup from the main dotnet-test job.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
dotnet/eng/scripts/New-FilteredSolution.ps1	Adds an exclusion parameter to filter out specific test projects when generating filtered .slnx files.
.github/workflows/dotnet-build-and-test.yml	Introduces path filters and a new dedicated job to run DurableTask/AzureFunctions integration tests with emulator setup.