architectural-fitness

Enforce .NET assembly dependency rules by codifying layer boundaries as automated tests using NetArchTest. This prevents architectural drift by causing test suite failures when Domain, Application, or Infrastructure assemblies reference forbidden layers.

Automate naming conventions checks for .NET handlers and entities by adding NetArchTest to a test project configured to run in CI. Assertions validate structural expectations like handlers ending with Handler and entities using private setters, failing the build on violations.

Validating layer dependencies in a .NET solution before merge is best done by running architecture tests in CI pipelines. This catches unintended references and naming regressions early, which is especially useful when onboarding contributors or evolving large solutions.

Yes, NetArchTest works with .NET test projects in CI pipelines. It requires the NetArchTest.Rules package added to your test project, where you create dependency and naming tests that run during CI and fail the build on rule violations.

Limitations of using NetArchTest for architecture tests include its strict requirement for .NET test projects configured to run in CI. It cannot enforce rules outside .NET ecosystems and relies entirely on assertions that must fail the build to catch regressions effectively.