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

Hot reload test discovery #76

Open
JamesHutchison opened this issue Jan 4, 2024 · 0 comments
Open

Hot reload test discovery #76

JamesHutchison opened this issue Jan 4, 2024 · 0 comments

Comments

@JamesHutchison
Copy link
Owner

Currently, test discovery is either ran from scratch or a cached instance is used. There's checks in place to try to clear the cache. The cached test discovery is also not leveraged for --collect-only

There could be a cached test discovery. When new test functions are added / renamed / removed, the cache could be updated.

The primary beneficiary of this would be VS Code users.

Note that at Carta I created a "nose style" test discovery which was very fast and eliminated the need for this kind of thing. Likewise, PyCharm doesn't use pytest for test discovery so its already fast. This would be a somewhat complex undertaking and so going with nose style test discovery may just be preferable as a first iteration solution. This nose style test discovery does not need to be a part of this project.

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

1 participant