carto/grpc @ cdb41dc0f3e72f955a00a677162af3952af04d83

Alexander Polcyn deeed7f12b don't hold the gil while waiting for bg thread to start		9 年之前
..
lib	f8dc32e9e2 make end2end test ports dynamic and slight refactor	9 年之前
protos	f8dc32e9e2 make end2end test ports dynamic and slight refactor	9 年之前
README.md	071f74f6f1 add copyright header to fix failing sanity tests	9 年之前
channel_closing_client.rb	4e606751db add end2end tests to formatter and adjust to formatter	9 年之前
channel_closing_driver.rb	077f890965 conform test to formatter	9 年之前
channel_state_client.rb	4e606751db add end2end tests to formatter and adjust to formatter	9 年之前
channel_state_driver.rb	077f890965 conform test to formatter	9 年之前
end2end_common.rb	077f890965 conform test to formatter	9 年之前
forking_client_client.rb	4736e01c16 add native grpc class init tests to check that presence of grpc_init calls	9 年之前
forking_client_driver.rb	792c7e3d27 add new test where client forks after require grpc, to test that lib startup	9 年之前
gen_protos.sh	071f74f6f1 add copyright header to fix failing sanity tests	9 年之前
grpc_class_init_client.rb	deeed7f12b don't hold the gil while waiting for bg thread to start	9 年之前
grpc_class_init_driver.rb	4736e01c16 add native grpc class init tests to check that presence of grpc_init calls	9 年之前
killed_client_thread_client.rb	077f890965 conform test to formatter	9 年之前
killed_client_thread_driver.rb	4364ded9b1 wording fix in comments	9 年之前
sig_handling_client.rb	4e606751db add end2end tests to formatter and adjust to formatter	9 年之前
sig_handling_driver.rb	077f890965 conform test to formatter	9 年之前
sig_int_during_channel_watch_client.rb	ea282e9c4c add passing test that kills a process while there are active watch chan state calls	9 年之前
sig_int_during_channel_watch_driver.rb	077f890965 conform test to formatter	9 年之前

This directory contains some grpc-ruby end to end tests.

Each test here involves two files: a "driver" and a "client". For example, the "channel_closing" test involves channel_closing_driver.rb and channel_closing_client.rb.

Typically, the "driver" will start up a simple "echo" server, and then spawn a client. It gives the client the address of the "echo" server as well as an address to listen on for control rpcs. Depending on the test, the client usually starts up a "ClientControl" grpc server for the driver to interact with (the driver can tell the client process to do strange things at different times, depending on the test).

So far these tests are mostly useful for testing process-shutdown related situations, since the client's run in separate processes.

These tests are invoked through the "tools/run_tests/run_tests.py" script (the Rakefile doesn't start these).

README.md