Why is the testing framework so often broken? #23066
-
|
I love VS Code, but this is infuriating. It makes me wonder whether I should switch to PyCharm. For the past few years, over 50% of the time I can remember, the Testing tab feature has not worked properly for Python. Either there's an error discovering tests, or when I try to run a test it says "Finished running tests!" without doing anything...I've reported issues before and problems just keep popping back up. I'm seeing the same problems on Insiders and on stable. Maybe I see more problems since I code on WSL? I normally use the workaround of the "debug file" button on a unit test file when I need to debug, but the debugger isn't stopping on breakpoints for some reason. This is so frustrating. Python is one of the very biggest languages in the world and unit testing and debugging are basic features that need to just work! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Can you please open issues as appropriate for the issues you're currently facing? We completely rewrote our testing support and pushed it out to everyone this year after spending over a year on that specific project. Otherwise there isn't anything actionable here and users in general have been quite happy w/ our rewrite. As such, I'm going to lock this issue and ask that you please open issues following the instructions at https://aka.ms/pvsc-bug to help us figure out why you're having issues w/ testing. |
Beta Was this translation helpful? Give feedback.
Can you please open issues as appropriate for the issues you're currently facing? We completely rewrote our testing support and pushed it out to everyone this year after spending over a year on that specific project.
Otherwise there isn't anything actionable here and users in general have been quite happy w/ our rewrite. As such, I'm going to lock this issue and ask that you please open issues following the instructions at https://aka.ms/pvsc-bug to help us figure out why you're having issues w/ testing.