27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# Fixture policy
|
|
|
|
## Allowed
|
|
|
|
- Small, synthetic, deterministic files created specifically for tests.
|
|
- Sanitized fragments whose provenance and redistribution permission are recorded.
|
|
- Malformed, missing-field, duplicate, moved, unmounted, unusual-path, invalid-encoding,
|
|
oversized-boundary, symlink, traversal, and shell-metacharacter cases.
|
|
- Temporary integration state created under a test-owned directory and removed afterward.
|
|
|
|
## Forbidden
|
|
|
|
- Live tokens, cookies, account identifiers, device identifiers, personal paths, save
|
|
files, complete personal libraries, crash dumps with private data, or proprietary
|
|
launcher databases copied wholesale.
|
|
- Network access in unit or contract tests.
|
|
- Fixtures whose expected result depends on the developer's username, UID, home path,
|
|
locale, clock, network, mount layout, or installed games.
|
|
|
|
## Review and storage
|
|
|
|
Every fixture directory contains a README stating its origin, license/permission,
|
|
sanitization, parser behavior being tested, and whether it may be redistributed. Binary
|
|
fixtures require a size justification and checksum. Secrets scanners and adversarial
|
|
tests treat fixtures as hostile input, not trusted code or shell text.
|
|
|