Sample files for CI/CD pipelines
Fixtures for build, test and deployment pipelines, with checksums for verification.
Pipelines handle files constantly: artifacts are uploaded, caches are restored, archives are unpacked and configuration is parsed. When you write or debug a pipeline step, a file of known size and checksum tells you immediately whether the step did its job.
The published SHA-256 values let a job verify what it downloaded before using it.
Recommended files
| File | Size | Why this one | Download |
|---|---|---|---|
| 10 MB BIN samplesample-bin-10mb.bin | 10 MB10,485,760 bytes | Artifact upload and cache tests | Download BIN |
| 1 MB TAR samplesample-tar-1mb.tar | 1 MB1,048,576 bytes | Extraction steps | Download TAR |
| Sample Docker Compose YAMLsample-docker-compose.yaml | 744 B744 bytes | Configuration parsing | Download YAML |
| Sample customers SQL script (100 rows)sample-customers.sql | 19.3 KB19,777 bytes | Seeding a test database | Download SQL |
| 5 MB ZIP samplesample-zip-5mb.zip | 5 MB5,242,880 bytes | Archive artifact | Download ZIP |
Checklist
Pin and verify
When a job downloads a fixture, check its SHA-256 before use and fail the job if it differs.
Cache fixtures
Store downloaded files in the pipeline cache or an artifact repository so later runs do not depend on the network.
Test artifact size limits
Upload 10 MB and larger files as artifacts to find the limits and timing of your CI provider.
Test archive handling
Use the TAR and GZ samples to check the extraction steps of deployment scripts.
Guides
- How to create test files of any size
Commands for Linux, macOS and Windows that produce a file of an exact byte count, and when to use each.
- How to test file downloads
Completeness, integrity, speed, range requests and resume, each with a command you can run.
- File upload and download testing with Playwright
setInputFiles, file choosers, in-memory files, download assertions and API uploads, with working examples.
Related use cases
Frequently asked questions
- How do I verify a checksum in a shell step?
- Write the expected hash and file name to a file and run sha256sum --check against it. The command exits with an error if the file does not match.