I have an erronous test class that cannot be loaded in the container due to a NoClassDefFoundError. (A dependent class is missing.)
      The test passes unexpectedly and all test methods are reported to have passed although log entries or SystemOuts show that the methods are actually never invoked.

      The problem seems to be a regression that came with the last release.
      In JUnitTestRunner the TestResults exception is overwritten with null in such a case.
      I will attach a screenshot of the debugger showing that.
      I also have a try of a patch that I will link as soon as I prepared the pull request on github.

            [ARQ-1758] Test passes although it fails unexpectedly

            Aslak Knutsen added a comment - - edited

            Aslak Knutsen added a comment - - edited pushed upstream https://github.com/arquillian/arquillian-core/commit/e39433696861f11588180894378c32f795da8085

            I just wanted to create a bug report for what i think is the same issue as this: A test that should clearly fail passes because of a failure to inject members. I managed to isolate the problem in a quickstart project: https://dl.dropboxusercontent.com/u/6070309/arq-pass-bug.tgz

            GreeterEJB doesn't implement GreeterRemote, thus it's obviously not possible to resolve the bean. If you fall back to Arquillian 1.1.3 an Exception is thrown, though with 1.1.4 the test just passes.

            Daniel Latzer (Inactive) added a comment - I just wanted to create a bug report for what i think is the same issue as this: A test that should clearly fail passes because of a failure to inject members. I managed to isolate the problem in a quickstart project: https://dl.dropboxusercontent.com/u/6070309/arq-pass-bug.tgz GreeterEJB doesn't implement GreeterRemote, thus it's obviously not possible to resolve the bean. If you fall back to Arquillian 1.1.3 an Exception is thrown, though with 1.1.4 the test just passes.

            Thanks. Noticed some similar behavior when using Rules. Working on a fix to get the whole Rule thing solved. Will take this into consideration when applying that.

            Aslak Knutsen added a comment - Thanks. Noticed some similar behavior when using Rules. Working on a fix to get the whole Rule thing solved. Will take this into consideration when applying that.

            Sent PR on Github: https://github.com/arquillian/arquillian-core/pull/65
            I am not sure if it really solves the whole story as I guess that the recent changes were done due to the random build problems with Wildfly and Junit 4.11.
            But the test case passes and my own test suites now fail as expected

            Robert Panzer (Inactive) added a comment - Sent PR on Github: https://github.com/arquillian/arquillian-core/pull/65 I am not sure if it really solves the whole story as I guess that the recent changes were done due to the random build problems with Wildfly and Junit 4.11. But the test case passes and my own test suites now fail as expected

              aslak@redhat.com Aslak Knutsen
              robert.panzer_jira Robert Panzer (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: