3c5e12de08
|
||
|---|---|---|
| .. | ||
| BUILD | ||
| README.md | ||
| create_private_dns_zone.sh | ||
| gen_build_yaml.py | ||
| generate_resolver_component_tests.bzl | ||
| private_dns_zone_init.sh | ||
| resolver_component_test.cc | ||
| resolver_component_tests_runner.sh | ||
| resolver_component_tests_runner_invoker.cc | ||
| resolver_gce_integration_tests_runner.sh | ||
| resolver_test_record_groups.yaml | ||
| test_dns_resolver.py | ||
| test_dns_server.py | ||
| test_tcp_connect.py | ||
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:
-
Increment the "version number" in the
resolver_tests_common_zone_nameDNS zone (this is a yaml field at the top ofresolver_test_record_groups.yaml). -
Regenerate projects.
-
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.