Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test result not found on VS Code Ext #1407

Closed
6 tasks done
acostaf opened this issue May 31, 2022 · 7 comments
Closed
6 tasks done

Test result not found on VS Code Ext #1407

acostaf opened this issue May 31, 2022 · 7 comments

Comments

@acostaf
Copy link

acostaf commented May 31, 2022

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

@itpropro
Copy link

itpropro commented Jun 8, 2022

I have the same problem in VSCode with a simple test that just checks for toBeDefined. In the terminal it works fine including watch mode, in VSCode, it throws the following error:
image

@KevinAsher
Copy link

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:

image

@itpropro
Copy link

itpropro commented Jul 7, 2022

Multiple issues were fixed by @zxch3n in the vscode repository (thanks!). If @acostaf doesn't have any additional problems, I think we can close this issue.

@acostaf
Copy link
Author

acostaf commented Jul 7, 2022

Fixed, thanks everyone.

@acostaf acostaf closed this as completed Jul 7, 2022
@DenisMitryakov
Copy link

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

@enekaken
Copy link

enekaken commented Aug 5, 2022

I'm encountering the same issue..

tried the command line option cd to the root where my package lies in my workspace along with && rushx test but getting this error.

image

  "@vitejs/plugin-react": "^1.3.1",
"vite": "^2.9.9",
"vitest": "^0.20.3"

@sheremet-va
Copy link
Member

Please, if you have an issue with vscode extension, open an issue in its repository.

@vitest-dev vitest-dev locked as resolved and limited conversation to collaborators Aug 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants