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

Failing integration tests when running locally

Open
#972 1 comment 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-qa

Research direction

Start with extensions/ql-vscode/src/vscode-tests/cli-integration/databases.test.ts, especially the "should add a database from a folder" test, and run the integration tests repeatedly in a local environment. Inspect how temporary databases are created and cleaned up; done means the test passes on subsequent runs without manually deleting /private/var/folders/.../tmp-* databases.

Written by the indexing model from the issue text.

Description

bug VSCode

When running integration tests locally, they pass the first time you run them and fail subsequently.

In particular, extensions/ql-vscode/src/vscode-tests/cli-integration/databases.test.ts should add a database from a folder fails. And I can get it passing if I clear out all of the vscode temporary databases in /private/var/folders/41/kxmfbgxj40dd2l_x63x9fw7c0000gn/T/tmp-*. (This is likely a different folder on different machines.)

The integration tests are passing on CI because they always run in a clean state.

I can think of two possibilities that might fix the problem:

  1. Run cleanup code (eg- delete all databases) after running all the tests
  2. Ensure we have a clean slate before starting any tests.

version: CodeQL extension version: 1.5.6 CodeQL CLI version: 2.6.3 Platform: darwin x64

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

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.