microsoft / microsoft/vscode-extension-test-runner

Tests not being discovered/shown in the Testing UI

Open
#32 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
17
Forks
15
Avg merge
2d 5h
Merged PRs (30d)
2

Description

I followed the steps in the README and can successfully run the CLI from the command line. The --coverage option works as expected on the command line but I don't see anything on vscode even after running the tests directly from the editor. Does this require any setup? Is there a sample repo I can use?

This is the launch configuration I am using:

        {
            "name": "Extension Tests",
            "type": "extensionHost",
            "request": "launch",
            "runtimeExecutable": "${execPath}",
            "testConfiguration": "${workspaceFolder}/.vscode-test.mjs",
            "args": [
                "--disable-extensions",
                "--extensionDevelopmentPath=${workspaceFolder}",
                "--extensionTestsPath=${workspaceFolder}/out/test"
            ],
            "outFiles": ["${workspaceFolder}/out/**/*.js"],
            "preLaunchTask": "npm: watch"
        }

This is what I get when I use the Test: Run All Tests command:

 *  The test run did not record any output. 

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the README instructions, the .vscode-test.mjs configuration, and the extension test launch settings shown in the issue. Run Test: Run All Tests and compare the command-line coverage behavior with the VS Code Testing UI; done means tests are discovered and shown there instead of producing no recorded output.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.