3 ms·
I think I know what you mean, but annotations and scanning for them is definitely Java and used very widely. Honestly, when JUnit was still "just Java" by that
by Argorak 12y ago
I think I know what you mean, but annotations and scanning for them is definitely Java and used very widely.
Honestly, when JUnit was still "just Java" by that definition, it was a much worse framework.
- guelo 12y agoThis is tangential, but before annotations JUnit still used reflection and scanning looking for methods named testXXX(). And honestly, it wasn't that much worse.
- timclark 12y agoIf I compare the lines of code between JUnit without annotations and JUnit with annotations I usually have less lines of code without annotations and I don't find it bothersome to name my test method correctly. Annotations in Java have always bothered me! Why are they needed? I don't need them in Clojure, Go, Haskell, C - similar behaviour is supplied by alternative means.
- thescrewdriver 12y agoIn many cases annotations are just a crutch to work around glaring limitations in the Java language.