-
Bug
-
Resolution: Done
-
Major
-
4.4.0.Alpha1
-
None
-
devex #113 April 2016
ConnectionRegistryTest.shouldNotifyConnectionChange is frequently (even though not always) failing when running tests via surefire.
shouldNotifyConnectionChange(org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest) Time elapsed: 0.002 sec <<< FAILURE! java.lang.AssertionError: Exp. a notification to the listener and there was none at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.jboss.tools.openshift.test.core.connection.ConnectionRegistryTest.shouldNotifyConnectionChange(ConnectionRegistryTest.java:142) Failed tests: ConnectionRegistryTest.shouldNotifyConnectionChange:142 Exp. a notification to the listener and there was none Tests run: 314, Failures: 1, Errors: 0, Skipped: 2
- blocks
-
JBIDE-22451 Tests: Improve test coverage in OpenShift
- Open