During the last days two posts Find JUnit assertions without a message and Find JUnit tests without assertions have been published here about useful rules regarding proper usage of JUnit. Now a colleague came up with the hint that it would be very useful to ensure that every occurrence of the annotation @org.junit.Ignore shall provide…
Read moreThe JPA specification allows field vs property based access for entities. Following query can be used to find entities using property access.
Read moreAs a follow up of the last post Find JUnit assertions without a message another useful constraint can be created using a set of cypher queries. How can we find all test implementations which do not perform any assertion? Here’s an example Java class: @Test public void test() { // prepare data int a =…
Read moreDuring our last Neo4j tutorial in Leipzig one of the participants pointed out that there could be some useful constraints regarding test implementations based on JUnit. A quite useful and easy thing would be finding all assertions without a human readable message:
Read morejQAssistant 1.0.0-M3 is now available. Beside new scanners, rules and improved performance the most notable change is a SonarQube plugin. It allows to define and activate or deactive rules as a part of a quality profile on a SonarQube server and creating issues for violated constraints. You’re strongly encouraged to try it! For more information…
Read more