At the start of a project, productivity is high. The architecture, components, and dependencies are clearly defined. However, as the codebase grows and requirements become more complex, unwanted dependencies creep in. Changes take longer and become more costly. The code and architecture diagrams no longer align.

Architecture tests can counteract this. They work like unit tests but focus on non-functional requirements. By automating them in the continuous build process, they prevent violations of the initially established architectural rules.

This talk provides an overview of the capabilities of architecture tests with ArchUnit.NET. Using a sample architecture, it demonstrates how various aspects of the architecture can be tested.