Within your parent module create a directory „jqassistant“ and a rules file „my-rules.xml“ in it:
<requiresConcept refId="junit4:TestClass" />
<description>All JUnit test classes must have a name with suffix "Test".</description>
t.name =~ ".*Test"
t AS InvalidTestClass
<includeConstraint refId="my-rules:TestClassName" />
Run the build
Execute the following command from your parent module:
The build will fail with the message specified by your rule if it is violated. If everything is fine you can also create a report as part of your Maven site:
Explore your application
jQAssistant comes with an integrated Neo4j server, you can run it using
Would you like to explore Java structures online? Then you should have a look at our Neo4j demo instance at /demo/java8!
It gives you access to a Neo4j browser where you can execute your own queries and explore the structures of the Java 8 Runtime Environment as scanned by the jQAssistant Java plugin. Just enter one of the following queries in the top level area and hit Ctrl-Enter:
How many types are contained in the Java Runtime Environment?
Which class extends from another class?
Which classes contain the highest number of methods?
class.fqn, count(method) as Methods
Which class has the deepest inheritance hierarchy?
class.fqn, length(h) as Depth
Which classes are affected by IOExceptions?
jQAssistant – Getting Started.
If you want a fast and effective start with jQAssistant you should check out the new 2-day-workshop. The full agenda is available at www.buschmais.de/seminare (Only in German).
You want to have a chat about Software Architecture and Quality Assurance?
Dirk, Stephan and Oliver will be attending the following events either as a visitor or as a speaker.
Feel free to contact him beforehand!