Prevent assertion aspects from crashing on missing optional types - #1415
Merged
Conversation
pratushnyi
approved these changes
Sep 3, 2026
This was referenced Sep 3, 2026
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
2 participants
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.
Context
Projects can now use Allure’s AssertJ and JUnit Jupiter assertion integrations alongside Spring Boot and other libraries that reference optional types without AspectJ aborting during class loading or generating
ajcorecrash dumps. Assertion calls continue to appear as Allure steps, including fluent AssertJ chains and JUnit exception assertions.The regression is covered by a self-contained missing-type scenario, ensuring it remains effective independently of future Spring Boot dependency changes.
fixes #977
Checklist