Continuous Testing and Architectural Integrity: Performance Fences, Acceptance Test Nets, and Dependency Checks

Building on a previous discussion about software decay, the author emphasizes continuous testing as a crucial feedback loop that uses a left‑shift approach to automate and accelerate testing across all development stages, ensuring quality standards are met.

For a North American client, a performance‑testing fence was added to the CI pipeline, defining explicit response‑time thresholds in user‑story acceptance criteria; each code commit triggers performance tests, turning the CI status red if limits are exceeded, which forces developers to investigate and fix regressions.

In an Australian financial legacy project, an acceptance‑test net was built with JBehave and BDD specifications, turning tests into living documentation that captures real business scenarios, helps discover mismatches between code and documentation, and enables safe technology‑stack migration using feature toggles.

The author also introduces ArchUnit for package‑dependency checks, showing how to write unit‑style architecture tests. Example snippets include:

noClasses()
    .that()
    .resideInAPackage(".source..")
    .should()
    .dependOnClassesThat()
    .resideInAPackage(".foo..");

and

classes()
    .that()
    .resideInAPackage(".foo..")
    .should()
    .onlyHaveDependentClassesThat()
    .resideInAnyPackage(".source.one..", ".foo..");

Finally, a full ArchUnit layer‑dependency test is presented:

@RunWith(ArchUnitRunner.class)
@AnalyzeClasses(packages = "hk.org.xx.model.xxx.xxxx")
public class LayerArchitectureTest {
    @ArchTest
    public static final ArchRule layer_dependencies_are_respected = layeredArchitecture()
            .layer("biz").definedBy("hk.org.xx.model.xxx.xxxx.biz..")
            .layer("persistence").definedBy("hk.org.ha.model.cms.hafm.persistence..")
            .whereLayer("biz").mayNotBeAccessedByAnyLayer()
            .whereLayer("persistence").mayOnlyBeAccessedByLayers("biz");
}

The author concludes that architectural decay is an ongoing enemy and that continuous testing is a powerful weapon that should be actively employed.