Methodologies & Tools
Monday, 13. May 2019., 15:40
All bad architectures start with good intentions. You can pick an architecture perfectly suited for your problem, make all the developers understand the rules, make a document for all the newcomers, but these rules are forgotten, documents are not read and clutter and mess emerge in production code. Instead of relying on extensive documentation or repetitive code reviewing, a better solution is to make these rules a part of the code and inform the developer via a 'test failed' warning when a rule is broken.This presentation will be a demo of the library ArchUnit that allows you to write architecture rules as JUnit tests.