🐌 Test Explorer vs Terminal: 30x Performance Difference in Large Monolithic Project #25151
Unanswered
Noam Erez (nerez)
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Environment:
Problem Statement
I'm experiencing a significant performance difference between running pytest via terminal vs VS Code Test Explorer:
Reproduction Steps
pytest path/to/test.py::test_function→ 5sHypothesis & Investigation
The performance degradation appears to scale with the number of Python files/apps in the workspace:
Questions for the team:
What overhead occurs during Test Explorer execution that doesn't happen with direct terminal pytest?
Does VS Code's test runner:
Is there any caching mechanism for:
Are there configuration options to:
Expected Behavior
Running a single test via Test Explorer should have similar performance to terminal pytest, regardless of workspace size.
Workaround Attempts
Impact
This performance difference makes Test Explorer unusable for our team's migration from PyCharm to VS Code. Any guidance on optimization strategies or configuration options would be greatly appreciated!
Thank you
All reactions