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
[WIP] Parallel device testing support #317
base: master
Are you sure you want to change the base?
[WIP] Parallel device testing support #317
Conversation
…testing-support-rebased
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.
Some files could not be reviewed due to errors:
.rubocop.yml: Lint/DefEndAlignment has the wrong namespace - should be Layout
.rubocop.yml: Lint/DefEndAlignment has the wrong namespace - should be Layout .rubocop.yml: Lint/EndAlignment has the wrong namespace - should be Layout .rubocop.yml: Lint/Eval has the wrong namespace - should be Security .rubocop.yml: Style/AlignHash has the wrong namespace - should be Layout .rubocop.yml: Style/AlignParameters has the wrong namespace - should be Layout .rubocop.yml: Style/CaseIndentation has the wrong namespace - should be Layout .rubocop.yml: Style/ClosingParenthesisIndentation has the wrong namespace - should be Layout .rubocop.yml: Style/CommentIndentation has the wrong namespace - should be Layout .rubocop.yml: Style/EmptyLineBetweenDefs has the wrong namespace - should be Layout .rubocop.yml: Style/EmptyLines has the wrong namespace - should be Layout .rubocop.yml: Style/EmptyLinesAroundBlockBody has the wrong namespace - should be Layout .rubocop.yml: Style/EmptyLinesAroundClassBody has the wrong namespace - should be Layout .rubocop.yml: Style/EmptyLinesAroundModuleBody has the wrong namespace - should be Layout .rubocop.yml: Style/ExtraSpacing has the wrong namespace - should be Layout .rubocop.yml: Style/FirstParameterIndentation has the wrong namespace - should be Layout .rubocop.yml: Style/IndentationWidth has the wrong namespace - should be Layout .rubocop.yml: Style/LeadingCommentSpace has the wrong namespace - should be Layout .rubocop.yml: Style/MultilineOperationIndentation has the wrong namespace - should be Layout .rubocop.yml: Style/SpaceAfterComma has the wrong namespace - should be Layout .rubocop.yml: Style/SpaceAroundEqualsInParameterDefault has the wrong namespace - should be Layout .rubocop.yml: Style/SpaceAroundOperators has the wrong namespace - should be Layout .rubocop.yml: Style/SpaceInsideBlockBraces has the wrong namespace - should be Layout .rubocop.yml: Style/SpaceInsideHashLiteralBraces has the wrong namespace - should be Layout .rubocop.yml: Style/SpaceInsideParens has the wrong namespace - should be Layout .rubocop.yml: Style/TrailingBlankLines has the wrong namespace - should be Layout .rubocop.yml: Style/TrailingWhitespace has the wrong namespace - should be Layout Error: The `Style/TrailingComma` cop no longer exists. Please use `Style/TrailingCommaInArguments`, `Style/TrailingCommaInArrayLiteral`, and/or `Style/TrailingCommaInHashLiteral` instead. (obsolete configuration found in .rubocop.yml, please update it)
Another issue I found is that when xcodebuild is run with multiple destinations with |
Any update on this? |
@thii Nope! Feel free to finish it up. I've since switched over to using |
@chrisballinger Thanks. I ended up porting |
@thii Hahaha awesome, that's the spirit! |
@chrisballinger / @thii I'm assuming you're not using xcpretty through fastlane then? Since xcpretty seems to be stalled on fixing this, and since fastlane uses xcpretty, using alternatives like xcbeautify and XCTestHTMLReport don't seem to be an option if using fastlane's scan function to run our parallel tests |
@ecerney Yeah you would have to use xcodebuild directly. |
Resolves #295.
Since it looks like progress on #299 has stalled, I'm opening up a new PR based on the original that contains additional fixes from the technology-ebay-de fork, as well as some fixes of my own. Unfortunately after merging the latest upstream/master the cucumber tests no longer pass, with the following error:
I believe this is caused by the recent change in 87dd9f8. I'm not very familiar with how cucumber tests work, so any help there would be appreciated. Perhaps it has something to do with how parallel test output appears as Swift instead of ObjC?
TODO:
rake spec
passesrake lint
passesrake cucumber
fails:Scenario: Showing tests with one having a swift fatal error
-disable-concurrent-testing
is enabled