In Code Maat, the partitioning between tests and application code isn’t a stable architectural boundary; you identified a temporal coupling of 80 percent. That means they’ll change together most of the time.
But our current analysis has a limitation. Code Maat uses both unit tests and system-level tests. In our analysis, we grouped them all together. Let’s see what happens when we separate the different types of tests.
If you look into the folder test/code_maat of your Code Maat repository, you’ll find four folders, shown in the following figure. Each of them contains a particular suite of test cases. Let’s analyze them by their individual boundaries.
Open a text editor, enter the following mapping, and ...