Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Xcode test navigator integration #1

Closed
modocache opened this issue Jun 5, 2014 · 3 comments
Closed

Xcode test navigator integration #1

modocache opened this issue Jun 5, 2014 · 3 comments
Labels
bug

Comments

@modocache
Copy link
Member

Currently tests do not appear correctly in Xcode's test navigator.
@modocache
Copy link
Member Author

Turns out Specta has same issue: specta/specta#83

@modocache modocache mentioned this issue Jun 8, 2014
Closed
@modocache
Copy link
Member Author

Specta works on Xcode 5 and prior, but I'm not sure why. I believe XCTest used to infer the name of the test case by taking -[XCTestCase name], removing the name of the XCTestCase subclass, stripping any characters not allowed in method names, and then using what was left.

In Xcode 6, it appears to use NSStringFromSelector() on the selector of the current test cases's NSInvocation. This makes a lot of sense from Apple's point of view, but it makes things difficult for Specta and Quick. Quick calls the same selector multiple times---[XCTestCase runExampleAtIndex:]--with different parameters.

Maybe I can get around this by defining appropriately named methods at runtime.

modocache added a commit that referenced this issue Jun 9, 2014
@modocache
Quick is the 1st BDD framework to support Xcode 6
606d77a 
This fixes issue #1: Xcode test navigator integration.

As of Xcode 6, each test invocation's selector is used to determine the
name displayed in the test navigator. Specta and Quick both used the
same instance method (`-[QuickSpec runExampleAtIndex:]`, in Quick's
case) to run each example. As a result, all tests in the same spec had
the same name, causing each example to "overwrite" each previous one in
the navigator. This caused several issues, including red lines to
indicate test failure in Xcode suddenly disappearing when the next
example finished running.

During `+[QuickSpec testInvocations]`, define a new instance method for
each example. Then, return an invocation that executes that new instance
method
@modocache
Copy link
Member Author

@modocache modocache mentioned this issue Jun 9, 2014
Closed
modocache pushed a commit that referenced this issue Jun 27, 2014
@bryanenders
Merge pull request #1 from modocache/master
5b9e635 
Brought fork up to date
@sharplet sharplet mentioned this issue Jun 28, 2014
Closed
@sharplet sharplet mentioned this issue Jul 12, 2014
Merged
@modocache modocache mentioned this issue Aug 14, 2014
Merged
@TomasLinhart TomasLinhart mentioned this issue Sep 4, 2014
Closed
@modocache modocache mentioned this issue Sep 5, 2014
Closed
@arvindraghavan arvindraghavan mentioned this issue Oct 3, 2014
Closed
@esetnik esetnik mentioned this issue Oct 28, 2015
Closed
@mikeyme123 mikeyme123 mentioned this issue Apr 1, 2016
Closed
NachoSoto pushed a commit to NachoSoto/Quick that referenced this issue Jul 5, 2016
@norio-nomura
Merge pull request Quick#1 from liscio/cl-swift-3-compatibility
43ef41a 
Get the unit tests building & passing for macOS and iOS targets
NachoSoto pushed a commit to NachoSoto/Quick that referenced this issue Jul 18, 2016
@jeffh
Made lazy property test more explicit. Closes Quick#1
e4b6aad
NachoSoto pushed a commit to NachoSoto/Quick that referenced this issue Jul 18, 2016
@robrix
Merge pull request Quick#1 from github/restrict-osx-valid-arches
5cb5827 
Only allow x86_64 for OS X builds
karagraysen pushed a commit that referenced this issue Aug 27, 2016
@LinShiwei
Merge pull request #1 from Quick/master
d784427 
Update from origin
@bupojung bupojung mentioned this issue Aug 9, 2019
Closed
@sandeepkumarrepo sandeepkumarrepo mentioned this issue May 27, 2024
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@modocache