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 21 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
You are testing software that accepts files from people. Sooner or later you need:
- a PDF of exactly 10 MB, to find out whether the upload limit is real
- the three files that sit either side of that limit, to catch off by one errors
-10,000 log files, to see what the nightly job does when the folder is big
- a ZIP that genuinely holds 200 documents, not a stub with the right extension
- a 4 GB file, without keeping a 4 GB file in your repository
Features
- Generate documents: pdf, docx (Word), xlsx (Excel), pptx (PowerPoint)
- Generate images: png, jpg, bmp, gif, ico, svg
- Generate text: txt, md, csv, json, xml, html, log
- Generate archives: zip, targz (.tar.gz)
- Generate audio: wav
- Create one file or thousands of them
- Full GUI + CLI
- Ask for size in Bytes, KB, MB, GB
- Generate archives with real files inside them
- Repeat itself byte for byte - same recipe and seed, same bytes, on any machine. Commit a small recipe instead of large binary fixtures.
- 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.
- Take settings per format - image dimensions, JPEG quality, PDF pages, spreadsheet rows and columns.
- Clean up after itself - verify tells you nothing moved, cleanup removes exactly what it wrote and nothing else.
- 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.