Test and build
Test
go test ./...Tests boot the app with test settings and a database of their own
(SQLite in memory, or .env.testing’s), and send requests to it like
a browser, through anetostest:
// illustrative
func TestHome(t *testing.T) {
app := anetostest.New(t, setup)
app.Get("/").AssertOK().AssertSee("Welcome")
}Each test runs in a transaction that is rolled back, so tests don’t see
each other’s rows. make:crud and make:auth wrote tests for their
pages; add one for each page and form you write. Test your
app shows forms, logged-in users, emails and
queue jobs.
go tool anetos check runs it all before you call a change done: the
generators, the frontend’s build (with a frontend/), go build,
go vet, the tests, doctor and the security check’s basic rules.
Build
go tool anetos build # bin/blog
./bin/blog migrate
./bin/blog # the web server, the queue's workers and the scheduleranetos build compiles the views and the models’ columns (and, with a
frontend/, writes its TypeScript types and builds it, with Node.js),
then builds one static binary that holds the migrations, the views and the files
of public/ and locales/. A server needs only the binary and its
settings (the environment, or a file: deploy/production.env.example
lists them).
Deploy runs it on a server with systemd or
in a container (the project has a Dockerfile), and Deploy to a cloud
platform on Cloud Run, Azure Container
Apps, ECS, DigitalOcean, Kubernetes, Fly.io or Render.
Before going live, run ./bin/blog doctor with the production
settings: it reports unsafe ones (SESSION_SECURE=false, a database
reached without TLS, the log mail driver…) and migrations that haven’t
run. See Secure your app.
Next: the tutorial builds a whole app, step by step.