|
Name |
|
Date |
Size |
#Lines |
LOC |
| .. | | - | - |
| artifacts/ | H | 25-Apr-2025 | - | 1,904 | 1,326 |
| build_stats/ | H | 25-Apr-2025 | - | 107 | 105 |
| dockerize/ | H | 25-Apr-2025 | - | 418 | 232 |
| generated/ | H | 25-Apr-2025 | - | 13,483 | 13,477 |
| helper_scripts/ | H | 25-Apr-2025 | - | 1,014 | 475 |
| interop/ | H | 25-Apr-2025 | - | 244 | 196 |
| lb_interop_tests/ | H | 25-Apr-2025 | - | 375 | 313 |
| performance/ | H | 25-Apr-2025 | - | 7,987 | 6,589 |
| python_utils/ | H | 25-Apr-2025 | - | 2,954 | 2,350 |
| sanity/ | H | 25-Apr-2025 | - | 1,632 | 1,028 |
| xds_k8s_test_driver/ | H | 25-Apr-2025 | - | 4 | 2 |
| README.md | H A D | 25-Apr-2025 | 2.2 KiB | 47 | 28 |
| run_grpclb_interop_tests.py | H A D | 25-Apr-2025 | 22.6 KiB | 699 | 578 |
| run_interop_tests.py | H A D | 25-Apr-2025 | 57.7 KiB | 1,868 | 1,528 |
| run_microbenchmark.py | H A D | 25-Apr-2025 | 4.1 KiB | 169 | 125 |
| run_performance_tests.py | H A D | 25-Apr-2025 | 28.2 KiB | 844 | 716 |
| run_tests.py | H A D | 25-Apr-2025 | 63.6 KiB | 1,922 | 1,604 |
| run_tests_matrix.py | H A D | 25-Apr-2025 | 20.3 KiB | 659 | 553 |
| run_xds_tests.py | H A D | 25-Apr-2025 | 155.4 KiB | 4,334 | 3,855 |
| start_port_server.py | H A D | 25-Apr-2025 | 1,000 | 30 | 10 |
| task_runner.py | H A D | 25-Apr-2025 | 4.4 KiB | 151 | 114 |
README.md
1# Overview
2
3This directory contains scripts that facilitate building and running tests. We are using python scripts as entrypoint for our
4tests because that gives us the opportunity to run tests using the same commandline regardless of the platform you are using.
5
6# Unit tests (run_tests.py)
7
8Builds gRPC in given language and runs unit tests. Use `tools/run_tests/run_tests.py --help` for more help.
9
10###### Example
11`tools/run_tests/run_tests.py -l python -c dbg`
12
13###### Useful options (among many others)
14- `--use_docker` Builds a docker container containing all the prerequisites for given language and runs the tests under that container.
15- `--build_only` Only build, do not run the tests.
16
17Note: 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.
18
19Note: some tests may be flaky. Check the "Issues" tab for known flakes and other issues.
20
21The full suite of unit tests will take many minutes to run.
22
23# Interop tests (run_interop_tests.py)
24
25Runs tests for cross-platform/cross-language interoperability. For more details, see [Interop tests descriptions](/doc/interop-test-descriptions.md)
26The 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.
27
28###### Example
29`tools/run_tests/run_interop_tests.py -l python -s c++ --use_docker` (run interop tests with C# client and C++ server)
30
31Note: if you see an error like `no space left on device` when running the
32interop tests using Docker, make sure that Docker is building the image files in
33a location with sufficient disk space.
34
35# Performance benchmarks (run_performance_tests.py)
36
37The `run_performance_tests.py` script is deprecated.
38See [end-to-end benchmarking documentation](/tools/run_tests/peformance/README.md) for more info.
39
40# Artifacts & Packages (task_runner.py)
41
42A generalized framework for running predefined tasks based on their labels. We use this to building binary artifacts & distrib packages and testing them)
43
44###### Example
45`tools/run_tests/task_runner.py -f python artifact linux x64` (build tasks with labels `python`, `artifact`, `linux`, and `x64`)
46
47