Support of globbing

[pmiossec]

In azure pipelines (also for other CI services I imagine), what is painful to replace usage of DotNetCoreCLI and prevent drop-in replacement is the lack of support of filepath globbing.

We could have something configured like:

     - task: DotNetCoreCLI@2
        displayName: Run Integration Tests
        inputs:
          command: test
          projects: '$(Build.SourcesDirectory)/**/*IntegrationTests.csproj'
          arguments: --no-restore --nologo --configuration $(buildConfiguration)

and the DotNetCoreCLI task will take care of running dotnet test for every csproj matching the projects globbing.

If we want to switch using dotnet retest, we can't replace it just by what is written in the README.md:

    - name: 🧪 test
      run: |
        dotnet tool update -g dotnet-retest
        dotnet retest -- --no-build [other test options and args]

because we need to handle the globbing ourself and run dotnet retest for every csproj files found.

So, is it something that could be included in dotnet retest to support the globbing?
dotnet retest will take care of finding the projects to run and run them all.
It would be great!

If you think it's outside the scope of the project, maybe we could discuss (and it will serve as documentation for others) about the easiest way to do that (because I don't have an idea of an easy one).

Thanks a lot in advance.

[kzu]

Thanks for your question! This would be non-trivial to implement, since each run of the retest command emits the trx files which are then read to determine which tests to retry. And there's the issue of the GH comment summary reporting, which would overwrite previous runs too.

I think you can achieve a similar filtering by using the underlying test --filter options (where you could annotate tests with the Integration trait/category).