---
title: "Discussion on \"Tests Are the Verification Layer: Proving Agent Generated Changes\" | Hashnode"
description: "Discussion on \"Tests Are the Verification Layer: Proving Agent Generated Changes\". The coding agent reports that the feature is complete. The project compiles. Four tests pass. The fifth was deleted because it represented legacy behavior. This is one way to achieve a green build."
url: "https://hashnode.com/posts/verifying-ai-generated-code/6ab1f6f0eadf106c5cad8ffb"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Tests Are the Verification Layer: Proving Agent Generated Changes](https://pragmaticstack.in/verifying-ai-generated-code?utm_source=hashnode&utm_medium=feed)

The coding agent reports that the feature is complete. The project compiles. Four tests pass. The fifth was deleted because it represented legacy behavior. This is one way to achieve a green build.

Sep 22 · 5 min read · pragmaticstack.in  
Updated Sep 24  
Read the article

-   [#ai-coding](https://hashnode.com/tag/ai-coding)
-   [#software-testing](https://hashnode.com/tag/software-testing)
-   [#software-architecture](https://hashnode.com/tag/software-architecture)

## Written by

[Alen Joy](https://hashnode.com/@alenj)

@alenj · Bangalore, India

  
[View profile](https://hashnode.com/@alenj)

I help enterprises ship AI that doesn’t embarrass them in production.

AI Architect. I design the boring control plane plumbing that keeps your impressive demos from quietly setting themselves on fire in production.

## Responses 4

Markdown supported · ⌘↵ to post

[Brian · AI News](https://hashnode.com/@brianainews)

[Sep 23](https://hashnode.com/posts/verifying-ai-generated-code/6ab1f6f0eadf106c5cad8ffb/comment/6ab3ede1ccd8b2fba5a1ad24)

Context windows are not free memory. Stuffing every log into the prompt slows the loop and hides the signal. I summarize tool output hard before the next turn.

[Alen Joy](https://hashnode.com/@alenj)

[Sep 24](https://hashnode.com/posts/verifying-ai-generated-code/6ab1f6f0eadf106c5cad8ffb/comment/6ab3ede1ccd8b2fba5a1ad24#reply-6ab50360e108cdff42b6de51)

Agreed, dumping raw logs into the prompt mostly buries the one line that matters. The catch from a verification angle is that a summary can hide exactly the thing you needed to see. "Tests passed" can quietly mean one was skipped or a warning got dropped along the way.

What I'd do is keep two copies. A tight summary for the agent's next turn, and the full output stored as an artifact that CI and the reviewer can check. I'd also make the summariser keep failures, skips and warnings word for word, and only compress the passing noise.

[Puneet Khandelwal](https://hashnode.com/@lifestyle4u)

[Sep 22](https://hashnode.com/posts/verifying-ai-generated-code/6ab1f6f0eadf106c5cad8ffb/comment/6ab25152d0cebd65f6820f53)

Code reviews consume more hours than writing the actual code. Engineering time shifts entirely toward verification now, and the bottleneck slows down every single release.

[Alen Joy](https://hashnode.com/@alenj)

[Sep 24](https://hashnode.com/posts/verifying-ai-generated-code/6ab1f6f0eadf106c5cad8ffb/comment/6ab25152d0cebd65f6820f53#reply-6ab503bc04953b150d899287)

Writing code was never really the expensive part. Deciding what it should do and checking that it does was always the hard bit. Agents just made that impossible to ignore.

So review time has to be protected. Anything a machine can check should be checked before a person opens the PR. Changes stay small. Reviewers spend their attention on changed test expectations and on whether the intent is right, not on rereading every line.

If the agents still produce more than the team can get through, slow the agents down. A pile of unreviewed PRs looks like progress but isn't.
