Uploaded image for project: 'OpenShift Java Client'
  1. OpenShift Java Client
  2. OSJC-36

openshift-java-client: DomainResourceIntegrationTest#shouldContainErrorMessageAndContainErrorCode128 is failing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.2.0
    • None
    • None
    • None

    Description

      The test makes sure that there's an application and then kills the domain without using "force" which is supposed the fail. The exception that's being thrown then is asserted for the Messages it is supposed contain.

      The test fails in the following assertion:

      assertThat(e.getRestResponse().getMessages().get(0)).isNotNull();
      

      The assertion fails with the following error:

      java.lang.AssertionError: expecting actual value not to be null
      	at org.fest.assertions.Fail.failure(Fail.java:228)
      	at org.fest.assertions.Fail.fail(Fail.java:167)
      	at org.fest.assertions.Fail.failIfActualIsNull(Fail.java:100)
      	at org.fest.assertions.GenericAssert.isNotNull(GenericAssert.java:238)
      	at com.openshift.internal.client.DomainResourceIntegrationTest.shouldContainErrorMessageAndContainErrorCode128(DomainResourceIntegrationTest.java:122)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
      	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
      	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
      	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
      	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
      	at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
      	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
      	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
      	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
      	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
      	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
      	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
      	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
      	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
      	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
      	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
      	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
      	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
      	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
      	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
      

      This is a regression that was most likely introduced when resolving JBIDE-14509

      Attachments

        Issue Links

          Activity

            People

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: