Overview
File handling crosses several boundaries: HTTP upload metadata, temporary files, content validation, storage permissions and download authorization.
Test validation separately
Cover file size, allowed media types, extension mismatches, malformed files and missing upload data. Do not trust a browser-provided MIME type or filename as proof of file content.
Use isolated storage
Configure a temporary test directory and ensure tests clean it up even when an assertion fails. Never let test code write to the application's production upload directory.
Test authorization
A valid file should not automatically be public. Verify that downloads enforce ownership or access rules and that storage paths cannot be manipulated through user input.
Include failure cases
Test unwritable directories, partial writes, duplicate names and cleanup after processing errors. These cases reveal operational defects that a happy-path upload test misses.