Well its public so who knows in what other package is using it.
And it's static, so who know what kind if monster is calling it from some inapropriate place.
I have seen static methods being called from translation/localization files, because "it works".
IntelliJ finds most uses in my experience unless you're doing something weird with reflection or similar. And if it's a public facing API only used by the library's consumers..– it should be used in tests at the very least! Especially if it's prone to regressions like the comment suggests
There are only 7 unit test classes. 2 of which I wrote myself this month.
Well its public so who knows in what other package is using it. And it's static, so who know what kind if monster is calling it from some inapropriate place. I have seen static methods being called from translation/localization files, because "it works".
IntelliJ finds most uses in my experience unless you're doing something weird with reflection or similar. And if it's a public facing API only used by the library's consumers..– it should be used in tests at the very least! Especially if it's prone to regressions like the comment suggests
There are only 7 unit test classes. 2 of which I wrote myself this month.