Skip to content
Novus Examples
docx37.3 KB

Pine Assembly Workshop: Work order (DOCX)

Work order (DOCX) for Pine Assembly Workshop. The shop paperwork for BUILD-1: 2 DESK due 2026-09-10, the 3 materials to issue at 50.40 USD, the 5 routing operations totalling 30 minutes, and a cost build-up that closes at 80.00 USD against a 80.00 USD standard, a zero variance. The PDF twin in the same directory carries the identical text.

Rendered preview of Pine Assembly Workshop: Work order (DOCX)

Rendered preview of the docx file (37.3 KB). Download above for the original.

Specifications

Document Set
manufacturing
Industry
manufacturing
Source Kit
inventory-manufacturing
Entity
Pine Assembly Workshop
Synthetic
true
As Of
2026-09-08
Work Order
BUILD-1
Quantity
2
Operations
5
Total Minutes
30
Order Cost
80.00
Variance
0.00
Lot
LOT-2026-0912
Renderer
python-docx
Paragraphs
12

Testing contract

Expected to pass
Scenario
Take the three tables in order and check that each one feeds the next.
Expected result
The material table totals 50.40, which is line 1 of the cost table; the routing totals 30 minutes, which at 37.00 an hour is line 2 at 18.50; and the cost table closes at 80.00 with a 0.00 variance against standard.

What is a .docx file?

DOCX is the default Microsoft Word format, an Office Open XML document packaged as a ZIP archive of XML parts, media, and relationships. It stores structured text, styles, tables, images, and metadata. It is the dominant format for editable word-processing documents.

How to use this file

Use an example DOCX to test Office Open XML parsing, text and style extraction, ZIP-package handling, and converters that render or transform Word documents.

How to use this file for testing

“Pine Assembly Workshop: Work order (DOCX)” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: DOCX · 38,239 bytes. 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.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

from docx import Document  # pip install python-docx

doc = Document("work-order-BUILD-1.docx")
for p in doc.paragraphs[:10]:
    print(p.text)

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