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
CocoaPods tests rely on being online #1477
Comments
👍 |
Issue has been confirmed by @segiddins |
@segiddins know if this is still legit? |
This issue is still valid, it's only a single test which requires internet use. "validates a podspec with dependencies" from
|
Yeah I did some work for it... however iirc correctly also some integration tests present an issue with a repo which was not easy to solve. |
I think now it's only the integration specs. We could definitely fix that in a super hack way (by injecting a 'hack' ruby file to override sources so we can use submodules or a tarball), but I'm not sure if thats worth it. Thoughts, @mrackwitz ? |
Would be nice to have, but it's for me still not top priority. Also I think it's good that we test the actual download code paths. |
👍 |
👎 I've worked on a slow connection on a couple projects which have tests like this, and it's maddening. Please reconsider this, especially if it's just one or two tests which require network access. Having an Not all developers have always-on, super-fast, unmetered wifi connections. Please consider ways to make the project easy and accessible for them. |
It's only the integration specs that have a net dependency, and they're specifically testing things that use the network. The unit and functional specs should all work offline. We'd welcome a PR making the integration specs work offline, but it's just not worth the effort for us at the moment. |
Reference tweet " Honestly, the main issue I’ve run into with contributing is the dev setup. Tests have odd dependencies, require net access "
The text was updated successfully, but these errors were encountered: