Hi, I'm working with Justin Burke on adding support for server SSL certificate reloading [1].
The implementation (C-core and Python bindings) is going through review. In the mean time, I'd like to add an "end-to-end" test that tests Python bindings and C-core by doing: 1. creates one server and two clients, that will talk some basic RPC, e.g., "hello world" or "ping" 2. clientA establishes a long-lived channel before the server switches certificates; the channel should work (i.e., successfully performs RPCs) before and after the server's switch 3. clientB establishes 3 short-lived channels: one before the server's switch, which succeeds; one after that, that fails certificate verification; and then one that succeeds once clientB itself switches over to new CA to verify the server's new certificate. I have such a "test" [2], but it's not hooked up with gRPC's (automated) test suites. So I'm looking for guidance on how best to proceed (Justin is new to that part of the code and is not familiar), e.g., - should I add to somewhere under `src/python/grpcio_tests/tests`? - is `tools/run_tests/run_tests.py -l python [--compiler ...]` the right way to run the tests? I'm looking around to try to find out on my own, but any help appreciated! Thanks! [1] https://github.com/grpc/grpc/issues/10528 [2] https://github.com/cauthu/grpc/tree/master/test/core/security/server_credentials_reloading -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/0da67b37-336b-4529-b26e-26b8a75985ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
