Skip to content
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

Feature: Custom Test Discovery Option #308

Open
juandiegopalomino opened this issue Mar 11, 2024 · 1 comment
Open

Feature: Custom Test Discovery Option #308

juandiegopalomino opened this issue Mar 11, 2024 · 1 comment

Comments

@juandiegopalomino
Copy link

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-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?

@kondratyev-nv
Copy link
Owner

then the test collection takes over 10 minutes, and usually breaks the editor with too much data.

Does test discovery/running works faster from the command line? I mean, how does that work if you run pytest from CLI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants