Skip to content
Novus Examples
zip2.3 KB

ZIP Containing tar, tgz, txz and tbz2

One ZIP holding the same two-member tar in four containers - plain, gzip, xz and bzip2 - so a recursive lister can be checked on four codecs in one pass. The already-compressed members are stored rather than deflated, which is what a competent writer does and what a naive one does not.

Archive contents — 5 entrieszip
  • README.txt
  • plain.tar
  • gzipped.tgz
  • xz-compressed.txz
  • bzip2-compressed.tbz2

Specifications

Seed
20260807
Members
5
Nested Archives
4
Nesting Depth
2
Inner Members
2
Outer Method
already-compressed members are STORED; the plain tar is deflated
Inner Content Identical
true

Testing contract

Expected to pass
Scenario
List the outer archive, then descend into each nested member and list that.
Expected result
Four nested archives are found and each yields the same 2 members, README.txt and data/records.csv, with identical bytes; nesting stops at depth 2.

What is a .zip file?

ZIP is a widely supported archive format that bundles multiple files and directories into one container, typically with per-file DEFLATE compression and a central directory index. It supports random access to individual entries without decompressing the whole archive. It underlies many document formats such as DOCX and EPUB.

How to use this file

Use an example ZIP to test archive extraction, central-directory parsing, per-entry decompression, and protection against path-traversal (zip-slip) during unpacking.

How to use this file for testing

“ZIP Containing tar, tgz, txz and tbz2” is a deterministic Novus Examples fixture for Conversion testing, Compression testing. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.

Documented properties for this file: seed 20260807. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Archive fixtures are documented down to their member list (shown on this page) and are deliberately safe — no zip bombs, executables, or hidden payloads. Test extractors against nested, unicode, empty, and encrypted variants.

Code examples

unzip -l zip-of-tar-family.zip     # list members
unzip zip-of-tar-family.zip -d out/  # extract

Generated by generation/archives_p7.py. Free for any use, no attribution required — license.