05/08/2016, 2:28 PM
What's the best way to define
fields/methods in JUnit tests? With Java I usually declared a public field having the annotation. If I do the same with a public Kotlin property, the compiler will generate a private field having the annotation, and will put a public getter in front of it (without the annotation). This will throw a runtime exception, since JUnit requires the annotated field to be public, or the method to be annotated. Right now I added
to the property. But while that works, it looks odd and maybe there's some better way? How do you use JUnit rules?