The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/

History

Jan Tattermusch 5c35dbed93 run tests using the correct runtime for C# (#29302 )		3 years ago
..
artifacts	Try fix csharp macos distribtests (#29156 )	3 years ago
build_stats	…
dockerize	Run bloat_diff.py in a separate kokoro job (#28892 )	3 years ago
generated	HTTP Proxy: Ignore empty entry in no_proxy list (#29217 )	3 years ago
helper_scripts	Remove epollex poller (#29160 )	3 years ago
interop	…
lb_interop_tests	Migrate Infrastructure Scripts to Python 3 (#27135 )	3 years ago
performance	Big query upload (#29197 )	3 years ago
python_utils	Switch .py shebang to python3 (#28963 )	3 years ago
sanity	Upgrading envoyproxy/data-plane-api (#29264 )	3 years ago
xds_k8s_test_driver	[PSM interop] Change restart policy to Never (#29236 )	3 years ago
README.md	…
run_grpclb_interop_tests.py	Switch .py shebang to python3 (#28963 )	3 years ago
run_interop_tests.py	Use a non-root user in Node interop docker images (#29062 )	3 years ago
run_microbenchmark.py	More run_microbenchmark.py cleanup (#28893 )	3 years ago
run_performance_tests.py	Switch .py shebang to python3 (#28963 )	3 years ago
run_tests.py	run tests using the correct runtime for C# (#29302 )	3 years ago
run_tests_matrix.py	Add dockerized ARM64 tests (bazel C/C++, C#, PHP, ruby, python) (#28966 )	3 years ago
run_xds_tests.py	switch run_xds_tests.py shebang to python3 (#28964 )	3 years ago
start_port_server.py	…
task_runner.py	Switch .py shebang to python3 (#28963 )	3 years ago

README.md

Overview

This directory contains scripts that facilitate building and running tests. We are using python scripts as entrypoint for our tests because that gives us the opportunity to run tests using the same commandline regardless of the platform you are using.

Unit tests (run_tests.py)

Builds gRPC in given language and runs unit tests. Use tools/run_tests/run_tests.py --help for more help.

Example

tools/run_tests/run_tests.py -l csharp -c dbg

Useful options (among many others)

--use_docker Builds a docker container containing all the prerequisites for given language and runs the tests under that container.
--build_only Only build, do not run the tests.

Note: If you get an error such as ImportError: No module named httplib2, then you may be missing some Python modules. Install the module listed in the error and try again.

Note: some tests may be flaky. Check the "Issues" tab for known flakes and other issues.

The full suite of unit tests will take many minutes to run.

Interop tests (run_interop_tests.py)

Runs tests for cross-platform/cross-language interoperability. For more details, see Interop tests descriptions The script is also capable of running interop tests for grpc-java and grpc-go, using sources checked out alongside the ones of the grpc repository.

Example

tools/run_tests/run_interop_tests.py -l csharp -s c++ --use_docker (run interop tests with C# client and C++ server)

Note: if you see an error like no space left on device when running the interop tests using Docker, make sure that Docker is building the image files in a location with sufficient disk space.

Performance benchmarks (run_performance_tests.py)

Runs predefined benchmark scenarios for given languages. Besides the simple configuration of running all the scenarios locally, the script also supports orchestrating test runs with client and server running on different machines and uploading the results to BigQuery.

Example

tools/run_tests/run_performance_tests.py -l c++ node

Useful options

--regex use regex to select particular scenarios to run.

Artifacts & Packages (task_runner.py)

A generalized framework for running predefined tasks based on their labels. We use this to building binary artifacts & distrib packages and testing them)

Example

tools/run_tests/task_runner.py -f python artifact linux x64 (build tasks with labels python, artifact, linux, and x64)