-
-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calva not detecting tests when trying to run a single tests. #1269
Comments
Thanks for the report! |
I cannot reproduce this on MacOS. I suspect it may be an issue only on Windows. Do you see any errors in the developer console after reproducing the issue? @PEZ Maybe you could try this on your Windows machine? @jmayaalv If you'd like to debug and fix this, Calva has a pretty easy contribution process. |
Thank you for looking at this @bpringe. I am not really a VS code user myself and the ecosystem is very foreign for me, i use Cider and on macOS as well. I reported this on behalf of a new team mate totally new to the Clojure ecosystem. We check the the console but there doesn't seem to be anything relevant there, screenshot below: |
Thanks, it seems a good next step would be for someone to run Calva in the extension development host on Windows and set breakpoints to see where things are going wrong. CC @PEZ |
Calva currently fails silently when the test commands fail due to the unknown-op status. Here we handle that error and show a warning message when it occurs. This doesn't address the root cause of the issue, but it will help users to understand the problem. This will help to debug BetterThanTomorrow#1269
Calva currently fails silently when the test commands fail due to the unknown-op status. Here we handle that error and show a warning message when it occurs. This doesn't address the root cause of the issue, but it will help users to understand the problem. This will help to debug BetterThanTomorrow#1269
Calva currently fails silently when the test commands fail due to the unknown-op status. Here we handle that error and show a warning message when it occurs. This doesn't address the root cause of the issue, but it will help users to understand the problem. This will help to debug BetterThanTomorrow#1269
Calva currently fails silently when the test commands fail due to the unknown-op status. Here we handle that error and show a warning message when it occurs. This doesn't address the root cause of the issue, but it will help users to understand the problem. This will help to debug BetterThanTomorrow#1269
Calva currently fails silently when the test commands fail due to the unknown-op status. Here we handle that error and show a warning message when it occurs. This doesn't address the root cause of the issue, but it will help users to understand the problem. This will help to debug BetterThanTomorrow#1269
Can you try to reproduce this again with the latest Calva please? We added better error reporting, and I would expect to see a better error message in the REPL window now. |
Hello @marcomorain, Thanks a lot for the help ! |
Awesome! |
Calva is unable to detect test when trying to run a single tests. Test is found if all the tests in the namespace are executed.
I could reproduce it on windows and can say that works on cider, so probably not something related to
cider-nrepl
the output when running a single tests is always:The same behavior can be seen if
deftest
is aliased or refered, so doesn't seem to be related to #1086The text was updated successfully, but these errors were encountered: