Testing Software Architecture
summary
Shows how to test architecture by turning qualities into measurable checks using architectural Fitness functions and common tools like ArcUnit and Sonargraph. Uses a student-assessment system with 20 to 120,000 concurrent users to demonstrate concrete tests: checksum comparisons that detect lost answers between submit queue and DB, queue-depth throughput tracking, response-time vs load trends, and startup-time (MTTS) that doubled after a release. Compares continuous vs triggered fitness functions and their tradeoffs.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 2:31Why test software architecture
- 8:09Operational characteristics testing
- 15:23When to test architecture
- 21:06Testing student assessment system
- 35:54Structural integrity testing
- 45:22Summary and key takeaways
- 46:24Q&A session
related talks
58mTesting Software Architecture
44mTesting Software Architecture
40mTesting Software Architecture
43mTesting Software Architectures
01h 15mHow to measure your architecture
01h 34mThe Intersection of Architecture and Implementation
53mTest architecture is a real thing
42mFitness Functions for Your Architecture – in Practice