Testing Software Architectures
summary
Claims that architecture is testable by automation using static code analysis and code queries to track erosion of module boundaries and rising local/global complexity Proven approach uses tools like NDepend (or equivalents) integrated into CI to measure trends rather than fixed thresholds Reports a live system surviving seven years despite churn and cites a cautionary example of roughly 200 services communicating where rising public method count on an API surface signals entropy and prompts targeted refactoring.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 6:21Software architecture importance
- 15:10Evolutionary architecture
- 20:39Testing beyond functional tests
- 29:18Complexity in system design
- 31:04Automating architectural tests
- 37:06Summary
- 39:04Q&A
related talks
40mTesting Software Architecture
44mTesting Software Architecture
47mTesting Software Architecture
58mTesting Software Architecture
51mTesting Software Architecture
41mInside Software Architecture - Where the Bodies are Buried
47mTestable Architecture: How to Build High-Quality Software and Ship Fast
20mSupporting your architecture with code coverage and static analysis rules
