[
https://issues.apache.org/jira/browse/LABS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696957#action_12696957
]
Bernd Fondermann commented on LABS-337:
---------------------------------------
See build/ant/tests/junit/reports/* for more infos about the failures.
One or two of them are empty test classes, if I remember correctly.
The others are induced by the test framework's mocking class, which cannot
track and inspect more than one stanza sent directly to the client.
Failing unit tests are bad, I have to admit. Sorry. This should be fixed soon.
> Some JUnit tests fail after clean checkout
> ------------------------------------------
>
> Key: LABS-337
> URL: https://issues.apache.org/jira/browse/LABS-337
> Project: Labs
> Issue Type: Bug
> Components: Vysper
> Affects Versions: Current
> Environment: java version "1.6.0_0"
> OpenJDK Runtime Environment (IcedTea6 1.5pre-r0507febca60d)
> (ArchLinux-1.5-0.1-x86_64)
> OpenJDK 64-Bit Server VM (build 14.0-b10, mixed mode)
> Reporter: Michael Jakl
> Priority: Minor
>
> After a fresh checkout four JUnit tests fail when running "ant
> run-unit-tests":
> [junit] Test
> org.apache.vysper.xmpp.modules.core.im.handler.PresenceHandlerBaseTestCase
> FAILED
> [junit] Test
> org.apache.vysper.xmpp.modules.core.im.handler.PresenceSubRequestOutHandlerTestCase
> FAILED
> [junit] Test org.apache.vysper.xmpp.protocol.ProtocolStateTestCase FAILED
> [junit] Test
> org.apache.vysper.xmpp.protocol.ProtocolWorkerProcessTestCase FAILED
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
