Testing private export access from request to eventual deletion

Goal

Follow a private export through generation, retrieval, expiry, and cleanup. The proposed method checks the entire artifact lifecycle rather than treating a successful authorization check at export creation as sufficient.

Prerequisites

Use synthetic records in an isolated service, a local artifact store, an owner account, and an unrelated account. Define who may request, list, download, and delete exports at each lifecycle stage.

Steps

1. Request an export as the permitted account and verify its synthetic contents. Record artifact identifiers and status transitions without placing generated download credentials in the test report.

2. Using the unrelated account, test the application’s supported listing and retrieval paths for that same artifact. Inspect metadata exposure separately from access to the full exported contents.

3. Change the owner’s access while a separate export is pending. Apply the documented policy independently to job completion and later download; do not derive either expectation from creation permission alone.

4. Advance the fixture through its supported expiry or deletion mechanism. Recheck direct retrieval and any alternate application download route, using the known synthetic artifact identifier.

5. After fixing a mismatch, rerun the owner’s valid retrieval and the denied lifecycle cases. Confirm that the test observes actual bytes or their absence, not only a user-interface button.

Expected result

A useful report shows the authorized principal and expected visibility for each artifact state, including metadata and content as distinct observations.

Limits and test basis

This article proposes application-level checks only. Storage-provider access rules, intermediary caches, and external sharing features need separate authorized tests where those components are present. This is an original proposed method; no execution or empirical result is claimed.