You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According the attachment report the test org.xwiki.observation.remote.TCPROMTest.testSerializableEvent is not failing when the method DefaultEventConverterManager#createRemoteEventData content is replaced by return null. Well I did just that and the test fail as expected.
What is special about that test is that it's not testSerializableEvent method which is failing but tearDown() which trigger jmock validation (it make sure that some methods have been called during the test).
The text was updated successfully, but these errors were encountered:
tmortagne
changed the title
Junit 4 rules don't seems to be properly supported
Junit 4 rules don't seems to be properly supported (when they validate stuff right after test execution)
Sep 11, 2018
tmortagne
changed the title
Junit 4 rules don't seems to be properly supported (when they validate stuff right after test execution)
Junit 4 tearDown is not taken into account
Sep 11, 2018
tmortagne
changed the title
Junit 4 tearDown is not taken into account
Junit 4 @Afte is not taken into account
Sep 11, 2018
tmortagne
changed the title
Junit 4 @Afte is not taken into account
Junit 4 @After is not taken into account
Sep 12, 2018
In the module xwiki-platform-observation-remote.
According the attachment report the test
org.xwiki.observation.remote.TCPROMTest.testSerializableEvent
is not failing when the methodDefaultEventConverterManager#createRemoteEventData
content is replaced byreturn null
. Well I did just that and the test fail as expected.What is special about that test is that it's not
testSerializableEvent
method which is failing but tearDown() which trigger jmock validation (it make sure that some methods have been called during the test).The text was updated successfully, but these errors were encountered: