aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/ruby/end2end
diff options
context:
space:
mode:
authorGravatar Alexander Polcyn <apolcyn@google.com>2017-03-15 16:07:03 -0700
committerGravatar Alexander Polcyn <apolcyn@google.com>2017-03-15 16:07:03 -0700
commit4109c23734d572cc19cd7e54571757c854db27f7 (patch)
tree2f53747e4053119061f0a5b95c001007dc604aec /src/ruby/end2end
parent563ec5324f60b8ea521b41a1a440735b8bf6d2a6 (diff)
add a README for new test directory
Diffstat (limited to 'src/ruby/end2end')
-rw-r--r--src/ruby/end2end/README18
1 files changed, 18 insertions, 0 deletions
diff --git a/src/ruby/end2end/README b/src/ruby/end2end/README
new file mode 100644
index 0000000000..f0dc14fe9b
--- /dev/null
+++ b/src/ruby/end2end/README
@@ -0,0 +1,18 @@
+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).