Most AI projects fail. Yours doesn’t have to.
Reserve your spot today and get a production-ready Agent Blueprint in just 3 weeks
6
spots‍
‍available
Register for Your Agent Blueprint
Blog

Faster .NET CI/CD Pipelines With Test Filters

Sluggish CI/CD pipelines leave developers vulnerable to distraction. If your unit and integration tests live in one .csproj, use dotnet test filters to run only unit tests in CI and integration tests in CD.

Jan 15, 2021

By
Focused Team
Share:
Laptop screen showing a VS Code editor with a dark theme extension page and a coffee mug nearby

Sluggish integration and delivery pipelines leave developers vulnerable to distraction. If your unit and integration tests live in one .csproj and run in both CI and CD, tune your pipeline stages to run only relevant tests.

The Tests

Tuning the Pipelines

To run only unit tests in CI: dotnet test --filter Category=Unit

To run only integration tests in CD: dotnet test --filter Category=Integration

--- Photo credit: Andrew Parnell

Your message has been sent!

We’ll be in touch soon. In the mean time check out our case studies.

See all projects
/Contact Us

Let's Build better Agents Together

Modernize your legacy with Focused

Get in touch