---
title: "Discussion on \"Same Prompt, Different Test: Using AI Agent Workspaces to Make Testing Repeatable\" | Hashnode"
description: "Discussion on \"Same Prompt, Different Test: Using AI Agent Workspaces to Make Testing Repeatable\". Ask an AI agent to test your app twice, and you’ll probably get two different tests. Here’s how you can use an AI agent workspace to make your testing more repeatable."
url: "https://hashnode.com/posts/same-prompt-different-test-using-ai-agent-workspaces-to-make-testing-repeatable/6af8931c4aebfdfe7ae23cda"
---

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

Discussion

# [Same Prompt, Different Test: Using AI Agent Workspaces to Make Testing Repeatable](https://johnjvester.hashnode.dev/same-prompt-different-test-using-ai-agent-workspaces-to-make-testing-repeatable?utm_source=hashnode&utm_medium=feed)

Ask an AI agent to test your app twice, and you’ll probably get two different tests. Here’s how you can use an AI agent workspace to make your testing more repeatable.

14h ago · 9 min read · johnjvester.hashnode.dev  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#ai-workspace](https://hashnode.com/tag/ai-workspace)
-   [#tricentis](https://hashnode.com/tag/tricentis)
-   [#testing](https://hashnode.com/tag/testing)
-   [#repeat](https://hashnode.com/tag/repeat)
-   [#agentic-ai](https://hashnode.com/tag/agentic-ai)

## Written by

[John Vester](https://hashnode.com/@johnjvester)

@johnjvester

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

technologist | writer | musician | volunteer

Information Technology professional with 30+ years expertise in application design and architecture, feature development, project management, system administration and team supervision. Currently focusing on enterprise architecture/application design utilizing object-oriented programming languages and frameworks.

## Responses 1

Markdown supported · ⌘↵ to post

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[14h ago](https://hashnode.com/posts/same-prompt-different-test-using-ai-agent-workspaces-to-make-testing-repeatable/6af8931c4aebfdfe7ae23cda/comment/6af896f835d31d8be59a152c)

The Slack number is the part that frames the whole problem well, only about 20 percent of runs following the same sequence. Without that, repeatability sounds like a nice extra instead of the core requirement for regression tests and audits. The three approval gates are the detail I would keep too, especially the one before the write to qTest, since a bad decision saved into a workflow repeats on every run. The point about humans deciding whether a test checks the right thing is the honest limit of the whole approach, and it is good to see it stated plainly.