Unit Testing Your Architecture
summary
Shows how to add ArchUnit as a Maven dependency and write JUnit 5 tests that catch concrete issues: banning throws of generic Exception/RuntimeException, detecting use of System.out, finding package cycles via slices, and enforcing that all app exceptions extend ComponentException. Demonstrates running rules in the IDE/CI, finds five existing violations, uses ArchUnit’s freeze rules feature to baseline current violations into a stored file, and enforces layered/hexagonal dependency directions so new violations fail fast.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:52Architecture
- 1:31Architectural Q&A
- 2:29Culture is What You
- 3:55The Result: The Big Ball of Mud
- 5:37Code Review Tool
- 6:46Features
- 7:50Why Unit Tests?
- 19:36ArchUnit...
related talks
45mUnit Test Your Java Architecture With ArchUnit
43mUnit Test Your Java Architecture With ArchUnit
49mArchUnit: Guarding the Logic of Your Application
52mArchUnit - Unit Testing Architecture and Design
22mArchitecture & ArchUnit
42mArchitecture testing with ArchUnit: Implementation for DDD
46mEnforcing Architecture in Legacy Systems
01h 34mThe Intersection of Architecture and Implementation