I am not sure if I am making a mistake or there is a bug.
I have setup 2 tests. One of them fails one doesn't but the test suit gets the checkmark.
it seems like there has been a similar issue before in Xcode 5 but this was not useful to me.
http://stackoverflow.com/questions/19233626/xcode-5-says-tests-failed-but-shows-green-checkmarks
This is what I followed to setup kiwi
I appreciate the help.
Related
I'm having problem with getting code coverage in Xcode. It was working at some point of time, however after sometime it has just stopped showing coverage. I've checked both the schemes and test coverage plane for the appropriate settings.
This is how my scheme looks like:
This is what my test coverage plane shows after running test cases:
I tried many many things to get this fixed. Finally I ended up deleting all Xcode I had in the Mac, and cleared all the meta-data from /Users/bbirani/Library/Developer/. After all this clean-up, I re-installed Xcode and VOILAA!! it started working.
It happens to me a lot. Try restarting your xcode as well as the simulator(if you are using one). It seems like an xcode issue.
You can try some of this
Enabling the "show code coverage" from Editor while running a test case. I had this same problem before worked for me. Just try and see if that is working.
You can try checking the targets for the modules but not sure thats the case.
Or you can use the #testable way.This is a workaround and the long way to solve this.
Also u can try cleaning the whole project and deleting any derived data.And then try running the test case.
Also you can try deleting the scheme and try making a new scheme and check "Gather coverage data" for the same. If this things work then thats a xcode bug.
I hope your problem gets solved, I got stuck to the same problem before and it was frustrating to solve that, and you never know which way might work.
Maybe try using Slather instead?
https://cocoacasts.com/how-to-generate-code-coverage-reports-in-xcode-with-slather
I am doing XCUI Testing using the Cucumberish Framework. Sometimes when the test case starts it halts at the very first step
This is intermittent. Most of the times it runs seamlessly. I am are very confused what's going wrong.
I tried hard but can't get a stable solution.
I've got a real head scratcher here. I just upgraded to Xcode 7.3.1 and all my Bots have hit the floor during the integration process. For some reason or another the Bots get stuck on step 7 of 9 "Processing results". I let it sit for about 24 hours to see if it would work itself out but had no luck.
Anyone ran into this problem and have any idea what a fix might be? Short of reinstalling Xcode and Server on the build server, I'm not sure what else to try as I've tried a lot of random fixes that I've seen out on the interwebs.
Thanks in advance for any help?
UPDATE - The last thing to run in the raw build log is:
Test Suite 'All tests' failed at 2016-05-19 13:32:16.765.
Executed 131 tests, with 1 failure (0 unexpected) in 4.500 (4.592) seconds
Update: Fixed
Here's what I did:
Stopped the server.
deleted all bots from Xcode.
Went into /Library/Developer/XcodeServer and removed (you will need Admin access):
Logs
Integrations
Removed my derivedData directory
Restarted everything and rebuilt the bots using different names for them.
I had the same problem once. I think it happened after updating Xcode. Only solution was to reinstall OS X. After that I have not had any problems. I tried everything I could find from the web but there weren't any solutions out. I tried to delete everything that belongs to Xcode but I think I didn't find all of them. So my suggestion is to reinstall OS X. Copy all your important stuff to external hard drive or to cloud.
I know this is not the suggestion or answer you are looking for but it helps you out.
When I try to test my iOS app the Xcode 7 test navigator shows (null) the second time I run my tests.
The first time it looks normal:
However, as I run the tests again the 12 tests turn into a single test named (null) and it feels like the test cases aren't really run anymore, they just succeed every time after 1 millisecond.
I'm using Kiwi for the tests, but it feels more like something going wrong in Xcode7. I don't remember having this problem in Xcode6. The only thing that consistently solves the problem seems to be an Xcode reboot.
Has anyone had this issue as well?
I have just experienced the same issue. Commenting out the test class name so the test would not build and then putting the test class name back fixed it for me.
I am currently attempting to port a game I've developed in the Wintermute Lite engine to iOS platforms. My game will compile just fine in XCode (albeit using the armv6 architecture) and will run perfectly on the iOS simulator; however, when I try to deploy it to an iPad, the first thread will halt in XCode with the error "EXC_BAD_ACCESS (code=1, adress=0xfffffff6)", pointing to a non-specific line of assembly code.
First of all, if you guys have any ideas right off the bat as to what might be causing this, I would greatly appreciate some help. The thing is, I'm more than willing to debug this myself, but being a complete noob with Objective-C as well as XCode, I'm not sure how to trace this specific error back to the line of code that's causing it (I apologize if this is a really basic question but I've already attempted to find a command to get the line of code associated with the error, but with no success).
I realize that this is scant on details, but as I said, I'm not sure how to pinpoint the piece of code that's causing this error using XCode, otherwise I'd just debug this myself. If there's any extra information I can provide, let me know.
Thanks in advance for any help!
I got it working. After a lot of messing around with XCode, I realized that I incorrectly configured the project file provided by Wintermute. As far as I can tell, it had something to do with the fact that the project was originally set to build for "iOS Universal" and I changed it to "iPad 5.0," which somehow caused the project to break upon deployment.
Anyway, I started over with a new XCode project file and got it to compile perfectly! Sorry for the bother.
The problem is the fact that it isnt ment to run on iOS. The reason it runs on he simulator is that it is building for a Intel chip set, not ARM. Even though you set it to armv6 it doesn't mean that the code will run on a non-intel device.