Novus Examples, Real, documented example files for testing

Zig Add

Zig function plus a unit test stub — realistic small module.

File: ZIG · Zig
Use case: Syntax highlightingCode parsing+1

Zig Errdefer

Zig errdefer SAMPLE for Zig language-server tests.

File: ZIG · Zig
Use case: Syntax highlightingCode parsing+1

Zig Hello

Zig hello-world for Zig language-server and highlighter tests.

File: ZIG · Zig
Use case: Syntax highlightingCode parsing+1

Preview of ZIP - All Members Deflate — Actual file preview for ZIP - All Members Deflate

A ZIP whose every member uses compression method 8 (deflate). Its twin holds byte-identical content under the other method, so an extractor, a size estimator, or a repacking pipeline can be compared on the same payload with only the storage method changed.

File: ZIP · Zip Structure · 3 members
Use case: Conversion testingCompression testing· Conversion set

ZIP - All Members Stored

A ZIP whose every member uses compression method 0 (stored). Its twin holds byte-identical content under the other method, so an extractor, a size estimator, or a repacking pipeline can be compared on the same payload with only the storage method changed.

File: ZIP · Zip Structure · 3 members
Use case: Conversion testingCompression testing· Conversion set

ZIP - Backslash Path Separators

Two members use a backslash as the path separator, which APPNOTE 4.4.17.1 forbids and which Windows-written archives contain anyway. Readers that split on '/' only will create files literally named 'data\config.json' in the extraction root instead of data/config.json.

File: ZIP · Zip Names · 4 members
Use case: Conversion testingError handling· Conversion set

ZIP - Bounded High Compression Ratio

A deliberately bounded compression-ratio fixture: 4474 bytes on disk expanding to exactly 4 MiB of zeros, roughly 937:1. It is not a decompression bomb - there is no nesting and no recursion, and the expanded size is a fixed 4 MiB - so it exercises a ratio guard or a streaming extractor's memory ceiling without being dangerous to open.

File: ZIP · Zip Payload · 2 members
Use case: Conversion testingCompression testing+1· Conversion set

ZIP - Case-Only Name Collision

Three members under docs/ whose names differ only in letter case. On ext4 they are three files; on NTFS or a default APFS volume they are one file written three times, and the last one silently wins. Each payload names its own casing so you can tell which survived.

File: ZIP · Zip Names · 4 members
Use case: Conversion testingError handling· Conversion set

ZIP - CP437 Legacy Name Encoding

The legacy twin: names encoded in IBM CP437 with the language-encoding flag clear, which is what the ZIP spec says an un-flagged name means. Decoding these bytes as UTF-8 produces mojibake or an outright decode error, which is exactly the bug this file is for.

File: ZIP · Zip Encoding · 3 members
Use case: Conversion testingEncoding detection· Paired fixture

ZIP - Data Descriptor (no signature)

The same streaming layout with the data descriptor's PK\x07\x08 signature omitted, which the spec permits and which breaks readers that scan for the signature instead of trusting the central directory. The central directory here carries the authoritative sizes and CRCs.

File: ZIP · Zip Structure · 3 members
Use case: Conversion testingError handling· Conversion set

ZIP - Data Descriptor (with signature)

A ZIP written the way a streaming writer must write one: general-purpose bit 3 is set, the local header carries CRC 0 and sizes 0, and the real values follow the compressed data in a data descriptor introduced by the optional PK\x07\x08 signature.

File: ZIP · Zip Structure · 3 members
Use case: Conversion testingError handling· Conversion set

ZIP - Data Descriptor (ZIP64 8-byte fields)

A streaming ZIP in ZIP64 form: the data descriptor's compressed and uncompressed sizes are 8 bytes each rather than 4. Readers that assume a fixed 16-byte descriptor desynchronise on the very next local header.

File: ZIP · Zip Structure · 3 members
Use case: Conversion testingError handling· Conversion set

ZIP - Deep Directory Tree

A ZIP archive — a file nested six directory levels deep. Deterministic (fixed member timestamps) and safe to extract anywhere.

File: ZIP · Zip · 7 members
Use case: Conversion testing

ZIP - Directories Implied by Member Paths

The same three-directory tree with no directory records at all — the parents exist only as path components inside member names. Extractors that create directories only when they see a directory record fail on this shape, which is what most command-line ZIP writers produce.

File: ZIP · Zip Structure
Use case: Conversion testing· Conversion set

ZIP - Directory Records Without a Trailing Slash

Directory records whose names do NOT end in a slash — the directory-ness is carried only by the MS-DOS attribute bit in the external attributes field. A reader that decides by name alone creates three empty files called project, project/src and project/data, and then cannot create the directories that have to replace them.

File: ZIP · Zip Structure
Use case: Conversion testingError handling· Conversion set

ZIP - Dot Segments in Member Paths

Member names carrying './' prefixes, an inner './' and one inner '../' that cancels the segment before it. Every path resolves inside the archive root, so this exercises a normaliser without being a traversal payload: docs/sub/../notes.md must land at docs/notes.md, not at docs/sub/notes.md and not outside the extraction directory.

File: ZIP · Zip Names · 4 members
Use case: Conversion testingError handling· Conversion set

ZIP - Empty Archive

A valid ZIP with zero entries — the empty-archive edge case for testing how unarchivers handle a container with nothing inside.

File: ZIP · Zip · 0 members
Use case: Conversion testing

ZIP - Empty Archive With a Comment

A valid ZIP with zero members whose end record still carries an archive comment - the combination that catches readers which treat 'no entries' as 'not an archive' and readers which look for the end record only in the last 22 bytes. Its group siblings are the same empty case in five other container formats.

File: ZIP · Empty · 0 members
Use case: Conversion testingError handling· Conversion set

ZIP - Explicit Directory Records

A ZIP that stores each directory as its own zero-length record with a trailing slash and the MS-DOS directory attribute set. Its group siblings hold the same tree with the directory records implied and with the trailing slash missing, which is the trio an extractor's mkdir logic has to survive.

File: ZIP · Zip Structure
Use case: Conversion testing· Conversion set

ZIP - Extended Timestamp and Unix UID/GID Extra Fields

The DOS timestamp in a ZIP header has 2-second resolution and no timezone, so Info-ZIP adds a 0x5455 extended timestamp and a 0x7875 uid/gid field. Here the uid/gid field appears in the local header only, matching what Info-ZIP actually writes, so a reader that reads extras from the central directory alone sees the timestamp but loses the ownership.

File: ZIP · Zip Metadata · 2 members
Use case: Conversion testingMetadata testing· Conversion set

ZIP - Flat

A ZIP archive — 3 files at the root, no directories. Deterministic (fixed member timestamps) and safe to extract anywhere.

File: ZIP · Zip · 3 members
Use case: Conversion testing

ZIP - Info-ZIP Unicode Path Extra Field

The third way a ZIP carries a non-ASCII name: an ASCII-safe name in the header plus an Info-ZIP Unicode Path extra field (0x7075) holding the real UTF-8 name and a CRC32 of the header name. A reader must prefer the extra field, but only while that CRC still matches the header name it was computed from.

File: ZIP · Zip Encoding · 3 members
Use case: Conversion testingEncoding detection+1· Conversion set

ZIP - Leading Non-Archive Bytes

397 bytes of readable text precede the first local file header, giving the layout of a self-extracting archive without shipping an executable stub. Readers that start at byte zero see garbage; readers that find the end-of-central-directory record and work backwards read all three members. Open the file in a text editor to read the prefix.

File: ZIP · Zip Payload · 3 members
Use case: Conversion testingError handling· Conversion set

ZIP - Long Archive Comment

A 512-byte archive comment pushes the end-of-central-directory record well away from the end of the file. Readers that seek to the last 22 bytes and expect the end signature there fail immediately; correct readers scan backwards for it, which is what the format requires.

File: ZIP · Zip Metadata · 2 members
Use case: Conversion testingError handling· Conversion set

Explore the test library

Filter the library

5297 results