If you have already wondered how to check architecture rules continuously in your source code, this session is definitely for you.
You will be able to make the implicit of your current architecture explicit and avoid dependencies hell...
Arthur will facilitate a hands-on session in which we will work in mob (in java or C#) with the ArchUnit library to check:
- Architecture rules (Layers, Dependencies rules, ...)
- Naming conventions
- Team guidelines
- Class dependencies
- Return types
- Linguistic Anti-patterns and avoid them
- and much more (depending on your imagination 😊)
Recommended order (do at least 1 per category / test class):
LayeredArchitectureNamingConventionGuidelinesLinguisticAntiPatternsMethodsReturnTypesAnnotations
Which other rules could be added?
Solution is available in the solution folder