test: split integration tests and instantiate Vault per class - #142
Merged
Conversation
stklcode
force-pushed
the
test/split-it
branch
2 times, most recently
from
September 4, 2026 14:40
d264a35 to
56c0bb3
Compare
Tests became quite long. Extract nested into top-level classes and add an abstract base class. We only start one Vault instance per class and not per test method, if not required otherwise.
stklcode
force-pushed
the
test/split-it
branch
from
September 4, 2026 14:41
56c0bb3 to
f65fa0d
Compare
|
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
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.
Tests became quite long. Extract nested into top-level classes and add an abstract base class.
We only start one Vault instance per class and not per test method, if not required otherwise.