✅ Deploy Preview for testcontainers-dotnet ready!

Name	Link
🔨 Latest commit	480f294
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-dotnet/deploys/6907109f9e67480008d12158
😎 Deploy Preview	https://deploy-preview-1563--testcontainers-dotnet.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Summary by CodeRabbit

• New Features

  • Implemented intelligent test selection that runs only relevant tests based on changed files and branch context, improving CI/CD efficiency.

• Bug Fixes

  • Fixed test reporting to gracefully handle scenarios with no test results without causing failures.

• Chores

  • Optimized CI/CD pipeline workflow for streamlined execution.

Walkthrough

The changes implement selective test execution in CI pipelines by analyzing changed files and branch context. A new decision engine in Filter-TestProjects.ps1 filters which test projects run based on protected branches, global changes, and module-specific patterns. Collection scripts ensure safe JSON output, and workflow conditions prevent running CI jobs when no tests are collected.

Changes

Sequence Diagram

sequenceDiagram
    actor Workflow as CI Workflow
    participant Collect as Collect-TestProjects.ps1
    participant Filter as Filter-TestProjects.ps1
    participant SRT as Should-RunTests
    participant Env as Environment<br/>(Branch, Changed Files)
    
    Workflow->>Collect: Invoke with test projects
    Collect->>Filter: Pipe test projects
    
    loop For each test project
        Filter->>SRT: Invoke Should-RunTests(ModuleName)
        SRT->>Env: Read branch & changed files
        alt Protected Branch
            SRT-->>Filter: Include test
        else Global Changes Detected
            SRT-->>Filter: Include test
        else Module-Specific Changes
            SRT-->>Filter: Include test
        else No Relevant Changes
            SRT-->>Filter: Skip test
        end
    end
    
    Filter->>Collect: Output filtered projects
    Collect->>Workflow: Return JSON array or []
    
    alt Non-empty test-projects
        Workflow->>Workflow: Run CI job
    else Empty test-projects
        Workflow->>Workflow: Skip CI job (conditional)
    end

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20–25 minutes

• Key areas requiring attention:
  • Logic in Should-RunTests function: verify all decision rules are correct and cover intended scenarios (protected branches, global patterns, module categories)
  • Configuration arrays for protected branches, global changes, and module categorization: ensure they match actual repository structure and conventions
  • Integration between Collect-TestProjects.ps1, Filter-TestProjects.ps1, and workflow steps: validate the piping, variable passing, and environment variable usage
  • Workflow conditional logic: confirm that needs.collect-test-projects.outputs.test-projects != '[]' correctly prevents empty runs
  • Null-coalescing fallback in collection script: ensure it produces valid JSON in edge cases

Poem

🐰 Hoppity-hop through the CI flow,
With smart filters that help tests grow!
No more all-or-nothing runs today,
Just the changes' tests have their say! 🎯

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

What does this PR do?

This PR adds a script that filters which test projects need to run based on the list of changed files. The CI workflow gathers all available test projects and passes them to the script for filtering.

For the main and develop branches, all tests still run as usual.

@digital88 WDYT? It's quite aligned with your version. This version doesn't yet make use of file extensions, which we should probably include. I also like the comments and explanations in your version, which we should add as well.

Why is it important?

This should help reduce CI usage and overall build time, especially for pull requests.

Related issues

• Closes [README]: Contributing new modules #1136
• Closes Chore: script to detect which tests to run in CI pipeline #1417

I think file extensions are not necessary here, regex matching $GLOBAL_PATTERNS probably covers all cases. I used to check extensions in my version just to shorten $GLOBAL_PATTERNS a bit (mine has only "src/Testcontainers/").