Closed jgeewax closed 7 years ago
@tseaver What is the issue(s) with system tests?
I'll let @jgeewax weigh in
I don't know of anything particular: I just haven't investigated whether there are "ownership" or "uniqueness" issues involved in creating a zone. As long as the back-end lets us create a zone for example.com
, we should be OK.
Ugh. While trying to write a system test for zone creation:
gcloud.exceptions.BadRequest: 400 The 'example.com.' managed zone is not available to be created. (POST https://www.googleapis.com/dns/v1/projects/<project-id>/managedZones)
Do we have a Googler API owner that can help? Or chat with the gcloud-node
guys?
@jgeewax this is the issue for DNS system tests.
@jgeewax If we can get a domain managed within Cloud DNS (e.g., gcloud-python-testing.com
, and give access to our standard projects[1], I'll get the system tests done.
[1] we need access the same projects as requested for Cloud Search in #1181.
@jgeewax I think you said we had a domain available for system testing? Can you get "the usual suspects" (@dhermes' project, mine, and the gcloud-python-regression-tests
one) set up to manage that domain?
@tseaver Send me an email / ping me on Google Hangouts and we can chat about what already exists for gcloud-python.com
.
At this point, I consider the
gcloud.dns
on master to be "full coverage" of the API. The only remaining work is to add system tests for it (if those are feasible to run from Travis).