-
Notifications
You must be signed in to change notification settings - Fork 238
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
Tests fail locally, but pass on travis #74
Comments
@orta and @ixnixnixn -- try this out and let me know if it fixes your issue. http://stackoverflow.com/questions/24224193/xcodebuild-test-not-running-xctestcase-unit-test-file/25276814#25276814 |
The problem still persists for me. I think the simulator warning is more minor than the discrepancies that caused the test failures in the local environment. Anyways, I've managed to make #76 pass by adjusting the fixture files. |
What did you adjust in the fixtures to get it working locally? |
Cool! Can we close this out, then? |
Yeah, I'm happy to close this issue. |
I'm currently trying to add functionality to slather to output coverage files as static htmls. I've already added the basic functionality in my branch and currently trying to add tests to cover those up.
Although, I had a problem when running the tests in my local machine. I'm currently running Mac OS X 10.10.3, ruby 2.0.0p481 and Xcode 6.3.1. What I did was:
bundle install
bundle exec rspec
Firstly, I have a warning from iPhone simulator saying that the service could not established. Here is the warning message:
xcodebuild[3176:118116] [MT] iPhoneSimulator: SimVerifier returned: Error Domain=NSPOSIXErrorDomain Code=53 "Simulator verification failed." UserInfo=0x7f91a1d6e280 {NSLocalizedFailureReason=A connection to the simulator verification service could not be established., NSLocalizedRecoverySuggestion=Ensure that Xcode.app is installed on a volume with ownership enabled., NSLocalizedDescription=Simulator verification failed.}
Secondly, I have 3 tests failing, which all related to the fixture
Branches.m
on line 13. It seems that somehow the generated outputs differ from the fixture files. Below are my rspec failures:In contradiction, I pushed the same commit to run it on travis. It works fine. I'd really appreciate it if you guys could shed some light on how to run the tests properly.
Many thanks for this wonderful library! 👍
The text was updated successfully, but these errors were encountered: