Skip to content

Files

Latest commit

ctillerctiller
Actually turn on the test
Nov 10, 2017
d2ff02d · Nov 10, 2017

History

History
This branch is 27546 commits behind grpc/grpc:master.

run_tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
artifacts
artifacts
Oct 25, 2017
build_stats
build_stats
Dec 22, 2016
dockerize
dockerize
Oct 26, 2017
generated
generated
Nov 8, 2017
helper_scripts
helper_scripts
Nov 6, 2017
interop
interop
Jun 30, 2017
performance
performance
Oct 26, 2017
python_utils
python_utils
Oct 25, 2017
sanity
sanity
Nov 10, 2017
README.md
README.md
May 5, 2017
run_build_statistics.py
run_build_statistics.py
Aug 11, 2017
run_interop_tests.py
run_interop_tests.py
Oct 17, 2017
run_microbenchmark.py
run_microbenchmark.py
Aug 29, 2017
run_performance_tests.py
run_performance_tests.py
Sep 12, 2017
run_tests.py
run_tests.py
Nov 3, 2017
run_tests_matrix.py
run_tests_matrix.py
Oct 25, 2017
start_port_server.py
start_port_server.py
Jun 8, 2017
task_runner.py
task_runner.py
Jun 8, 2017

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.

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.

Stress tests (run_stress_tests.py)

Runs modified interop tests clients and servers under heavy load for an extended period of time to discover potential stability issues. The tests are internally using Kubernetes to run the client and server on GKE and upload statistics to BigQuery.

tools/run_tests/stress_test/run_on_gke.py --gcp_project_id=<google-cloud-platform-project-id> --config_file=<path-to-config-file>

The directory tools/run_tests/stress_test/configs/ contains the config files for several scenarios

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)