Add unit tests for ImportError handling and ValidationError on unbound SocketPath #10555
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.
Change Summary
This PR introduces new unit tests to enhance the test coverage by covering the following scenarios:
ValidationError for Unbound SocketPath:
Added a unit test to verify that a
ValidationError
is raised when the provided path is not bound by a socket. This ensures that the application correctly handles and reports errors related to unbound socket paths.ImportError Handling for email-validator
Introduced unit tests to verify the proper handling of ImportError scenarios related to the email-validator package. Specifically, the tests cover:
ImportError
whenemail-validator
is not installed.ImportError
when there is an invalid installation ofemail-validator
.Related to #7656
Checklist
Selected Reviewer: @sydney-runkle