tree: 9965b540443ba8c7368362e6c839d0cc9c73ef66 [path history] [tgz]
  1. testdata/
  2. app.yaml
  3. cloudbuild.yaml
  4. csp.go
  5. godev.go
  6. googlecn.go
  8. server.go
  9. server_test.go


Local Development

For local development, simply build and run. It serves on localhost:6060. You can specify the domain name as the first path element, such as http://localhost:6060/

go run .


The and web sites have a suite of regression tests that can be run with:

go test

Test cases that check for expected URLs, content, response codes and so on are encoded in *.txt files in the testdata directory. If there is a problem that no existing test caught, it can be a good idea to add a new test case to avoid repeat regressions.

These tests can be run locally, via TryBots, and they are also run when new versions are being deployed. The testdata/live.txt file is special and used only when testing a live server, because its test cases depend on production resources.


The web site has a suite of visual checks that can be run with:

go run ./cmd/screentest

These checks can be run locally and will generate visual diffs of web pages from the set of testcases in cmd/screentest/godev.txt, comparing screenshots of the live server and a locally running instance of cmd/golangorg.

Deploying to and

Each time a CL is reviewed and submitted, the site is automatically deployed to App Engine. If it passes its serving-readiness checks, it will be automatically promoted to handle traffic. Whether it passes or not, the new deployment can be found in the App Engine versions list.

If the automatic deployment is not working, or to check on the status of a pending deployment, see the “website-redeploy-golang-org” trigger in the Cloud Build console.