Help: Tests running slower then vim-test

[DanielCardonaRojas]

First of all thank you for creating this awesome plugin.

So I'm using neovim 0.7 and have setup vim-ultest and works fine, except for the fact that I noticed that test run much slower than running with vim-test.

I read something in the documentation regarding updatetime and watch mode but I couldn't understand it completely.

My setup is using lua so help would be appreciated to solve this in lua.

[CrystalMethod]

Same issue here.

In my case, however, I develop with Java / Maven and JUnit tests. While ":TestFile" from "vim-test" executes all tests in a .java file in one single Maven call, ":Ultest" executes each individual test case in a separate Maven call. Is there any chance to achieve this behaviour with Ultest? Are there any settings?

From the docs:

:Ultest
  Run all tests in the current file Some runners can be run as a single
  command if the output can be parsed to gain results. Otherwise, each test is
  run as a single command.

  Running as a single command can significanly improve performance, so if your
  runner is not yet supported please open an issue with sample output! Check
  the repo wiki for an updated list of runners.

[rcarriga]

So yes as the docs says ultest needs to be able to parse the output of the test runner to run the tests together. Otherwise tests must be run separately to use the exit code for each test. You can see the existing parsers here https://github.com/rcarriga/vim-ultest/blob/master/rplugin/python3/ultest/handler/parsers/output.py#L22. It's just a few regexes, I'd be happy to help with a PR :smile: