Skip to content

Expose running of unit tests to agent mode #250145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
davidanthoff opened this issue May 30, 2025 · 3 comments
Open

Expose running of unit tests to agent mode #250145

davidanthoff opened this issue May 30, 2025 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@davidanthoff
Copy link
Contributor

The Julia extension implements the testing API that VS Code has, i.e. Julia tests show up in the default VS Code testing UI and can be run via that.

I would have thought that in agent mode, when I ask it to make some edits and then run tests, that it would hook into that and run the tests via the default VS Code testing framework. But instead, it wants to launch a new Julia instance with command line parameters that would run the test.

I think ideally in agent mode, if an extension hooks into the testing API that VS Code provides, it should run tests that way.

@connor4312
Copy link
Member

There is a test runner tool that's available to the agent, but it might not be choosing to use it for whatever reason...

@connor4312 connor4312 added the bug Issue identified by VS Code Team member as probable bug label May 31, 2025
@davidanthoff
Copy link
Contributor Author

Hm, so this is the list of tools that I see, doesn't look like a test runner tool is exposed, maybe?

Image

@connor4312
Copy link
Member

connor4312 commented Jun 1, 2025

We have a tool for running tests, but it's enabled based on specific logic so that it's only present and added programmatically when there are tests contributed via the VS Code Testing API. It's possible this logic is outdated now, I need to revisit it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

2 participants