Skip to content

Port conditional test selection changes to main#15742

Draft
radical wants to merge 2 commits intomainfrom
port-conditional-test-selection-to-main
Draft

Port conditional test selection changes to main#15742
radical wants to merge 2 commits intomainfrom
port-conditional-test-selection-to-main

Conversation

@radical
Copy link
Copy Markdown
Member

@radical radical commented Apr 1, 2026

Description

Ports the conditional test selection work from conditional-test-selection-unified-rules-design onto main as a squashed change.

This brings over the workflow updates, selector tooling, Infrastructure coverage, and supporting docs as a single forward port so the branch-only work can be reviewed against current main without replaying the original merge-heavy history.

Validation performed:

  • ./restore.sh
  • ./dotnet.sh build tools/TestSelector/TestSelector.csproj -c Release --nologo
  • ./dotnet.sh build tools/Aspire.TestSelector/Aspire.TestSelector.csproj -c Release --nologo
  • ./dotnet.sh build tools/GenerateTestSummary/GenerateTestSummary.csproj -c Release --nologo
  • ./dotnet.sh build tests/Aspire.Cli.EndToEnd.Tests/Aspire.Cli.EndToEnd.Tests.csproj -c Release --nologo
  • ./dotnet.sh build tests/Aspire.EndToEnd.Tests/Aspire.EndToEnd.Tests.csproj -c Release --nologo
  • ./dotnet.sh build tests/Aspire.Templates.Tests/Aspire.Templates.Tests.csproj -c Release --nologo
  • ./dotnet.sh test tests/Infrastructure.Tests/Infrastructure.Tests.csproj -c Release -- --filter-namespace "*TestSelector*" --filter-namespace "*.PowerShellScripts" --filter-namespace "*.ConditionalSelection" --filter-not-trait "quarantined=true" --filter-not-trait "outerloop=true"

Fixes # (issue)

Checklist

  • Is this feature complete?
    • Yes. Ready to ship.
    • No. Follow-up changes expected.
  • Are you including unit tests for the changes and scenario tests if relevant?
    • Yes
    • No
  • Did you add public API?
    • Yes
      • If yes, did you have an API Review for it?
        • Yes
        • No
      • Did you add <remarks /> and <code /> elements on your triple slash comments?
        • Yes
        • No
    • No
  • Does the change make any security assumptions or guarantees?
    • Yes
      • If yes, have you done a threat model and had a security review?
        • Yes
        • No
    • No
  • Does the change require an update in our Aspire docs?

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@radical radical added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Apr 1, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 1, 2026

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15742

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 15742"

…-selection-to-main

# Conflicts:
#	.github/workflows/tests.yml
#	tests/Infrastructure.Tests/Infrastructure.Tests.csproj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant