Skip to content

Conversation

@ChrisPenner
Copy link
Member

@ChrisPenner ChrisPenner commented Oct 21, 2025

Overview

Allow the MCP to effectively run > test.

Implementation notes

  • Add a new tool for running (pure) tests, with an optional sub-namespace.

Test coverage

Added a transcript test.

Loose ends

How do we want to handle IO tests? Presumably tests are made to be run so it should be "safe" to allow the MCP to run them?

But also it's possible that it's an IO test that the AI itself just added... which makes it a bit more of a grey area 😐

@ChrisPenner ChrisPenner requested a review from aryairani October 22, 2025 00:52
@aryairani
Copy link
Contributor

How do we want to handle IO tests? Presumably tests are made to be run so it should be "safe" to allow the MCP to run them?

But also it's possible that it's an IO test that the AI itself just added... which makes it a bit more of a grey area 😐

Yeah I think just tag them as "could touch the world" and we'll go from there.

@aryairani aryairani merged commit 9f7fc16 into trunk Oct 22, 2025
31 checks passed
@aryairani aryairani deleted the mcp/tests branch October 22, 2025 02:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants