opentest4j | Open Test Alliance for the JVM | Runtime Evironment library

Thank @tim_yates, Set VM option

SonarQube reports no coverage for those lines because these tests do not actually execute this code. They perform some setup, but do not call any methods on ServiceImpl.

It's useful to think of tests as having three sections, usually called given, when, and then:

• Given represents the context or environment of the test case
• When describes the action that is taken - the operation that is being tested
• Then describes the expected or intended outcome

It might be helpful to use written language to write out the requirements in this format, and then translate the written requirements to code.

For example, I might write the requirements for these test cases (in English):

• Given a repository containing an entity with a "rango" of null or "0",
• When consultarReportes is called,
• Then the returned entity should have "rango" set to "0.0000"

And:

• Given a repository containing an entity with a "prima" of null or "0",
• When consultarReportes is called,
• Then the returned entity should have "prima" set to "0.0000"

In terms of code:

• Given often translates to setting up data and sometimes mocks.
• When is a call to the method under test.
• Then is usually an assertion about the return value, or some other state affected by the method. It can also be verifications of methods called on mock objects, particularly when you are testing a method with no return value that only performs side effects.

In this case, the tests might look like this:

The problem was in the Post#commentCount field. It was mistakenly calculated through the @Formula annotation with this native subquery:

restTemplate.getForObject() method has multiple set of parameters which can be invoked with:

• restTemplate.getForObject(String url, Class responseType, Object... uriVariables)
• restTemplate.getForObject(String url, Class responseType, Map uriVariables)
• restTemplate.getForObject(URI url, Class responseType)

so you have probably mocked another method call by providing the widest matchers (Mockito.any()). I suggest you to try mock the restTemplate.getForObject() method call by providing more specific matchers, like for example:

After going through you code, these were few mistakes that I could figure out due to which your tests are failing.

TEST 1

I would recommend trying out JsonUnit. It will allow you to write assert for json with good messages on failure. An example using AssertJ integration:

It was an Intelli-J issue!

So, cleaning the Intelli-J dependency spaghetti up solved it!

1. File > Invalidate cache ... and restart. Helped a bit.
2. Closing the Intelli-J project. Then removed manually the ".idea" folder and any *.iml file.

Yes, I did option 1 previously. Especially doing action 2 solved it within a minute.

Delete the .m2 folder then try again, I just experienced this.

Update: These issues have been fixed, and a patched version of jdeps is available as part of the early access build for JDK 18 at: http://jdk.java.net/18/ (starting from build 26)

Turning my comments into an answer. There seem to be 3 bugs going on here:

1. The MultiReleaseException seems to be because jdeps can not handle classes in different jars that have the same name, such as module-info.class, but are stored in a different META-INF/versions/xxx directory. (JDK-8277165)
2. The fact that this exception is sometimes suddenly not occuring seems to be the result of a race condition in the code that checks for the above; classes of the same name having multiple versions. (JDK-8277166)
3. The MultiReleaseException is missing it's exception message since it's thrown as part of an asynchronous task, which wraps it in an ExecutionException, which then leads to jdeps not reporting the exception correctly. (JDK-8277123)

As for a workaround, I don't think there's a good one at this point, except maybe for editing all the jars on the class path so that they put the module-info.class in the same META-INF/versions/xxx directory (but, this might have other consequences as well, so you probably don't want to run with the edited jars, and only use them for jdeps).