-
Notifications
You must be signed in to change notification settings - Fork 817
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
SDK conformance harness #672
Comments
As I understand we should generate single GRPC/RestAPI client which would be calling SDK implementations one by one (each with unique hostnames). |
I made a draft proposal on how the system of SDK harness tests could look like: |
Added a bunch of notes - PTAL |
I found an absence of new |
Can we close this now? We have the harness after all. |
Yes, we can close this PR now. |
Closing! |
A way for developers who want to develop / bring their own SDK to know that their SDK implementation is compliant with what we need it to do.
Ideally, I think it would not involve a full Kubernetes install, or e2e test, but likely could be run on it's own - maybe as a binary / docker container? Something simple.
We could then integrate this into our CI system to run against existing SDKs, and ensure that they always pass. Right now, this could fail for anything other than our Go sdk.
Would need to have a way to skip tests as well - since we often have SDKs that are partial implementations.
Open to suggestions on what this should look like?
The text was updated successfully, but these errors were encountered: