Facebook Pixel

What tests should be performed on photo uploading, viewing, and deletion?

Test a wedding photo gallery across valid uploads, invalid files, access permissions, interrupted requests, private viewing, and reliable storage cleanup.

What tests should be performed on photo uploading, viewing, and deletion?

Photo-gallery testing should cover the complete lifecycle of an image and the permissions around it. A successful upload demonstration is only the starting point. Verify that photos remain correct and accessible to the intended people through reloads, errors, and deletion.

Exercise uploads and processing failures

Upload representative supported images and confirm the resulting gallery records belong to the correct wedding. Check empty files, excessive size, unsupported formats, misleading extensions, and invalid image bytes.

Interrupt a transfer, let an upload URL expire, and repeat the finalization request. Confirm that errors are understandable and that retries do not create duplicate gallery items. Verify pending uploads do not appear as completed photos.

Test viewing as different users

Open the gallery as an organizer, an authorized member, and a user belonging to another wedding. Test direct image access as well as the page interface; hiding a card should not be the only access restriction.

Check empty states, pagination where implemented, mobile layout, loading failures, and image orientation. Reload after an upload to confirm that the displayed item comes from persisted records. Verify private images do not become publicly accessible through an unintended storage URL.

Verify deletion across both systems

Test authorized deletion and rejection of unauthorized requests. Confirm the application removes or retires the database record and deletes the corresponding stored object using the chosen lifecycle. R2's deletion documentation covers its object operations.

Simulate storage or database failure during deletion. The interface should represent the actual state and support recovery, rather than silently losing track of a still-accessible photo. Check that retrying deletion converges safely and that unrelated photos remain intact. Record the verified scenarios and remaining limitations before declaring the gallery increment complete.

Page controls can hide a photo while its storage URL remains accessible. Test the underlying read path to verify the intended privacy policy actually holds.

The application needs a recoverable state and retry strategy that reconciles the record with storage. It should not leave an unexplained broken card indefinitely.

That scenario verifies isolation between families. An authenticated user must not gain access to another wedding's private photos by changing identifiers or requesting direct image URLs.

Ready to master AI completely?

Want to upskill yourself, crack your next interview, and get your dream job? Join our comprehensive course to dive deeper with high-quality video tutorials, solve interview questions, and a premium community.