Test results no longer contain test failures

[ButkiewiczP]

So there seems to be some confusion around whether this was actually fixed, or is in the process of being fixed.

As of the 0.2.4 release, test failures are no longer included in the output (only verified on Xcode 8 right now). This was originally captured in issue #209 / #234 and later addressed in PR #240. However, before 0.2.4 was released, the changes from that PR were reverted in commit 28a56ab .

Is there something else that needs to be fixed in order to get that change merged again? I'm not sure why it was reverted, as this has been an issue for quite a few months now.

[rfodge]

+1

[jetersen]

This is still a issue 👎

[kenji21]

See also issue #291, which manage "testing restarts" xcode does when a test crashes (swift fatalError for example)

[daniel-beard]

Also seeing this

[dreampiggy]

I still face the issue. If some thread-safe code test fail, it mostlly will call Objective-C realse and finally call CFRelease -> pthread_kill, which trigger a SIGABRT signal and no any error reason occur. I have to check the raw stdout to find this reason, really suck. Any good idea ?

[stidch]

Any activity planned for this issue?

Isn't it actually a key feature of Xcpretty containing all executed tests (including crashed once) in the XML?

[draganrakas]

We're seeing this issue as well, where crashed tests don't appear in the xcpretty JUnit output.
Related: #291

Assertion failures are fine, but crashed tests are missing.