Home | History | Annotate | only in /external/grpc-grpc/tools/run_tests
Up to higher level directory
NameDateSize
artifacts/22-Oct-2020
build_stats/22-Oct-2020
dockerize/22-Oct-2020
generated/22-Oct-2020
helper_scripts/22-Oct-2020
interop/22-Oct-2020
performance/22-Oct-2020
python_utils/22-Oct-2020
README.md22-Oct-20202.5K
run_build_statistics.py22-Oct-202010.3K
run_interop_tests.py22-Oct-202050.9K
run_microbenchmark.py22-Oct-20208.9K
run_performance_tests.py22-Oct-202027.1K
run_tests.py22-Oct-202064.7K
run_tests_matrix.py22-Oct-202019.9K
sanity/22-Oct-2020
start_port_server.py22-Oct-20201,002
task_runner.py22-Oct-20203.8K

README.md

      1 # Overview
      2 
      3 This directory contains scripts that facilitate building and running tests. We are using python scripts as entrypoint for our
      4 tests 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 
      8 Builds 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 csharp -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 
     17 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. 
     18 
     19 Note: some tests may be flaky. Check the "Issues" tab for known flakes and other issues.
     20 
     21 The full suite of unit tests will take many minutes to run.
     22 
     23 # Interop tests (run_interop_tests.py)
     24 
     25 Runs tests for cross-platform/cross-language interoperability. For more details, see [Interop tests descriptions](/doc/interop-test-descriptions.md)
     26 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.
     27 
     28 ###### Example
     29 `tools/run_tests/run_interop_tests.py -l csharp -s c++ --use_docker` (run interop tests with C# client and C++ server)
     30 
     31 Note: if you see an error like `no space left on device` when running the
     32 interop tests using Docker, make sure that Docker is building the image files in
     33 a location with sufficient disk space.
     34 
     35 # Performance benchmarks (run_performance_tests.py)
     36 
     37 Runs predefined benchmark scenarios for given languages. Besides the simple configuration of running all the scenarios locally,
     38 the script also supports orchestrating test runs with client and server running on different machines and uploading the results
     39 to BigQuery.
     40 
     41 ###### Example
     42 `tools/run_tests/run_performance_tests.py -l c++ node`
     43 
     44 ###### Useful options
     45 - `--regex` use regex to select particular scenarios to run.
     46 
     47 # Artifacts & Packages (task_runner.py)
     48 
     49 A generalized framework for running predefined tasks based on their labels. We use this to building binary artifacts & distrib packages and testing them)
     50 
     51 ###### Example
     52 `tools/run_tests/task_runner.py -f python artifact linux x64` (build tasks with labels `python`, `artifact`, `linux`, and `x64`)
     53 
     54