Alvecta.Foundation.ArchitectureTesting 4.1.37

Universal architecture-test harness

Everything in this folder is solution-agnostic and is intended to be lifted, as-is, into a shared NuGet package (e.g. Alvecta.Foundation.ArchitectureTesting) and reused across solutions that follow the same Clean Architecture / bounded-context conventions. Nothing here hardcodes Alvecta.ShopifyConnector — the product identity is derived at runtime (see below).

What lives here

The *TestsBase classes are abstract, so xunit does not run them directly. Each consuming solution provides a thin sealed subclass (the "run-host") in its own arch-test project; xunit only discovers tests in the test assembly, and discovery walks up into the inherited [Fact]s. See the files in the project root (LayerDependencyTests.cs, etc.) for the pattern — typically one line each.

Policy vs. mechanism

All policy is exposed as protected virtual members with org-default values:

• LayerDependencyTestsBase.AllowedReferences, .UnrestrictedSourceLayers
• BoundedContextTestsBase.SharedContexts, .UnrestrictedSourceContexts
• TechnologyIsolationTestsBase.ForbiddenTechnologyAssemblies, .AllowedFrameworkReferenceNames

A solution that follows the template overrides nothing. A solution that deviates (different tech stack, differently named shared kernel, etc.) overrides the relevant member in its run-host subclass.

Portability requirements for a consuming solution

1. Naming convention. Assemblies must be named Company.Product.<Context>.<Layer>[.<Qualifier>], and the arch-test assembly itself must be Company.Product.ArchitectureTests. The product prefix and company prefix are derived from that name — when packaged, the package assembly (which also ends in .ArchitectureTests) is excluded and the single remaining match is the consumer's.
2. Assemblies must reach the output directory. The fixture scans the test bin folder for Company.*.dll. The arch-test project must therefore reference (directly or transitively) every product assembly it wants to police — referencing the composition-root / ApiHost projects normally pulls the whole graph in. An assembly that nothing references is silently not checked.

When extracting to a package

• Rename the root namespace to the package's (e.g. Alvecta.Foundation.ArchitectureTesting); consuming run-hosts add a using for it.
• Package dependencies: xunit.v3 and Alvecta.Utils only. Mark <DevelopmentDependency>true</…>.
• RequestValidationTests is not part of this harness — it is a solution-specific convention and stays in the consuming project (it pulls in Alvecta.Foundation.Application.Contracts).