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.
Ultest not passing anything as parameters for rust
See original GitHub issueI’ve just ran :Ultest and it marked as running. In the end all were green but i noticed in the float window that it actually didn’t test anything:
When I run :TestFile it runs normally the file.
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Ultest not passing anything as parameters for rust
Ultest not passing anything as parameters for rust. I've just ran :Ultest and it marked as running. In the end all were green...
Read more >Issues · rcarriga/vim-ultest - GitHub
The ultimate testing plugin for (Neo)Vim. Contribute to rcarriga/vim-ultest development by creating an account on GitHub.
Read more >Passing custom command-line arguments to a Rust test
Slightly orthogonal answer to your question - can we not set environment variable for the test; if the sole purpose it to pass...
Read more >rstest in rstest - Rust - Docs.rs
You can just declare all used fixtures by passing them as a function's arguments. This can help your test to be neat and...
Read more >Passing command line arguments to test functions : r/rust
So I'm trying to write a test (as a file in project/tests/) that makes sure a function returns Err when incorrect arguments are...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ah I see now the issue. This is a vim-test bug, not vim-ultest. If you run
TestNearestit will produce the same problem. I’ve submitted a PR to vim-test https://github.com/vim-test/vim-test/pull/635Closing as the fix has now been merged