Supporting your architecture with code coverage and static analysis rules
summary
Describes a practical rollout: measure coverage with Jacoco, check results into CI, and apply inclusion and exclusion rules so only architecturally relevant files count; that shifts an example metric from roughly 50% to a more meaningful 70% of “code that matters.” Enforce class simplicity with static checks (use cyclomatic complexity thresholds) so excluded files can’t hide testable logic, and require consistent names like DTO naming to auto-exclude API models while failing builds on violations.
AI-written summary · about
chapters (7)
- 0:00Introduction to architecture support
- 3:56Challenges with code coverage targets
- 7:48Exclusion rules for meaningful coverage
- 10:55Enforcing rules with static analysis
- 14:44Architecture enforcement through rules
- 16:51Monitoring coverage over time
- 19:40Conclusion and Q&A
related talks
42marchitect's Guide to Managing a Code Base
44mTesting Software Architecture
43mTesting Software Architectures
40mTesting Software Architecture
48mDown the Ivory Tower towards Agile Architecture
50mCoevolution of Architecture & Code - Closing The Gap
58mTesting Software Architecture
07msoftware architecture vs code