Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Show test results in CodeQL results view

Open
#933 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
developer-experience, devtools

Research direction

Start by locating the extension code that produces CodeQL test output and the implementation of the CodeQL results view. Trace how test result locations are represented and displayed; the work is done when test results open in the results view and their location information supports navigation to the relevant source elements.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.
When developing QL tests it can be difficult to triage the initial results shown in the CodeQL tests output, because you must manually lookup the cases in the test source file.

Describe the solution you'd like
Open the test results in the CodeQL results view where we can use the location information to quickly go to source elements.

Describe alternatives you've considered
n/a

Additional context
Add any other context or screenshots about the feature request here.

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.