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

Running tests can try to run non-tests as tests

Open
#1,480 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools, testing

Research direction

Reproduce the failure by opening the codeql-coding-standards repository and running the c folder from the testing pane. Inspect the folder-run path and compare passing --strict-test-discovery with explicitly passing discovered tests; done means non-test packs are not attempted as tests and the test packs still run.

Written by the indexing model from the issue text.

Description

bug VSCode

Describe the bug
When you have a folder that contains both multiple test packs and non-test packs, it will appear as runnable in the UI with the test packs a subpacks. When you run that folder it will also run the non-tests ibnside it as well.

Version
CodeQL extension version: 1.6.11
CodeQL CLI version: 2.10.3
Platform: linux x64

To reproduce
Open https://github.com/github/codeql-coding-standards/tree/next
Run the c folder in the testing pane. See codeql fail to find the extractor for a non-test folder.

Expected behavior

Only to try run the tests as tests.

Additional context

This can be seen by trying to run the c folder on https://github.com/github/codeql-coding-standards/tree/next

I think we either need to pass --strict-test-discovery when running or explicitly pass the set of tests rather than the folder.

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.