Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Nothing happens on Ultest* commands

See original GitHub issue

Very similar to #21.

Describe the bug Nothing happens when running Ultest* commands. Tests are seemingly detected fine (they show up in UltestSummary tree), however, they are not actually running. I am in Typescript test file, using Jest. :TestFile from vim-test runs succesfully.

Logs should be created using ULTEST_LOG_LEVEL=DEBUG ULTEST_LOG_FILE=vim-ultest.log nvim <test-file> and added here as well:

21:33:00 | INFO | MainThread | logging.py:create_logger:98 | Logger created 21:33:00 | DEBUG | MainThread | init.py:init:41 | Handler created 21:33:01 | DEBUG | Thread-1 | init.py:_handle_coroutine:57 | Starting job with group update_positions 21:33:01 | INFO | Thread-1 | tracker.py:_async_update:52 | Updating positions in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | file.py:parse_file_structure:22 | Converted pattern {‘test’: [‘\v^\s*%(it|test)\s*[( ]\s*%("|'|)(.*)%("|\'|)’], ‘namespace’: [‘\v^\s*%(describe|suite|context)\s*[( ]\s*%("|'|)(.*)%("|\'|)’]} to {‘test’: [re.compile(‘^\s*(?:it|test)\s*[( ]\s*(?:"|'|)(.*)(?:"|\'|)’)], ‘namespace’: [re.compile(‘^\s*(?:describe|suite|context)\s*[( ]\s*(?:"|'|)(.*)(?:"|\'|)’)]} 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test /path/to/bar.test.ts found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test bar5117784500479910972 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo0 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo1 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo2 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo3 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo4 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo5 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo6 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo7 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_async_update:79 | New test foo8 found in /path/to/bar.test.ts 21:33:01 | DEBUG | Thread-1 | tracker.py:_remove_old_positions:122 | No tests removed 21:33:01 | DEBUG | Thread-1 | init.py:_handle_coroutine:77 | Finished job with group update_positions 21:33:17 | INFO | MainThread | init.py:run_nearest:125 | Running nearest test in bar.test.ts at line 0 21:33:17 | INFO | MainThread | init.py:run_nearest:129 | No tests found for bar.test.ts rerunning after processing positions

To Reproduce See above

Expected behavior Tests actually run

Screenshots None

Additional context :checkhealth does not show any problems, remote plugins are up-to-date, Python3 and pynvim are available (I am also using UltiSnips which need Python and are functioning fine).

Issue Analytics

State:
Created 2 years ago
Reactions:2
Comments:16 (7 by maintainers)

Top GitHub Comments

3reactions

adammfrankcommented, May 7, 2022

Same here. Vim-test runs and Ultest does nothing. Typescript with Jest.

1reaction

nathani-axiscommented, Sep 22, 2021

I’m having the same issue, I can run vim-test commands but no Ultest commands I’m running vim-ultest in https://www.lunarvim.org/, and I’m working with go files, using the standard go tests

here’s my logs:

12:08:00 | INFO | MainThread | logging.py:create_logger:101 | Logger created
12:08:01 | INFO | MainThread | __init__.py:__init__:28 | Using local threaded child watcher
12:08:01 | DEBUG | MainThread | __init__.py:__init__:43 | Handler created
12:08:01 | ERROR | MainThread | tracker.py:_get_file_patterns:103 | Error while evaluating patterns for file test_file.go
Traceback (most recent call last):
  File "/home/nathani/.local/share/lunarvim/site/pack/packer/start/vim-ultest/rplugin/python3/ultest/handler/tracker.py", line 101, in _get_file_patterns
    return self._vim.sync_call("ultest#adapter#get_patterns", file)
  File "/home/nathani/.local/share/lunarvim/site/pack/packer/start/vim-ultest/rplugin/python3/ultest/vim_client/__init__.py", line 121, in sync_call
    return self._eval(expr, sync=True)
  File "/home/nathani/.local/share/lunarvim/site/pack/packer/start/vim-ultest/rplugin/python3/ultest/vim_client/__init__.py", line 134, in _eval
    return self._vim.eval(expr, async_=not sync)
  File "/home/nathani/.local/lib/python3.7/site-packages/pynvim/api/nvim.py", line 295, in eval
    return self.request('nvim_eval', string, **kwargs)
  File "/home/nathani/.local/lib/python3.7/site-packages/pynvim/api/nvim.py", line 182, in request
    res = self._session.request(name, *args, **kwargs)
  File "/home/nathani/.local/lib/python3.7/site-packages/pynvim/msgpack_rpc/session.py", line 102, in request
    raise self.error_wrapper(err)
pynvim.api.common.NvimError: Vim(let):E117: Unknown function: test#determine_runner
12:08:01 | DEBUG | MainThread | tracker.py:update:34 | No patterns found for test_file.go
12:08:03 | INFO | MainThread | __init__.py:run_nearest:125 | Running nearest test in test_file.go at line 0
12:08:03 | INFO | MainThread | __init__.py:run_nearest:130 | No tests found for test_file.go, rerunning after processing positions
12:08:03 | ERROR | MainThread | tracker.py:_get_file_patterns:103 | Error while evaluating patterns for file test_file.go
Traceback (most recent call last):
  File "/home/nathani/.local/share/lunarvim/site/pack/packer/start/vim-ultest/rplugin/python3/ultest/handler/tracker.py", line 101, in _get_file_patterns
    return self._vim.sync_call("ultest#adapter#get_patterns", file)
  File "/home/nathani/.local/share/lunarvim/site/pack/packer/start/vim-ultest/rplugin/python3/ultest/vim_client/__init__.py", line 121, in sync_call
    return self._eval(expr, sync=True)
  File "/home/nathani/.local/share/lunarvim/site/pack/packer/start/vim-ultest/rplugin/python3/ultest/vim_client/__init__.py", line 134, in _eval
    return self._vim.eval(expr, async_=not sync)
  File "/home/nathani/.local/lib/python3.7/site-packages/pynvim/api/nvim.py", line 295, in eval
    return self.request('nvim_eval', string, **kwargs)
  File "/home/nathani/.local/lib/python3.7/site-packages/pynvim/api/nvim.py", line 182, in request
    res = self._session.request(name, *args, **kwargs)
  File "/home/nathani/.local/lib/python3.7/site-packages/pynvim/msgpack_rpc/session.py", line 102, in request
    raise self.error_wrapper(err)
pynvim.api.common.NvimError: Vim(let):E117: Unknown function: test#determine_runner
12:08:03 | DEBUG | MainThread | tracker.py:update:34 | No patterns found for test_file.go

Top Results From Across the Web

Nothing happens on any Ult* command · Issue #21 · rcarriga/vim-ultest

Describe the bug When attempting to run any of the Ult* commands, nothing happens. Output of vim-ultest.log after running UltestNearest and then ...

Take your testing to the next level with vim-ultest! : r/neovim

However nothing happens when I'm trying to call Ultest or UltestNearest on a test. ... for instance, the command to run the nearest...

Four Completely Useless Linux Commands - The Geek Stuff

There are two advantages of using Linux command line instead of UI. ... tried ul command with a file that has underscores, nothing...

Command Line Options - SeleniumBase Docs

SeleniumBase provides additional pytest command-line options for tests: ... (NOTE: If you use --demo-sleep={NUM} without using --demo , nothing will happen.

Neovim for Beginners — Testing

Testing a file or a suite of test cases is straightforward. We can use either the Ultest , TestFile , or TestSuite command....