What's changed: Created Professional Cloud Developer Chapter 3 (Domain 2 "Build and test": dev environment = CLI emulators/unit tests, Cloud Shell/Cloud Workstations, Cloud Code, Gemini Code/Cloud Assist; build and test = Cloud Build/Artifact Registry, Binary Authorization (provenance), CI automation of unit/integration tests).
3.2Building and testing (CI)
Understand building containers from source with Cloud Build, storing them in Artifact Registry, ensuring provenance with Binary Authorization, automating unit/integration tests, and continuous validation in CI pipelines.
Turn source into artifacts safely and repeatably, and ensure quality with tests. CI (continuous integration) is core to development.
3.2.1Building and storing artifacts
Cloud Build builds container images from source and stores them in Artifact Registry (a container/package registry). For supply-chain safety, configure signing/verification (provenance) with Binary Authorization, allowing only trusted artifacts to deploy. Map "build from source = Cloud Build," "store artifacts = Artifact Registry," "provenance = Binary Authorization."
3.2.2Automating tests
Test in stages: unit tests validate individual functions/classes (fast, locally or via emulators), and integration tests validate cross-component behavior (run automatically as Cloud Build steps). Embed these in a CI pipeline to validate every change automatically, catching defects early and safely. AI coding assistants can help write tests. Map "auto-validate every change = embed in CI" and "validate integration = integration tests."
Common: requirement → means. E.g., "build containers from source" = Cloud Build; "store built images" = Artifact Registry; "deploy only trusted artifacts" = Binary Authorization (provenance); "auto-run integration tests on each change" = Cloud Build steps (CI).
Watch the mix-ups: (1) Cloud Build (build/CI) and Artifact Registry (storage) have different roles. (2) Do not confuse unit tests (in isolation) and integration tests (cross-component). (3) Binary Authorization is deploy-time trust verification, not the build itself.
3.2.3Section summary
- Cloud Build builds from source; Artifact Registry stores artifacts
- Binary Authorization ensures provenance; deploy only trusted artifacts
- Embed unit/integration tests in CI (Cloud Build) to auto-validate each change
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. Which CI service builds container images from source?
Q2. Which registry stores built container images and packages?
Q3. To ensure artifact provenance at deploy time and allow only trusted ones, what do you use?
Q4. To auto-validate cross-component behavior on each change, which best fits?
Q5. Which correctly contrasts unit and integration tests?
Q6. Which correctly contrasts Cloud Build and Artifact Registry?