feat(test): add ApplicationErrorAssert fluent assertion utility#500
Merged
sleberknight merged 1 commit intomainfrom Apr 30, 2026
Merged
feat(test): add ApplicationErrorAssert fluent assertion utility#500sleberknight merged 1 commit intomainfrom
sleberknight merged 1 commit intomainfrom
Conversation
Add AssertJ-style fluent assertions for ApplicationError via ApplicationErrorAssert, extending AbstractAssert. Supports chaining assertions on all ApplicationError fields including description, exception type/message, cause type/message, stack trace, numTimesOccurred, resolved, host info, and id. Closes #431
|
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.
Add AssertJ-style fluent assertions for ApplicationError by
introducing ApplicationErrorAssert, which extends AssertJ's
AbstractAssert. The entry point is assertThatApplicationError.
Supports chaining assertions on all ApplicationError fields:
description, exception type/message, cause type/message,
stack trace, numTimesOccurred, resolved status, host info, and id.
Each field has both equality and (where applicable) contains
variants, as well as a hasNoX variant for null checks.
Closes #499