OFFLINE-BEHAVIOR TEST SHEET
Prepared October 3, 2026 | Yenra
Guide: https://yenra.com/macromedia-central/
Purpose: test explicit promises about cached reading, local drafts and remote
confirmation. This is a modern design exercise inspired by application history,
not a Macromedia Central configuration or runtime test.

Application/build/browser or runtime:
Tester/date/test device:
Feature and promised user outcome:
Data source and source timestamp meaning:
Freshness policy, units and reason for the chosen threshold:
Test account and disposable data (no credentials):

For EACH case, record initial state, action, expected result, actual result,
visible content/status/timestamp, pass/fail and evidence location.

Required cases:
1. Previously loaded data; network unavailable; reopen saved view.
2. Empty cache; network unavailable; open same view.
3. Saved data passes the chosen freshness threshold.
4. Connectivity returns; endpoint returns a successful response.
5. Connectivity returns; endpoint times out or returns an error.
6. If drafts are promised: create locally, close and reopen before reconnecting.
7. If writes are queued: interrupt before and after receipt by the server;
   retry and check for duplicate effects, account changes and edit conflicts.

Worked example (invented times/policy; not weather safety guidance):
- Retrieve forecast at 09:00.
- Offline at 09:20; show saved forecast and original time.
- Freshness threshold = 60 minutes.
- At 10:15, age = 75 minutes; show that threshold is exceeded.
- Reconnect at 10:20; request refresh while keeping saved content available.
- Replace content and timestamp only after a successful response.
- On failure, keep old timestamp and provide a retry route.

Repair owner / next action:
Retest steps / result / remaining limits:
Related implementation reference:
https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Offline_and_background_operation