Binary streams, partial downloads and system test stubs (BIN, CRDOWNLOAD, EXE, ISO)

Test raw binary upload handlers, byte-range resumable downloads, antivirus/firewall extension blockers, and disk-image signature checkers safely without hosting live executable code.

System and raw binary formats

Quality assurance teams regularly need to test how an upload form, API gateway, or cloud storage bucket reacts to untyped binary payloads (.bin), incomplete browser downloads (.crdownload), Windows executables (.exe), and optical disc images (.iso). However, hosting real executable binaries on a public website creates security risks and triggers automated browser Safe Browsing blocks.

SampleTestFiles solves both problems cleanly: we provide deterministic high-entropy BIN files in exact sizes from 1 KB to 1 GB, and we provide an in-browser Inert Stub Generator that synthesizes non-executable .exe (DOS MZ header + plain-text warning) and .iso (ECMA-119 CD001 primary volume descriptor at sector 16) files directly on your device.

FormatMIME typeSignature bytesDelivery & QA purposeAction
BIN (Raw Binary)application/octet-streamDeterministic PRNG byte streamTesting raw binary uploads, chunked transfers, and uncompressible bandwidth throughput from 1 KB to 1 GBBIN samples
EXE (Inert MZ Stub)application/x-msdownload4D 5A ('MZ')Testing upload denylists and magic-byte blockers using an inert, non-executable DOS MZ stub built in your browserGenerate .exe stub
ISO (Inert ISO-9660 Stub)application/x-iso9660-image01 43 44 30 30 31 ('\x01CD001' at 0x8000)Testing optical disc image signature detection with a 64 KB inert ISO-9660 header stub built in your browserGenerate .iso stub
CRDOWNLOADapplication/octet-streamPartial target file bytesSimulating users accidentally selecting an unfinished Chrome download in a file pickerBroken-file suite

How to test executable and binary upload filters safely

Frequently asked questions

Why are .exe and .iso files generated in the browser instead of hosted as static downloads?
Hosting downloadable .exe or .iso files on a public web server triggers Google Safe Browsing warnings and corporate firewall blocks. Building an inert header stub inside your browser gives you the exact 'MZ' or 'CD001' magic signature for upload-filter testing without risking security flags.
How do I test a .crdownload upload rejection?
Download any truncated fixture from /broken-files/ and rename its extension to .crdownload to verify that your frontend file input rejects incomplete browser downloads.

Engineering test checklist for binary streams, partial downloads and system test stubs (bin, crdownload, exe, iso)

When designing automated integration suites for other pipelines, QA engineers must validate three distinct layers: binary container framing, metadata extraction accuracy, and resource-bounded parsing under concurrent load.

Verification layerTarget assertion for otherRecommended test fixture or tool
1. Signature & MIME checkConfirm backend inspects leading magic bytes rather than trusting the client Content-Type header for other uploadsMagic-Byte File Inspector & Spoofed-Extension Fixtures
2. Boundary byte sizesTest minimum valid header size, 1 MB default proxy limit, 10 MB application ceiling, and 50 MB+ streaming transfersSize Buckets (1 KB–1 GB) & In-Browser Generator
3. Corrupt payload handlingVerify that truncated streams or malformed headers in other return HTTP 400/422 instead of crashing the workerBroken-File QA Suite & errors-400.json
4. Checksum reproducibilityAssert that round-trip storage in cloud object storage preserves the exact byte length and SHA-256 digestSHA-256 Checksum Directory

Common failure points in other ingestion workflows