ansaurus

Question

Problem doing logic tests after XCode 3.2.4 upgrade

Answer 1

+2 A:

My suggestion to fix your problem is to consider using GHUnit. It works with your existing SenTestCase classes, but it also has a set of testing classes/assertions. You just setup a new target and point at their driver class. You get a fully functioning test harness that can run your tests on both the simulator and real devices. I find it much easier and more robust than setting up a test bundle and having to manage all that.

http://github.com/gabriel/gh-unit

logancautrell 2010-09-11 13:24:34

Appreciate the response but it doesn't solve the problem. I am getting the same error and would like to know how to fix it.

Patrick 2010-09-11 22:46:09

It looks like it has to do with the logging code. I have no clue how to fix that. You'd probably just have to disable it as part of your build and run the unit tests manually :(

logancautrell 2010-09-12 05:59:17

Not exactly an answer to my question, but nice though to now know about GHUnit.

leinz 2010-09-18 11:37:33

Answer 2

+3 A:

The workaround for the issue is posted in the Developer Forum of Apple. It works fine in my project. Visit the website and try it.

yusami 2010-09-18 04:56:32

Sounds nice, except that this requires being a member of the paid developer programs.

leinz 2010-09-18 09:39:10

The source code is posted in GitHub. http://gist.github.com/586296

yusami 2010-09-19 21:35:26

Answer 3

+3 A:

It seems to be a regression with some part of the reporting code not respecting timezone issues. The output is tagged as ending before it began, so gets very confused and chokes.

One work-around, that I found somewhere on Google, is to change the Run Script stage of the target.

Change

"${SYSTEM_DEVELOPER_DIR}/Tools/RunUnitTests"

to

"${SYSTEM_DEVELOPER_DIR}/Tools/RunUnitTests" 1> /tmp/RunUnitTests.out

It’s working round the issue, rather than solving it, but does work.

Andy W 2010-09-18 11:10:27

Runs fine now, thank you!

leinz 2010-09-18 11:35:44

Does this provide any indication of whether the tests failed or not? Because if not, you might as well disable the Unit Test target altogether (so you know it's not running), rather than letting it run and hide the results (so you might forget and think it's passing).

benzado 2010-09-18 18:43:21

As far as I can tell it just dumps the output into the build window without the fancy nesting that should happen, so you can still see the list of passed tests and/or errors. It doesn’t hide the results, so much as not format them.

Andy W 2010-09-20 08:32:15

ansaurus

tags:

views:

answers:

Problem doing logic tests after XCode 3.2.4 upgrade

related questions