0

I've got a large iOS project set up with OCUnit tests, some of which are imported from a dependent project, and some of which are local. When I have a failing test in the dependent project, I can click the error, and be transported to the line that's breaking. This isn't working for the local tests. It just takes me to the file, but not the breaking line.

Does anyone know if there is something special I need to do in my unit tests, or configuration of XCode, to get jumping to the broken test working?

(I'm on XCode 4.6.2)

joseph.hainline
  • 24,829
  • 18
  • 53
  • 70
  • Do you use normal STAssertX macros? – e1985 Jun 12 '13 at 19:54
  • And also, what do you mean with "a dependant project"? Are all your tests in the same test target? – e1985 Jun 12 '13 at 19:55
  • I do use normal assert macros, and I mean that there is another XCode project in my workspace, that is a build dependency of the first project, so it builds automatically when I build the first project. – joseph.hainline Jun 22 '13 at 02:01

1 Answers1

0

It's not you. Xcode 4 doesn't correctly interpret relative paths like proj1/foo/../../proj2/bar/file.m for unit test failures.

Jon Reid
  • 20,545
  • 2
  • 64
  • 95