#neotest — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #neotest, aggregated by home.social.
-
I did it!
Well, mostly I just tried #Neotest again with #Neovim.
As it turns out, the plugin was actually working currectly. At least for the most part.
There's a summary pane you can toggle and run tests from there and that's working perfectly.
What's not working at all, is running tests from a file or "nearest" test from the cursor position.
I've already opened up an issue with the Neotest project on GitHub.
Other than that, I'm really happy with the integration. 🙂
-
I did it!
Well, mostly I just tried #Neotest again with #Neovim.
As it turns out, the plugin was actually working currectly. At least for the most part.
There's a summary pane you can toggle and run tests from there and that's working perfectly.
What's not working at all, is running tests from a file or "nearest" test from the cursor position.
I've already opened up an issue with the Neotest project on GitHub.
Other than that, I'm really happy with the integration. 🙂
-
I did it!
Well, mostly I just tried #Neotest again with #Neovim.
As it turns out, the plugin was actually working currectly. At least for the most part.
There's a summary pane you can toggle and run tests from there and that's working perfectly.
What's not working at all, is running tests from a file or "nearest" test from the cursor position.
I've already opened up an issue with the Neotest project on GitHub.
Other than that, I'm really happy with the integration. 🙂
-
I did it!
Well, mostly I just tried #Neotest again with #Neovim.
As it turns out, the plugin was actually working currectly. At least for the most part.
There's a summary pane you can toggle and run tests from there and that's working perfectly.
What's not working at all, is running tests from a file or "nearest" test from the cursor position.
I've already opened up an issue with the Neotest project on GitHub.
Other than that, I'm really happy with the integration. 🙂
-
I did it!
Well, mostly I just tried #Neotest again with #Neovim.
As it turns out, the plugin was actually working currectly. At least for the most part.
There's a summary pane you can toggle and run tests from there and that's working perfectly.
What's not working at all, is running tests from a file or "nearest" test from the cursor position.
I've already opened up an issue with the Neotest project on GitHub.
Other than that, I'm really happy with the integration. 🙂
-
anyone know if with #neotest #neotestpython #nvim #lunarvim there is a way to create a test for a function? Like select function and create a test method? Maybe also jump to test?
-
anyone know if with #neotest #neotestpython #nvim #lunarvim there is a way to create a test for a function? Like select function and create a test method? Maybe also jump to test?
-
anyone know if with #neotest #neotestpython #nvim #lunarvim there is a way to create a test for a function? Like select function and create a test method? Maybe also jump to test?
-
anyone know if with #neotest #neotestpython #nvim #lunarvim there is a way to create a test for a function? Like select function and create a test method? Maybe also jump to test?
-
Third time seems to be the charm. After 2 attempts with spacemacs, I finally seem to have gotten a working setup with #Doomemacs.
The thing that took the longest time to figure out was getting #pyenv and #pyright to work correctly.
1. pyenv - project integration code needed to be added
2. pyenvs should be then created in the same name as the project itself
3. pyenv local needed to be run to create .python-version file
4. both lsp and tree-sitter tools enabled and added to python
Now I am almost feature parity with my #lunarvim #neotest setup to run tests. The final piece missing is DAP debugger... coming at you DAP -
Third time seems to be the charm. After 2 attempts with spacemacs, I finally seem to have gotten a working setup with #Doomemacs.
The thing that took the longest time to figure out was getting #pyenv and #pyright to work correctly.
1. pyenv - project integration code needed to be added
2. pyenvs should be then created in the same name as the project itself
3. pyenv local needed to be run to create .python-version file
4. both lsp and tree-sitter tools enabled and added to python
Now I am almost feature parity with my #lunarvim #neotest setup to run tests. The final piece missing is DAP debugger... coming at you DAP -
Third time seems to be the charm. After 2 attempts with spacemacs, I finally seem to have gotten a working setup with #Doomemacs.
The thing that took the longest time to figure out was getting #pyenv and #pyright to work correctly.
1. pyenv - project integration code needed to be added
2. pyenvs should be then created in the same name as the project itself
3. pyenv local needed to be run to create .python-version file
4. both lsp and tree-sitter tools enabled and added to python
Now I am almost feature parity with my #lunarvim #neotest setup to run tests. The final piece missing is DAP debugger... coming at you DAP -
Third time seems to be the charm. After 2 attempts with spacemacs, I finally seem to have gotten a working setup with #Doomemacs.
The thing that took the longest time to figure out was getting #pyenv and #pyright to work correctly.
1. pyenv - project integration code needed to be added
2. pyenvs should be then created in the same name as the project itself
3. pyenv local needed to be run to create .python-version file
4. both lsp and tree-sitter tools enabled and added to python
Now I am almost feature parity with my #lunarvim #neotest setup to run tests. The final piece missing is DAP debugger... coming at you DAP -
Third time seems to be the charm. After 2 attempts with spacemacs, I finally seem to have gotten a working setup with #Doomemacs.
The thing that took the longest time to figure out was getting #pyenv and #pyright to work correctly.
1. pyenv - project integration code needed to be added
2. pyenvs should be then created in the same name as the project itself
3. pyenv local needed to be run to create .python-version file
4. both lsp and tree-sitter tools enabled and added to python
Now I am almost feature parity with my #lunarvim #neotest setup to run tests. The final piece missing is DAP debugger... coming at you DAP