The Power of Architectural Testing

It’s 2018. Nowadays we are used to striving for agility and we exploit automation to stay responsive in our ability to adapt to change. We write tons of unit, integration and system tests as equal part of our production code, to ensure functional correctness. We make use of powerful linters to get and retain a high level of internal code quality. We let continuous integration servers execute those tests and checks on every single commit, to get a fast feedback for our highly iterative development process.

That’s really cool, isn‘t it?

Not quite. What about architecture? The layers? The component model? The dependency rules? The 10,000 ft birds view?

We often don’t care and, even more often, don’t check those very relevant, structural aspects of extensibility and maintainability.

In a perfect world we’d have architectural tests, that can be easily defined, executed and integrated in our continuous integration process along with all the other automatic tests and checks we know and love.

Transcript

1. Devsmeetup | 28 Nov. 2018 The Power of Architectural Testing
2. Speaker Armin Weißer Servant Leader & Craftsman armin.weisser@iternity.com https://www.xing.com/profile/Armin_Weisser2 https://gitlab.com/iternity
3. Ability to adapt to C H A N G E Test Automation Build Automation Clean Code Proper Architecture *Icons made by Freepik and Smartline from www.flaticon.com
4. Clean Code Code Formatting Linting Code Metrics *Icon made by Freepik from www.flaticon.com
5. Test Automation Unit Tests Verify each software component. Integration Tests Verify the interactions between components. System Tests Verify the fully integrated system. Performance/Load/Security Tests Verify non-functional requirements. *Icon made by Freepik from www.flaticon.com
6. Build Automation: Let the CI/CD pipe do all the work! *Icon made by Freepik from www.flaticon.com
7. Layer 2 Layer 1 *Icon made by Smartline from www.flaticon.com Proper Architecture Component Component Component Dependency Dependency Dependency
8. Are we now able to cope with C H A N G E ? Test Automation Build Automation Clean Code Proper Architecture *Icons made by Freepik and Smartline from www.flaticon.com
9. Layer 2 Layer 1 *Icon made by Smartline from www.flaticon.com Architectural Erosion Component Component Component Component Component Component
10. TEST YOUR ARCHITECTURE 111Einself!!!
11. *Icon made by Smartline from www.flaticon.com Architectural Style Ordering Shipping REST-API EMAIL MySQL IO CORE Dependency Rules * → CORE && not( IO → IO ) && not( CORE → IO )
12. // 1. Choose your architectural style var archStyle = new CleanArchLight("Petshop"); // 2. Identify and parse all components and dependencies in your solution. var petshopSolution = Microsoft.CodeAnalysis.MSBuild.MSBuildWorkspace .Create() .OpenSolutionAsync("Petshop.sln") .Result; var dependencies = new DependencyCollector(archStyle).Collect(petshopSolution); // 3. Check for invalid component dependencies. var checkedDependencies = DependencyCheck .WithDependencies(dependencies) .WithRule(archStyle) .Result(); // 4. Assert that all dependencies are allowed Assert.That(checkedDependencies.AllDependenciesAllowed, Is.True, "There are invalid dependencies in your code!"); https://gitlab.com/iternity/archlint.cs
13. https://github.com/TNG/ArchUnit JavaClasses classes = new ClassFileImporter().importPackages("com.tngtech.archunit.example"); Architectures.layeredArchitecture() .layer("Controllers").definedBy("com.tngtech.archunit.example.controller..") .layer("Services").definedBy("com.tngtech.archunit.example.service..") .layer("Persistence").definedBy("com.tngtech.archunit.example.persistence..") .whereLayer("Controllers").mayNotBeAccessedByAnyLayer() .whereLayer("Services").mayOnlyBeAccessedByLayers("Controllers") .whereLayer("Persistence").mayOnlyBeAccessedByLayers("Services") .check(classes);
14. Ability to adapt to C H A N G E Test Automation incl. Architectural Tests Build Automation Clean Code Proper Architecture *Icons made by Freepik and Smartline from www.flaticon.com
15. D E M O
16. References ▪ archlint.cs for .NET – by iTernity GmbH https://gitlab.com/iternity/archlint.cs ▪ plantuml.cs for .NET – by iTernity GmbH https://gitlab.com/iternity/plantuml.cs ▪ ArchUnit for Java – by TNG Technology Consulting GmbH https://github.com/TNG/ArchUnit ▪ The Clean Architecture – by Robert C. Martin https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html TEST YOUR ARCHITECTURE 111Einself!!!