Currently, the constraint junit:AssertionMustProvideMessage is part of the junit:Default although, it's implementation is jUnit4-specific. This is due to following two facts:

• requires only the concept junit4:AssertMethod
• matches only assert methods whose first parameter is a string

When using jUnit4 and jUnit5 at the same time (not saying that this is okay), jUnit 5 Assert methods will be always reported by this constraint becuase the message will be the last parameter.

There are three options:

1. move the constraint to the jUni4 group and add a spearate assertions to jUnit 5
2. update the constraint so that it filters for :JUni4:Assert
3. extend the constraint so that it supports both version.

My preference would be option 1. Any opinions?

Task Description

Migrate the existing documentation of the JUnit Plugin to the new reference manul.

Definition of Done for the Implementers

• The reference manual contains the same information as the old user manual
• The section on the JUnit Plugin in the old user manual points to the section for the plugin in the reference manual

Assertions usually come with a test framework like JUnit4 or 5 but others may provide their own assertions, e.g. AssertJ, Hamcrest or Mockito. Therefore any constraints depending on assertions (e.g. junit:TestMethodWithoutAssertion) should require an abstract concept which can be provided by plugins for different frameworks.

The fail()-Method of JUnit 4/5 is currently not being recognized as assertion, therefore false-positives are reported. For implementation #23 should be considered as a pre-requisite.

As core developer of jQAssistant, I want this project to be build on various plattforms with different JDK versions on each commit, so that I know if the change done my the commit does not break the build and the software is fully functional.

The following acceptance criterias must be met:

• mvn -DskipTests -Djqassistant.skip clean install must pass
• mvn -Djqassistant.skip clean install must pass
• mvn -P IT clean install must pass
• mvn -DskipTests -Djqassistant.skip=false clean install must pass

The junit5:AssertMethod concept does not support all assert methods from jUnit 5, thus leading to false positives in the constraint junit:TestMethodWithoutAssertion constraint. This is due to the fact that assert methods are considered as such if the have the following signature void assert.*

Following methods will not be matched:

• java.lang.Throwable assertThrows
• T assertTimeout*

Hi,
are there any plans for supporting JUnit 5 in the next Version?

JUnit 3 is quite old and after adding support for Junit 5 we should drop the support of Junit 3.

According to the XSD and the files junit4.xml and metric.xml there is also a metricGroup and metric element available. What are these for and what is the difference to the metric concepts available in the metric.xml? The documentation doesn't describe these elements.

Go over all documents of the documentation and unify the Asciidoctor markup.