Photo by Mohammad Rahmani on Unsplash

Test Your Software Architecture with the ArchUnit

With the iteration of requirement development, the gradual increase in the amount of code, the introduction of new classes, the features, and many other factors, the architectural rules at the beginning of the system will inevitably be destroyed. For example, the unforeseen violations of the specification are irregular naming, layered code are not standardized, etc

The architectural corruption will affect the maintainability and scalability of the software system because it requires us to check the coding specification, module classification specification, class dependency specification, et.

There are many other specifications that may need to be customized, which may eventually output a document. However, who can guarantee that all developers develop parameters according to the specifications of the document? It is impossible for a team to establish a perfect system architecture at the beginning. It is because the system architecture should evolve with the iterations of requirement development. By using the architectural metrics, we can ensure the correctness of architecture evolution.