Fausto Núñez Alberro

I believe this has to do with my config: ``` let test#strategy = "tslime" let test#filename_modifier = ':p' ``` EDIT: nevermind, it doesn't (from reading the `ultest.lua` file).

For what it's worth it was happening on Python test files, too. The filename is `forms.service.spec.ts` and the filetype is `typescript`. One important detail is that this is a monorepo,...

Related `vim-test` issue: https://github.com/vim-test/vim-test/issues/272

Thanks a lot for your time/attention! > As I said before, you will have to manually configure nvim-dap to respect the project root. So setting `g:test#project_root` isn't enough? I've updated...

We can discard the "Neovim too old" idea. I just ran `Ultest` on a project that's a bit simpler and everything's working fine: this time the directory containing `package.json` is...

Trying to build a reproduction. It's unrelated but I believe this: ``` let g:test#javascript_runner = "jest" let g:test#python_runner = "pytest" ``` Is wrong, and instead one should use: ``` let...

https://github.com/fnune/repro-issue-31-vim-ultest Copying the README here: 1. Run `yarn` 2. Open Neovim in the root directory 3. Open `packages/app/src/test_does_not_work.spec.ts` 4. Run `Ultest` there 5. Notice there's no output To "fix" it:...

What's weird is that I couldn't reproduce it with Python. I think it's because I use a virtual env and the dependencies are elsewhere? I built the same dir structure...

One important detail about the reproduction: running `yarn` creates a `node_modules` directory on the root of the repo but not in the workspace package directory. However, the `package.json` entries for...

I'm sorry it took me so long to answer. I must have lost the notification. To test this, I was running the regular version of `vim-test` and `vim-ultest`.