Google Git
Sign in
chromium / external / github.com / grpc / grpc / HEAD / . / src / ruby / end2end
tree: 16910094d564d78d7c53a059cab0a09321e9e15a [path history] [tgz]
  1. lib/
  2. protos/
  3. bad_usage_fork_test.rb
  4. call_credentials_returning_bad_metadata_doesnt_kill_background_thread_test.rb
  5. call_credentials_timeout_test.rb
  6. channel_closing_client.rb
  7. channel_closing_test.rb
  8. channel_state_client.rb
  9. channel_state_test.rb
  10. client_memory_usage_client.rb
  11. client_memory_usage_test.rb
  12. echo_server.rb
  13. end2end_common.rb
  14. errors_load_before_grpc_lib_test.rb
  15. fork_test.rb
  16. fork_test_repro_35489.rb
  17. forking_client_client.rb
  18. forking_client_test.rb
  19. gen_protos.sh
  20. graceful_sig_handling_client.rb
  21. graceful_sig_handling_test.rb
  22. graceful_sig_stop_client.rb
  23. graceful_sig_stop_test.rb
  24. grpc_class_init_client.rb
  25. grpc_class_init_test.rb
  26. killed_client_thread_client.rb
  27. killed_client_thread_test.rb
  28. load_grpc_with_gc_stress_test.rb
  29. logger_load_before_grpc_lib_test.rb
  30. multiple_killed_watching_threads_test.rb
  31. package_with_underscore_test.rb
  32. prefork_postfork_loop_test.rb
  33. prefork_without_using_grpc_test.rb
  34. README.md
  35. secure_fork_test.rb
  36. sig_handling_client.rb
  37. sig_handling_test.rb
  38. sig_int_during_channel_watch_client.rb
  39. sig_int_during_channel_watch_test.rb
  40. simple_fork_test.rb
  41. status_codes_load_before_grpc_lib_test.rb
src/ruby/end2end/README.md

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).