Prepare a file test card with agreed limits
Record permitted types, count, size and the actual environment's supported limits. Select files just below, at and above the agreed boundary where its meaning is defined. Avoid unreasonably large files that burden the service.
Give the exercise a unique case number and put a harmless marker inside the file. Recipients can then distinguish it from an old file with the same name. Do not use real customer documents, malicious code or private information.
Test refusal without losing useful input
Select an allowed file, then a harmless file outside the agreed format policy. Check that visitors receive useful guidance and can replace it. Browser filtering is not the same decision as receiving validation.
Have the responsible developer demonstrate handling of missing or conflicting format evidence in the test environment. A filename alone must not supply acceptance. This is authorised testing of your own implementation.
| Exercise | Expected outcome | Evidence |
|---|---|---|
| Allowed test file | Received under the agreed model | Marker and correct case relationship |
| Size boundary | Included or refused according to policy | Accurate feedback at the right boundary |
| Disallowed format | Refusal and correction route | No falsely complete case |
| Interrupted transfer | Interruption understood and handled | Accurate state and retry |
| Different test recipient | No unauthorised download | Access decision on the actual file route |
Interrupt transfer and try again
Simulate a controlled transfer failure without affecting production. Note whether the text case already exists and the file is incomplete. Confirmation must describe what succeeded, rather than complete evidence when the attachment is missing.
Retry and trace the association. Check that old partial objects are not confused with the new file or exposed accidentally. Abandoned uploads need an agreed cleanup procedure and owner.
Open the file as the intended recipient
Find the test case at its agreed destination and open the attachment using the intended recipient role. Compare its marker, name where relevant and association. If delivery uses expiring links, test expiry and the appropriate next step too.
Test mobile and keyboard selection, correction and replacement. Report case number, checks, actually received evidence, uncertainty and retest. Clean up test material under the plan. This exercise does not guarantee future file safety or delivery.