You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have verified that package.json contains a script "test": "jest --watch".
I have verified that running the following on the command line works: npm run test.
I have verified that neotest-jest is apparently finding jest in devDependencies.
I have looked at what file_path parameter the function adapter.is_test_file is receiving, and it is NOT the file that "Run Nearest" was executed in.
I'm pretty sure Its something I'm doing wrong, but I've exhausted my current thoughts on what the issue might be... Any help would be appreciated, even if its tips on debugging.
The text was updated successfully, but these errors were encountered:
@folke Thanks for all your amazing work. Just as a data point, I've been trying to get neotest-jest working via :LazyExtras for a few hours now, and it was this thread, specifically adding the treesitter dependency as described above that finally resolved it. With the line there, it works, without it I get "No tests found". I'm on LazyVim 10.8.2, nvim v0.9.4, MacOS 14.2.1.
My configuration is based on LazyVim, having added support for Neotest by including the appropriate "extras" configuration.
To ensure it wasn't an issue with my original project, I created a simple Next.js project here.
Additional configuration is specified in
lua/plugins/test.lua
with the following content:I have verified that package.json contains a script
"test": "jest --watch"
.I have verified that running the following on the command line works:
npm run test
.I have verified that neotest-jest is apparently finding
jest
indevDependencies
.I have looked at what
file_path
parameter the functionadapter.is_test_file
is receiving, and it is NOT the file that "Run Nearest" was executed in.I'm pretty sure Its something I'm doing wrong, but I've exhausted my current thoughts on what the issue might be... Any help would be appreciated, even if its tips on debugging.
The text was updated successfully, but these errors were encountered: