Fix for @InjectTest with inherited field injection #499
Conversation
This file contains 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
With a test class with inheritance and field injection on inherited fields, those fields were not being injected. This fixes this issue.
rob-bygrave
commented
Feb 12, 2024
| @Test | ||
| void test_expect_inheritedFieldIsInjected() { | ||
| assertThat(something).isNotNull(); | ||
| assertThat(steamer).isNotNull(); |
There was a problem hiding this comment.
This [inherited] steamer field was not getting injected
SentryMan
deleted the
feature/fix-testscope-inherited-fields-injection
branch
|
I had forgotten that we could do that with abstract classes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With a test class with inheritance and field injection on inherited fields, those fields were not being injected.
This fixes this issue.