Guides · Test as you build

Test and validate the system as it is being built

10 November 2026 · Escherbridge

GAO's Agile Assessment Guide treats "test and validate the system as it is being developed" as a requirements-management practice: continuous integration and automated testing in the build process, and a product owner who agrees to and accepts the definition of done for each user story. A clean compile is not the same as meeting the requirement. GAO is explicit: even good-quality code may not meet the original user story, which is why testing and a shared definition of done belong in the build, not only after a demo. This is a delivery practice, not a QA-tool sales page, and not a client story.

the GAO Agile Assessment Guide is cited here as the September 2020 Exposure Draft, not as a later final edition.

the GAO Agile Assessment Guide, "Test and Validate the System as it is Being Developed." "In an Agile environment, teams routinely build and test the software through continuous integration and automated testing." "Continuous integration merges all developer working copies to ensure they function as intended through an automated process by repeatedly integrating the code multiple times a day. However, continuous integration is only as strong as the automated testing used in the build process. If a build fails, the developer should address the issue and resubmit the code for continuous integration. Once successfully built and adopted into the code base, the developer and organization can gain confidence that the code will execute properly in the future." "Code may not meet the requirements of the original user story even if the quality of the code is good."

The chapter's best-practice checklist for this practice: "Continuous integration and automated testing are used in the build process." "The product owner agrees to and accepts the definition of done for each user story."

What the guide actually says

Routine build-and-test through continuous integration and automated testing; integrate multiple times a day; CI is only as strong as the automated tests; a failed build is addressed and resubmitted; confidence comes after a successful build is adopted into the code base. The product owner agrees to and accepts the definition of done for each story. What is a definition of done is the short companion for that shared test. Verifiable requirements and a definition of done and Working software in Agile development are the batch-1 siblings. Each wave ends with a check is the house essay for an honest go / adjust / not-yet.

This page does not invent a house CI stack, a client, a defect rate, a pass rate, or a required tool. It uses no CHAOS rates.

The first conversation still ends with a yes, a no, or a better idea, at Start. The dashboard remains "opening soon."

The useful next step is to put automated tests in the build, and to agree the definition of done before the next story starts. If something on this page is wrong, write to us.

Author: Escherbridge. Last reviewed: 2026-11-10, America/Denver.