Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Test result not found on VS Code Ext

See original GitHub issue

Describe the bug

Right clicking the test on Vscode returns “Test result not found”

Reproduction

Right clicking the test on Vscode

System Info

System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
    Memory: 16.94 GB / 31.78 GB
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.53)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    @vitejs/plugin-react: ^1.3.2 => 1.3.2
    vite: ^2.9.9 => 2.9.9
    vitest: ^0.12.9 => 0.12.10

Used Package Manager

npm

Validations

Follow our Code of Conduct
Read the Contributing Guidelines.
Read the docs.
Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
The provided reproduction is a minimal reproducible example of the bug.

Issue Analytics

State:
Created a year ago
Reactions:3
Comments:7 (1 by maintainers)

Top GitHub Comments

3reactions

KevinAshercommented, Jul 6, 2022

I had a similar issue, turns out I was using yarn workspaces and the actual root of my package was deeply nested in another folder, so when the extension tried to run yarn test, it couldn’t find the test command, so a simple fix was to change the command line setting in of the extension to cd in the directory and then run yarn test as follows:

2reactions

denisonepiececommented, Aug 1, 2022

@acostaf not working with multiple workspaces in last version. After opening folder in new vscode window, everthing is ok. Maybe reproducing on macos?

Top Results From Across the Web

Test result not found for pytest. · Issue #16963 - GitHub

Click the test explorer icon on the explorer tab to the left and click Configure Python tests : Select pytest in the dropdown...

VS Code “Test result not found for:” When Running Tests for a ...

Check the Output panel and click on the drop-down and select Python Test Log to see the stack trace of the error to...

VS Code not finding pytest tests - python - Stack Overflow

10 Answers 10 · Uninstall the Python extension · Delete the file that contains the extension from your ~/.vscode folder (mine looked like...

Testing Python in Visual Studio Code

Python testing in Visual Studio Code. The Python extension supports testing with Python's built-in unittest framework and pytest.

Troubleshoot Terminal launch failures - Visual Studio Code

Troubleshooting steps · Test your shell directly. Try running your designated integrated terminal shell outside VS Code from an external terminal or command ......