Repository navigation
feat(studio): run the test at the cursor, a tag, or the failed tests - #517
Merged
Merged
Conversation
Next to Run, a scope control picks the whole file (the default), the test at the cursor, the tests with one tag, or the tests that failed the last time the file ran in this session. Automation's run_file takes line, tag or failedOnly, and studio_run_file takes line, tag or failed_only; give at most one. The scope is resolved before the run starts, so a scope that matches no test is an error and nothing runs. Two tests that share a name refuse a scope that names one of them. The runner gains a name filter (TestNames) for this; the CLI is unchanged. Results group failed, passed and skipped tests when a run has more than one outcome. The failed tests are kept in memory only.
# Conflicts: # CHANGELOG.md # internal/mcp/studio.go # studio/app.go # studio/frontend/src/main.ts # studio/runtrack.go # website/src/content/docs/tools/mcp.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
run_fileand the MCP toolstudio_run_filetakeline,tagorfailed_only; give at most one. A scope that matches no test is an error and nothing runs. Two tests with the same name refuse a scope that names one of them..probefile inside the open workspace or an automation folder, and the check runs before the file is read for its tests.probe testis unchanged.mainis merged in. The conflicts were in the Studio run path, the MCP tool description and the changelog.Test plan
go vet ./...andgo test ./...instudio, including the scope tests and tests that the folder check runs before the scopego vet ./...andgo test ./internal/mcp/... ./internal/runner/... ./internal/cli/...at the repo rootnpm run build,typecheck:device-view,test:device-view,test:probescript,check:probescript,test:run-scope(10)🤖 Generated with Claude Code