[#noissue] Add null check for PluginTestReport in PluginForkedTestUnitTestDescriptor #13177
+22
−15
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.
This pull request updates the copyright year and improves the robustness of the test report output handling in the
PluginForkedTestUnitTestDescriptorclass. The main change ensures that the code checks for anullreport before setting output and logs a message if the report is missing, preventing potentialNullPointerExceptions during test execution.Improvements to test report output handling:
nullcheck for thereportobject before setting its output, preventing exceptions when the report is missing.null, including relevant identifiers and output for easier debugging.General maintenance: