Live Updates & File Uploads

Testing Live Updates & Image Storage


Learning Objectives

  • You can distinguish an operation check from a transport or persistence check.
  • You can match a claim to the boundary an observation exercises.
  • You can identify which real dependency an observation must exercise.

Check publication order with a controlled commitment trace and image permissions with a denied-visitor read. The next three cases ask which observation supports each claim.

Match each claim to its evidence

The preceding chapters used a recording publisher, a bounded HTTP read and storage checks. Each observation supports a particular claim:

ClaimUseful observation
Publication follows commit.Controlled pending operation and recording publisher.
Older snapshots cannot replace newer state.Controlled read and event sequence.
SSE framing and cleanup work.One bounded real response, then cancellation and resource observations.
Unauthorized upload causes no write.Service check with recording storage.
Protected multipart routing and metadata uniqueness work.Actual route and PostgreSQL integration, with permitted and denied cases.

Use the real dependency when its behavior belongs to the claim. Use route checks for routing and browser journeys for connected interactions. Combine these with focused service checks to support a larger claim while retaining failures that identify the broken boundary.

Choose the additional evidence needed for a broader claim in the next three cases.

Together, these observations cover message formatting, resource cleanup and protected persistence while keeping failures focused enough to diagnose.

Check Your Understanding

  1. Which boundaries must an observation exercise to establish both delivery and persistence?
  2. A hub check passes but a browser receives no complete event. Which boundary should the next observation examine?
  3. A protected upload route passes its checks. What additional behavior would a browser journey need to observe?