بنقرة واحدة
dotnet-ci-foundation
Patterns for setting up a .NET CI pipeline with GitHub Actions and xUnit test projects
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Patterns for setting up a .NET CI pipeline with GitHub Actions and xUnit test projects
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full-stack acceptance testing with Aspire.Hosting.Testing — launching entire AppHost including containers
How to wire up .NET Aspire 13.1 AppHost with containers, databases, and service projects
Patterns for integration testing Aspire-hosted .NET services with WebApplicationFactory, Testcontainers, and SQLite
Pattern for hosting Discord.NET bot inside a .NET generic host BackgroundService
| name | dotnet-ci-foundation |
| description | Patterns for setting up a .NET CI pipeline with GitHub Actions and xUnit test projects |
| domain | testing |
| confidence | low |
| source | earned |
When bootstrapping a .NET project's CI pipeline and initial test infrastructure. Applies to any .NET solution using GitHub Actions and xUnit.
.github/workflows/ci.yml with three steps: dotnet restore, dotnet build --no-restore, dotnet test --no-builddotnet new xunit template to generate test projects — it produces correct package versions and includes global <Using Include="Xunit" />tests/ directory, added to solution under a /tests/ folderAssert.True(true)) so CI has something to run from day one — proves the pipeline is wired end to end<IsTestProject>true</IsTestProject> in csproj so dotnet test discovers the project# .github/workflows/ci.yml
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-dotnet@v4
with:
dotnet-version: '10.0.x'
- run: dotnet restore
- run: dotnet build --no-restore
- run: dotnet test --no-build --verbosity normal
dotnet discover them at the repo rootdotnet test without --no-build when a build step already ran — wastes CI minutesdotnet new xunit to get correct, compatible package versions