Test file presets, one set for each testing question

A preset is a whole set of test files designed around one question, with a manifest saying how your system should react to each file. You pick the question, the tool builds the set. Each preset has its own page with what it usually finds, what is in the set and every setting it takes.

Empty and minimal

Does a file that is valid and as small as the format allows get through?

empty-and-minimal
File name handling

Will my system store, show and give back a file name it did not expect?

filename-handling
Size boundaries

Is a size limit enforced exactly where it is declared?

size-boundaries
Tabular import

Does my table import survive what real tools export?

tabular-import
Text encoding

Does my reader know which encoding a file is in, or is it guessing?

text-encoding
Upload validation

Does my upload form take what it should and turn the rest away?

upload-validation

How is a preset different from a recipe?

Underneath, it is not. A preset is a recipe the tool writes for you from a few settings. tfg preset eject prints that recipe so you can keep it next to your tests and edit it, and a recipe of your own can build on a preset with one line, extends: preset: followed by its id.

tfg preset list
tfg preset show size-boundaries
tfg preset eject size-boundaries > my.yaml

Can I trust the defaults?

For the files, yes. For a number only your system knows, such as the limit of an upload form, a default is a placeholder of ours, and the tool says so every time it uses one. The page of each preset marks those settings, and tfg preset show says it before anything is written.