Clear boundaries in code are important... and hard. Especially in legacy code. ArchUnit allows you to capture the structure your team agreed on in tests.
Starting to work with legacy code
Recently we picked up a project and attempted to move it forwards. We wanted to introduce new concepts and structures in a new UI. Also, we wanted to keep the old UI until the new one was ready for production.
The new UI would start as a read-only version. It should not depend on existing code, allowing us to learn the codebase over time. Only in the next phase would we change the existing business logic.
Typically, you would document decisions like this, for instance in an ADR. This is a great way to capture the reasons behind the decision. But expressing the decision in tests gives additional benefits.
The benefit of tests
The tests remind everyone on the team about the decision. If my code for the new UI depends on legacy code, the tests break. This obviously helps new team members learn about decisions that have been made.
It is also helpful for those who have been on the team from the beginning. If in the heat of the moment a dependency sneaks in, then there is a failing test. Gently reminding you of the team agreement. Also, when you have bigger changes, maybe a refactoring, it's hard to keep track of all the changes. ArchUnit tests lift some mental burden off from you because they check that you agreed to avoid dependencies to legacy code.
Failing tests as a chance
When a test fails, it gives you the chance to rethink the approach you just went with. Either you come up with a better idea, or you start a fruitful discussion with your teammates. Of course, the outcome of such a discussion can be to change or relax the rules a bit. But then it is a deliberate decision. Nothing sneaked in without you being aware of it. Changing the ArchUnit tests is something that can be easily seen in a PR review. Which again is a chance for a fruitful discussion with your team.
The power of arch unit tests
ArchUnit tests run pretty fast. They won't slow your test suite down, giving you an additional safety net on every test run. This allows you to avoid dead ends when implementing or refactoring early; way earlier than a fellow developer can in a code review.
So in short ArchUnit tests will help your team to
And all of that with every test run. Which means early and reliable feedback.
Show, don’t tell
I hope by now that you are excited about ArchUnit. So what does this look like in code?
ArchUnit tests are regular JUnit tests. Just include ArchUnit as a dependency and you are ready to go.
// gradle dependencies { testImplementation 'com.tngtech.archunit:archunit-junit5:0.20.1' }
In our project we decided that all code for the new UI lives in a package called v2. In the test we declare that this v2 package should not rely on legacy code. For this we use ArchUnits ability to assert on package dependencies. In the simplest form this looks as follows
@Test public void version2PackagesShouldNotDependOnLegacyPackages() { // first declare the rule var isolatedVersion2 = noClasses() .that() .resideInAPackage("com.acme.webapp.v2..") // the trailing dot tells ArchUnit to match all sub-packages as well .should() .dependOnClassesThat().resideInAPackage("com.acme.webapp.legacy.."); // second define on which classes the rule should be applied var webapp = new ClassFileImporter() .withImportOption(new ImportOption.DoNotIncludeTests()) .importPackages("com.acme.webapp"); // finally run the check isolatedVersion2.check(webapp); }
But we cannot completely isolate from legacy code. We do want to make use of logged in users for example. So we need to allow some classes. For that we can create a custom predicate that defines the exceptions.
DescribedPredicate legacyPackagesWithAcceptedDependencies = new DescribedPredicate<>("reside in legacy package"){ String[] acceptedDependencies = { "OrganizationDto", "IdentityContext" }; @Override public boolean apply(JavaClass input) { var isAnAcceptedDependency = Arrays .stream(acceptedDependencies) .anyMatch(acceptedDependency -> input.getSimpleName().equals(acceptedDependency)); return !isAnAcceptedDependency && input.getPackageName().startsWith("com.acme.webapp.legacy"); } };
When put together the whole code looks like this
package architecture; import com.tngtech.archunit.base.DescribedPredicate; import com.tngtech.archunit.core.domain.JavaClass; import com.tngtech.archunit.core.importer.ClassFileImporter; import com.tngtech.archunit.core.importer.ImportOption; import org.junit.jupiter.api.Test; import java.util.Arrays; import static com.tngtech.archunit.lang.syntax.ArchRuleDefinition.noClasses; public class LegacyIsolationTests { DescribedPredicate legacyPackagesWithAcceptedDependencies = new DescribedPredicate<>("reside in legacy package"){ String[] acceptedDependencies = { "OrganizationDto", "IdentityContext" }; @Override public boolean apply(JavaClass input) { var isAnAcceptedDependency = Arrays .stream(acceptedDependencies) .anyMatch(acceptedDependency -> input.getSimpleName().equals(acceptedDependency)); return !isAnAcceptedDependency && input.getPackageName().startsWith("com.acme.webapp.legacy"); } }; @Test public void version2PackagesShouldNotDependOnLegacyPackages() { var isolatedVersion2 = noClasses() .that() .resideInAPackage("com.acme.webapp.v2..") .should() .dependOnClassesThat(legacyPackagesWithAcceptedDependencies); var webapp = new ClassFileImporter() .withImportOption(new ImportOption.DoNotIncludeTests()) .importPackages("com.acme.webapp"); isolatedVersion2.check(webapp); } }
Conclusion
What I like about putting team agreements into code like this is that it makes sure that the agreement is actually documented and followed. For new team members, it's easy to discover these rules; the tests will tell them. And for those who are around for longer time it's a nice nudge to think more closely about structure and dependencies. Or start a discussion instead of just being lazy and sneak in just that one exception to the rule.
