-
Notifications
You must be signed in to change notification settings - Fork 106
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.
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
Improve test target detection in xcodeproj_helper #251
Conversation
Now that we have customizable test target names, we can use that to detect test targets instead of just looking for the suffix "Tests".
@@ -86,11 +90,11 @@ def test_target | |||
end | |||
|
|||
def application_targets | |||
all_targets.reject { |t| t.name.end_with?('Tests') } | |||
all_targets.reject { |t| t.name.end_with?(@test_target_name) } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thoughts on t.name == @test_target_name
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, yeah, that makes more sense
Would you be able to add a test covering this? |
I don't think so. This is so deep in the dumpster fire that is |
If you have ideas on how to test this though, I'm all ears. |
@gfontenot For a test I'd probably stub out the xcode_project method to return a stub of one and then test the 2 methods you modified work as expected. |
that sounds like so much work fine |
carry on. private methods, le sigh. |
Opened #254 to try and fix this |
Now that we have customizable test target names, we can use that to
detect test targets instead of just looking for the suffix "Tests".
Fixes #218 (finally)