New reporter output format breaks Jenkins test report parsing about specta

[nerdyc]

Hi Jonathan,

A classic OCUnit reporter seems like a good way to go. I'll have a look and try to have something out this week.

Can you create a GitHub issue for this?

Christian

On Aug 26, 2013, at 7:20, Jonathan Crooke [email protected] wrote:

Hi,

We recently updated Specta from 0.1.8 to 0.1.11. Whilst the new reporter output format is certainly very nice when running locally, we found that it broke JUnit output report parsing on our Jenkins instance:

FATAL: Log statements out of sync: current test suite was null
It would certainly be nice to keep up to date with Specta. Perhaps the new reporting format could be disabled with an environmental variable? This would be more easily controller when configuring the Jenkins job. Alternatively, the parser plugin may be updated, but since the old OCUnit format is so well established I don't see this happening particularly soon.

In any case, looking forward to hearing from you regarding this matter. Thanks for all the great work on this library.

J

—
Reply to this email directly or view it on GitHub.

[itsthejb]

Sounds good. Is this issue not sufficient, though?

[nerdyc]

Whoops! I wrote that last reply on my iPhone and missed the issue number at the end.

On Aug 27, 2013, at 1:40, Jonathan Crooke [email protected] wrote:

Sounds good. Is this issue not sufficient, though?

—
Reply to this email directly or view it on GitHub.

[petejkim]

With Specta v0.2.x, you can set SPECTA_REPORTER_CLASS env var to SPTXCTestReporter in your test scheme to use original XCTest reporter.