Chiebot-Mirror
/
grpc
mirror of https://github.com/grpc/grpc.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#) https://grpc.io/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
29997 Commits
274 Branches
377 Tags
1.2 GiB
 
 
 
 
 
 
Tag: Branch: Tree: 174e02ae3e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '174e02ae3e'
${ noResults }
grpc/test/cpp/naming
Yash Tibrewal 8cf1470a51
Revert "Revert "All instances of exec_ctx being passed around in src/core removed"" 		7 years ago
..
BUILD Add tests for c-ares wrapper using a local DNS server. 7 years ago
README.md Query for TXT service configs with _gprc_config prefix 7 years ago
create_private_dns_zone.sh Query for TXT service configs with _gprc_config prefix 7 years ago
gen_build_yaml.py Add c-ares resolver tests against GCE DNS, using the unit test. 7 years ago
generate_resolver_component_tests.bzl Add tests for c-ares wrapper using a local DNS server. 7 years ago
private_dns_zone_init.sh Query for TXT service configs with _gprc_config prefix 7 years ago
resolver_component_test.cc Revert "Revert "All instances of exec_ctx being passed around in src/core removed"" 7 years ago
resolver_component_tests_runner.sh Query for TXT service configs with _gprc_config prefix 7 years ago
resolver_component_tests_runner_invoker.cc Enable clang-tidy as a sanity check, fix up all known failures 7 years ago
resolver_gce_integration_tests_runner.sh Query for TXT service configs with _gprc_config prefix 7 years ago
resolver_test_record_groups.yaml Query for TXT service configs with _gprc_config prefix 7 years ago
test_dns_server.py Add c-ares resolver tests against GCE DNS, using the unit test. 7 years ago

README.md

Resolver Tests

This directory has tests and infrastructure for unit tests and GCE integration tests of gRPC resolver functionality.

There are two different tests here:

Resolver unit tests (resolver "component" tests)

These tests run per-change, along with the rest of the grpc unit tests. They query a local testing DNS server.

GCE integration tests

These tests use the same test binary and the same test records as the unit tests, but they run against GCE DNS (this is done by running the test on a GCE instance and not specifying an authority in uris). These tests run in a background job, which needs to be actively monitored.

Making changes to test records

After making a change to resolver_test_record_groups.yaml:

  1. Increment the "version number" in the resolver_tests_common_zone_name DNS zone (this is a yaml field at the top of resolver_test_record_groups.yaml).

  2. Regenerate projects.

  3. From the repo root, run:

$ test/cpp/naming/create_private_dns_zone.sh
$ test/cpp/naming/private_dns_zone_init.sh

Note that these commands must be ran in environment that has access to the grpc-testing GCE project.

If everything runs smoothly, then once the change is merged, the GCE DNS integration testing job will transition to the new records and continue passing.