Improve test isolation and pytest integration #67
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
elronbandel
force-pushed
the
make-tests-standalone
branch
from
9180c2a to
77d2f08
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, pytest would instantiate all test classes during discovery, which caused every backend to be loaded including heavy ones like the local 8B granite model.
Now, tests can be scanned without eagerly realizing all backends. This means that missing dependencies or a faulty backend no longer block discovery: the remaining tests are still visible and runnable.
As a result, you can run and debug tests in VS Code without crashes or unnecessary loading of large models on every code change.