Testing Software Architecture
summary
Argues for concrete architectural tests rather than vague principles and shows actual tooling and signals to watch for using NDepend to compute metrics like cyclomatic complexity and tracking public interface growth over time integrated into CI pipelines, flags high local complexity when unit tests become fragile, flags high global complexity when changes ripple across services, cites a system that survives seven years in production despite language and infrastructure migrations by continuously measuring, reinforcing boundaries and automating those checks.
AI-written summary · about
chapters (12)
- 0:00Start
- 9:31Complexity Management
- 12:04Global Complexity
- 18:55FUNCTIONAL TESTING: UNIT, INTEGRATION, END-TO-END
- 19:33Bad Architecture
- 23:48QA Engineers
- 25:04Database Administrators
- 26:08Operations
- 27:55Static Code Analysis
- 33:42EVOLUTION DRIVERS
- 33:56ORGANIZATIONAL CHANGE DRI
- 35:35BUSINESS STRATEGY CHANGE DE
related talks
44mTesting Software Architecture
43mTesting Software Architectures
47mTesting Software Architecture
58mTesting Software Architecture
51mTesting Software Architecture
41mInside Software Architecture - Where the Bodies are Buried
53mTest architecture is a real thing
20mSupporting your architecture with code coverage and static analysis rules