Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Explore whether we can use a mock for GCS #2486

Open
droazen opened this issue Mar 20, 2017 · 3 comments
Open

Explore whether we can use a mock for GCS #2486

droazen opened this issue Mar 20, 2017 · 3 comments
Assignees
@jean-philippe-martin
Labels
NIO question QuixoticDream tests

Comments

@droazen
Copy link
Collaborator

droazen commented Mar 20, 2017

Would be very helpful for projects like htsjdk that can't have a direct dependency on google-cloud-java!
@droazen droazen added this to the 4.0 release milestone Mar 20, 2017
@droazen
Copy link
Collaborator Author

droazen commented Mar 20, 2017

For @jean-philippe-martin to explore when he has time (complete wishlist item, no urgency)

@droazen droazen added the NIO label Mar 22, 2017
@jean-philippe-martin
Copy link
Contributor

This corresponds to this gcloud issue:
googleapis/google-cloud-java#684
"Provide an in-memory or local-disk emulator of the storage APIs for testing"

@jean-philippe-martin
Copy link
Contributor

This dream may not be as Quixotic as the labels suggest, after all.

@droazen droazen removed this from the Engine-4.0 milestone Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jean-philippe-martin jean-philippe-martin

Labels
NIO question QuixoticDream tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@droazen @jean-philippe-martin