Open bbadjari opened 4 months ago
Since #774 (released with ArchUnit 0.23.0), ArchUnit can Fail Rules on Empty Should, i.e. when the should-part of rules is evaluated against an empty set of classes, which should catch your case.
You're not accidentially using an archunit.properties
file with archRule.failOnEmptyShould=false
(or even a very old version of ArchUnit), are you?
Is there a convenient way to fail tests when no classes are imported via
ClassFileImporter
? I found some old tests that continued to pass even though they were doing nothing useful becauseClassFileImporter
was attempting to import classes from a package (via theimportPackages()
method) that no longer existed.