#APPCODE SUPPORT FOR XCODE 9.4 CODE#

#APPCODE SUPPORT FOR XCODE 9.4 CODE#

Looking just at the Quick code project, if I open FunctionalTests_SharedExamplesTests_SharedExamples, I can cmd-click on Configuration and navigate ok, while QuickConfiguration can't be found. Yet, if I do the same for AlamoFire, another Cocoapod integrated framework, it works fine. When I'm editing one of my tests and attempt to navigate to QuickSpec, it says it can't find it. One thing that is probably a complicating factor for Quick and why it doesn't just work is that Quick is a mixed language framework and (I think) the main class that they'd need to understand, QuickSpec, is implemented in Obj-C. So if you wanted to see how they handle code in general, I think you could learn a bunch from the OS versions. One thing to point out is that though AppCode seems to be closed source only, JetBrains open sources a LOT of their stuff and there are open source, community editions of a number of their tools. It's why you can do tons of refactoring for Swift today while XCode still doesn't do any.ДЄs such, they're building up the code model to work from themselves and they're still not quite there. I'm not sure if you've used AppCode or other JetBrains tools much, but they do a phenomenal job of understanding and manipulating code. While I haven't used it recently, I just checked how well Specta works using one of my old projects and it seems to work fine. Not sure when this happened as my old test configs work fine. So it seems like AppCode has some serious testing issues. What I get is that all of my Quick based tests run. You should be able to run those by switching to use that.ДЇinal note: I cannot for the life of me get the XCTest based file to run in AppCode, even after creating a custom Run config that targets that class and the single testExample() function it contains. Create a custom Run/Debug configuration for your tests. However, I don't run my tests via the right click method and this may work for you. Your apps code-signing identity sets the certificate that uniquely identifies you.

So it seems like there are a variety of bugs re: Unit Testing and they're not just about Quick. The previous two chapters took advantage of Xcodes automatic code. However, if I attempt actually run the tests from right clicking on the XCTest file, what actually runs are the Quick based ones! If I right click on the XCTest file, I see the run commands as per your first image, while I don't when I do the same for the Quick based ones. I created a new XCTest file in my project which has all other tests based on Quick. It seems like the testing support is even a bit more broken than what you're seeing though. I'm seeing the same thing with AppCode 3.3.1 (just came out today) and XCode 7.0.

Appcode support for xcode 9.4