Follow-up · depth 1
How would you test Artifact Promotion (Build Once)?
How would you test Artifact Promotion (Build Once)?
Answers use simple, clear English.
Quick interview answer
Test Artifact Promotion (Build Once) with unit checks for the happy path, integration tests for real I/O boundaries, and load/chaos checks so regressions show up before prod. Core idea: At Architect depth: start with the problem, then mechanism, then a short example. Build a versioned image/package once in CI; promote the same digest through staging→prod.
Detailed answer
Interview answer for testing Artifact Promotion (Build Once): 1) Unit: isolate the pure logic behind Artifact Promotion (Build Once) with deterministic fixtures. 2) Integration: exercise real timers/I/O/network boundaries the way production does. 3) Load & soak: prove the event path still meets SLOs under concurrency. 4) Failure injection: break dependencies and assert recovery/backpressure. Best practices to include: Pin by digest; SBOM; sign images (cosign). Call out mistakes: latest tag in prod; rebuilding on deploy job. Parent context: At Architect depth: start with the problem, then mechanism, then a short example. Build a versioned image/package once in CI; promote the same digest through staging→prod.
Full explanation
Interviewers want a test strategy, not “I would write tests.” Tie each layer back to how Artifact Promotion (Build Once) fails: correctness, latency, and starvation. Build a versioned image/package once in CI; promote the same digest through staging→prod. Never rebuild for prod with different flags.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — Artifact Promotion (Build Once)
At Architect depth: start with the problem, then mechanism, then a short example. Build a versioned image/package once in CI; promote the same digest through staging→prod.
View full parent question →