Add tests for error handling and retry scenarios in RegistryWireMockTest #165
+90
−0
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.
Signed-off-by: vaidikcode [email protected]
Description
Issue #23
This PR improves test coverage for the Registry client by adding three new test methods:
shouldHandle500Error
: Tests the client's ability to properly handle HTTP 500 errors from the registry and convert them into OrasExceptions with the correct status code.shouldHandleTimeout
: Tests the client's handling of HTTP 408 (Request Timeout) responses, ensuring that timeout conditions are properly propagated as OrasExceptions.shouldRetryBlobUpload
: Implements scenario-based testing using WireMock to verify that the client can successfully retry blob uploads after an initial server error. This test demonstrates the retry capability of the Registry client when pushing content.Testing done
Tests run successfully in isolation and in sequence
Some existing test failures in other classes are unrelated to these changes
Submitter checklist
mvn license:update-file-header
,mvn spotless:apply
,pre-commit run -a
,mvn clean install
before opening the PR