Improve navigation from source code to test

Open
#334 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript, vscode
Domain
developer-experience, testing, tooling

Research direction

Start by tracing the CLI test runner, test UI, and file system view entry points mentioned in the issue. Compare how the active source file and test tree are represented, then define which navigation and immediate test-execution behavior should be supported. Done means the agreed workflow is available from the source file and file system view without navigating manually through the test UI.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.
I find myself using the CLI test runner, as navigating in the test ui to the test I am working on is quite a hassle, it is too slow.

Describe the solution you'd like
Some way to
a1) jump from a source code that is test file to the test runner
a2) Have an auto-navigation mode from active file to the test tree (like in the file system view, where an open editor immediately opens the tree and selects the currently opened file)
b) A button exectute tests immediately from the file system view, like the "Run Query" command

Dominant language
TypeScript
Stars
539
Forks
240
Avg merge
2d 6h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-codeql

All issues in github/vscode-codeql

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.