Add edge-case tests for failures, timeouts, and concurrent access#11
Merged
Conversation
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
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.
Summary
Extends test coverage with 67 new edge-case tests targeting failure paths, timeout behavior, and concurrent access patterns across all architecture layers.
Changes
What's tested
Failure paths
ProcessImageUseCase(thumbnail cleanup OSError, processor ValueError, save failures at each stage)Timeouts
asyncio.timeoutwrapping slow processing, storage, and retention operationsConcurrent access
get_by_idcache misses (thundering herd)API validation boundaries
Version bump
PATCH:
2.0.0→2.0.1(tests only, no API or behavior changes)Checklist
ruff check— all cleanruff format— all formattedmypy— success, no issuespytest— 168/168 passing (67 new + 101 existing)