Testing Files Generator is a tool for QA engineers and developers who need real files to test against - an upload form, a parser, anything that takes a file and has an opinion about it. You pick one of its 20+ formats and the size you want, and you get exactly that: ask for a 10 MB PDF and you get a PDF that a reader will open, at 10 MB to the byte. Every run also leaves a manifest saying what your system should do with each file, which is the part other generators leave to you. GUI + CLI
? What it can do
Hit an exact size, to the byte - ask for 10485761 bytes and get exactly that, never a silently rounded file.
Write 20+ real formats - a generated PNG opens in an image viewer, a DOCX opens in Word, a ZIP extracts. Not padded zeros with an extension.
Say what should happen to each file - the manifest carries an expected outcome, so your test reads the assertion instead of you writing it out.
Repeat itself byte for byte - same recipe and seed, same bytes, on any machine. Commit a small recipe instead of large binary fixtures.
Build a boundary set in one command - one byte under a limit, the limit itself, one byte over. That is where off by one errors live.
Produce ten thousand files at once - one command, one manifest, and sizes drawn from the seed.
Fill an archive for real - a ZIP that holds 200 documents, not a stub with the right extension.
Take settings per format - image dimensions, JPEG quality, PDF pages, spreadsheet rows and columns.
Fit into CI - an exit code for every ending, machine readable output, and nothing on standard output when a run fails.
Clean up after itself - verify tells you nothing moved, cleanup removes exactly what it wrote and nothing else.
Work completely offline - no account, no cloud, no telemetry, no update check. The command line binary has no network stack compiled into it at all.
Cost nothing and stay out of your way - GPL-3.0, and the files you generate are yours with no strings attached.