Skip to content

E2E Framework Overhaul #65

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
Closed
davidz627 opened this issue Jul 11, 2018 · 1 comment
Closed

E2E Framework Overhaul #65

davidz627 opened this issue Jul 11, 2018 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/test Categorizes issue or PR as related to testing

Comments

@davidz627
Copy link
Contributor

E2E Framework should actually run locally, we can create instances (possibly multizonal) that run the driver binary that actually exposes their endpoint as an SSL secured TCP endpoint:
https://grpc.io/docs/guides/auth.html#examples

This way the e2e tests can actually spin these instances up, and spin up a grpc client that we use to call these instances for the tests.

This makes the multi-zonal tests easier to create and makes it so that we dont have to stream test commands and results back and forth between the instances
@davidz627 davidz627 added kind/feature Categorizes issue or PR as related to a new feature. kind/test Categorizes issue or PR as related to testing labels Jul 11, 2018
@davidz627
Copy link
Contributor Author

Fixed by #71

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/test Categorizes issue or PR as related to testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@davidz627