Shipping Manifests · File Download

Download handling both ways it appears in the wild: static files, and backend-generated files with a real Content-Disposition header.

Sign for your crates. Static manifests always ship; the live waybills need the backend.

File Download is a medium Data & Files challenge on Fun UI Playground. Download handling both ways it appears in the wild: static files, and backend-generated files with a real Content-Disposition header. It needs the site’s live backend for real HTTP behavior. Every interactive element carries a stable id and data-testid prefixed with “download-”, and the techniques it exercises are download events, assert filenames, attachment headers, read downloaded content.

At a glance

Category
Data & Files
Difficulty
medium
Teaches
download events · assert filenames · attachment headers · read downloaded content
Backend
Needs the live /api backend
Locators
Stable id and data-testid, prefixed download-

Selectors on this page

LocatorWhat it is
#download-staticStatic manifests: links inside #download-static → /downloads/manifest-001.txt, waybills.csv, cargo.json
#download-liveLive waybills (backend required): links inside #download-live → /api/download/waybill.txt etc., served with Content-Disposition: attachment

Frequently asked questions

How do I assert a file download in an automated test?

Wait for the download event, then assert the suggested filename and — for the static manifests in #download-static — the contents byte for byte. The live links in #download-live come from the backend with a real Content-Disposition: attachment header.

What happens if the backend is offline?

The static manifests (/downloads/manifest-001.txt, waybills.csv, cargo.json) always ship, and the live section shows an offline notice instead of broken links — so a download test still runs without /api.

More Data & Files

Updated

Fun UI Playground — all challenges, bug hunts, getting started, glossary, about.