neotest-vitest icon indicating copy to clipboard operation
neotest-vitest copied to clipboard

Vitest adapter for Neovim Neotest plugin

Results 27 neotest-vitest issues
Sort by recently updated
recently updated
newest added

I just installed and setup for the first time and got things seemingly working except they always show as failed even when the tests are successful. See screenshot. Any thoughts?...

Still a draft, taking inspiration from [neotest-jest](https://github.com/nvim-neotest/neotest-jest/pull/51) I had first to make the plugin tests works first, nio module was missing somehow and I had troubles on asserting command paths...

Looks like this is not supported, am I right? They looks to be "listed" in the output, but not in the summary and they're always "skipped".

Tests using backticks/template literals (`) do not get listed in the summary (and may not be found by the adapter at all; not sure). Example: ![image](https://user-images.githubusercontent.com/595711/185988902-0d6628b0-3ff1-43a4-8add-0cb76a47417b.png)

bug

Anytime neotest-vitest is used within a buffer attempting to change the current working directory within neovim fails due to nio background tasks. Full stack trace: ```  Error 09:16:12 AM...

In a monorepo where tests are managed in a package, the root package.json is unlikely to have `vitest` as a dependency. This handles that case by parsing each workspace's package.json...

We have a `__tests__` folder in the root of our project for legacy reasons and the actual tests for our components are in the components' sub-folders within `src`. How to...

Tried using with a workspace based mono repo. I had to delete the package.json dependency checks in my fork to get this plugin to work. May want to refactor how...