xunit-test-arch

Standardize xUnit test architecture by creating a MyLib.XUnit executable test project alongside a MyLib.Testing companion library for shared fixtures. Separate Unit and Integration tests into distinct folders to maintain a reproducible project layout and consistent naming conventions across the .NET solution.

Centralize shared build configuration for xUnit test projects using Directory.Build.props. This approach aligns test dependencies, coverage tooling, and MSBuild conventions across all projects in the solution, ensuring consistent multi-targeting frameworks without duplicating settings in individual .csproj files.

Configure multi-targeting in xUnit test architecture by selecting framework-specific xUnit and coverage packages via MSBuild conventions. Use Directory.Build.props to manage dependencies per target framework, ensuring accurate coverage tooling across different .NET versions like net9.0.

Yes, the xUnit test architecture prescribes a specific folder structure that explicitly separates Unit and Integration tests. It also supports dedicated folders for shared test fixtures within the MyLib.Testing library, keeping different test types organized and isolated.

Establish a companion MyLib.Testing library when scaffolding new xUnit test projects for .NET class libraries. This separates shared code and fixtures from the executable test project, enforcing consistent architecture and making test utilities reusable across multiple test projects.

Scaffold a new xUnit test project layout by applying standardized naming conventions, creating the MyLib.XUnit executable project, and setting up Directory.Build.props. This enforces consistent folder structures, multi-targeting, and coverage tooling for .NET versions from net9.0 and beyond.