QA testing scenarios

Each playbook pairs long-form QA context with stable deep links (?preset=..., bytes=, etc.). Link these from your team's runbooks so everyone regenerates identical fixtures instead of passing around zipped mystery files.

• 5 MB dummy PDF for upload-limit testing

  Generate a deterministic ~5 MiB Portable Document Format file to exercise storage tiers, multipart boundaries, antivirus queues, and “file too large” messaging — without scraping random PDFs from the web.

  Read scenario & presets→

• Exact-byte dummy files for API & storage QA

  Produce JSON, CSV, images, WAV, synthetic MP4/WebM shells, and more padded or trimmed to a precise byte footprint for boundary regressions.

  Read scenario & presets→

• Large padded CSV for import & ETL benchmarking

  Stress CSV parsers and upload routes with deterministic payloads — avoid inventing PHI in spreadsheets copied from staging.

  Read scenario & presets→

• Defensive MIME tests: mismatched signatures vs extensions

  Document benign QA workflows pairing extension checks with sniffers — never deceptive files aimed at humans.

  Read scenario & presets→

• ~24 MB synthetic PDF upload stress

  Provoke sluggish paths—chunked uploads, Axios defaults, multipart backpressure, antivirus sandboxes—without juggling multi-gigabyte objects during early regressions.

  Read scenario & presets→

• ~512 KB padded JSON for REST clients

  Exercise JSON.parse heavy paths without importing scrubbed-but-still-sensitive production dumps.

  Read scenario & presets→

• Team shareable generator links (preset query params)

  Encode MIME + sizing (or canned presets) in URLs — paste into runbooks instead of juggling shared drives.

  Read scenario & presets→