Quick: Quick does not work well with the Xcode 9 test runner
- I have read CONTRIBUTING and have done my best to follow them.
What did you do?
Run all tests (⌘U) from Xcode 9.
What did you expect to happen?
Quick Specs should have a green (for passing) or red (for failing) glyph in the left hand gutter of Xcode’s editor windows, like they did in Xcode 8 and earlier. Ideally, one per it(), describe() and context() block, but I’d take one at the top level spec() as a good start. I should be able to click on these to (re-)run the individual block.
Also, the test navigator does not consistently show the list of specs correctly. Sometimes they’re all there, sometimes they’re not, sometimes they’re there but ghosted. This seems to work well for plain XCTests.
What actually happened instead?
No glyphs are evident. All you get is a red X glyph on a failed test. Test Navigator does not always show a complete and correct list of the available specs.
Environment
List the software versions you’re using:
- Quick: 1.1.0
- Nimble: 7.0.1
- Xcode Version: Version 9.0 (9A235)
- Swift Version: 4.0
Please also mention which package manager you used and its version. Delete the other package managers in this list:
- Carthage: 0.25.0
Note: fit() and fdescribe() are inconvenient stopgap measures at best. I have a nice IDE in front of me and I’d like to use it!
I realize this may be more of an issue of the hooks Xcode makes available for Quick to integrate with and what I want may not be possible right now, but I’d like to have this issue here to link the radar to if this is the case.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 15
- Comments: 15 (2 by maintainers)
This seems to be broken again on Xcode 9.2 (9C40b)
Got the same issue, for me even after running the tests non of the Quick generated tests show up in the navigator.
I managed to get it to be a bit more usable in Xcode 9 by adding a dummy test method to my Quick specs, afterwards I can at least run a specific file which is better than having to run the entire test suite…
The same issue is happening in XCode 11.2. Also, tests aren’t even running