-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Isolate tests with external server dependencies #3624
Comments
Totally agree, unit tests should use mock in those areas, since we want to keep test coverage high with basic unit tests. I just run into:
Generally speaking we should replace external deps with pre-built stuff available in testing env (eg. docker images, github repos, etc.) |
I just ran into the following errors:
Git error in asset tests:
|
we can remove the cdnify task |
|
@liggitt are you making progress on this? Doesn't really look like it. Why not squash individual ones as they come up? |
I am not. dockerhub and github are our biggest dependencies, and they are pervasive. |
We've moved some to integration. For now, this is unactionable. |
this is biting us for maintenance releases with dependencies on dockerhub versions that don't exist any more |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/unassign |
Several tests at several layers (unit, integration, test-cmd.sh, etc) have dependencies on external servers like dockerhub, etc. When these servers have issues, they can block the merge queue.
Possible failures (all from #3619):
Our core tests should be able to run with minimal dependencies on external servers. Tests that depend on other servers should be moved to an extended test suite.
The text was updated successfully, but these errors were encountered: