Basically what is happening is that right now the python test suite discovery relies on pytest running with the --collect-only flag. For normal projects, this works fine as this pytest command would take 1-2 seconds. But if you happen to have a really big python project with 80K tests and counting like in my company, Rippling, then the test collection takes over 10 minutes, and usually breaks the editor with too much data.
This is how the Microsoft test runner does it, and looking at your source code, this is how it's done here as well.
This problem is the last major blocker for my company's adoption of VS Code, and I'm sure that this is a problem for other companies with large python code bases as well :( . Is there any guidance or feature addition you could give us?
Hi there!
OK, so leveling with you here-- this is pretty much a copy of this ticket I submitted to Microsoft.
Basically what is happening is that right now the python test suite discovery relies on pytest running with the
--collect-onlyflag. For normal projects, this works fine as this pytest command would take 1-2 seconds. But if you happen to have a really big python project with 80K tests and counting like in my company, Rippling, then the test collection takes over 10 minutes, and usually breaks the editor with too much data.This is how the Microsoft test runner does it, and looking at your source code, this is how it's done here as well.
This problem is the last major blocker for my company's adoption of VS Code, and I'm sure that this is a problem for other companies with large python code bases as well :( . Is there any guidance or feature addition you could give us?