Skip to content
Novus Examples
json2.3 KB

Pine Assembly Workshop — Numeric expected results

Numeric expected results for Pine Assembly Workshop. Exact table counts, metric formulas, 6 chart points and three negative-test outcomes. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

Data import
Preview, first 50 linesjson
{
  "schemaVersion": 1,
  "kitId": "business-inventory-manufacturing",
  "asOf": "2026-09-08",
  "tableCounts": {
    "parts": 6,
    "bom": 6,
    "movements": 24,
    "suppliers": 2,
    "procurement": 8,
    "production_orders": 4,
    "material_requirements": 12,
    "routes": 4,
    "shipments": 16,
    "vehicles": 4,
    "shipment_exceptions": 3
  },
  "primaryKeyDuplicates": 0,
  "foreignKeyFailures": 0,
  "metrics": [
    {
      "id": "movements-received",
      "label": "Units received",
      "value": 96.0,
      "unit": "units",
      "calculation": "Sum movements.received over the included records.",
      "formula": {
        "op": "sum",
        "table": "movements",
        "column": "received"
      }
    },
    {
      "id": "movements-issued",
      "label": "Units issued",
      "value": 72.0,
      "unit": "units",
      "calculation": "Sum movements.issued over the included records.",
      "formula": {
        "op": "sum",
        "table": "movements",
        "column": "issued"
      }
    },
    {
      "id": "bom-count",
      "label": "Assembly relationships",
      "value": 6.0,
      "unit": "records",
      "calculation": "Count unique bom_id values in bom.",
… 111 lines total: download for the full file.

Specifications

Kit
inventory-manufacturing
Industry
manufacturing
Schema Version
1
Synthetic
true
As Of
2026-09-08

Testing contract

Reference control
Scenario
Use numeric expected results in the Pine Assembly Workshop bill-of-materials, stock-movements, reorder-planning, procurement, production-planning, shipments, delivery-exceptions workflow.
Expected result
Exact table counts, metric formulas, 6 chart points and three negative-test outcomes. Units received=96.00 units; Units issued=72.00 units; Assembly relationships=6.00 records.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Pine Assembly Workshop — Numeric expected results” 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: JSON · 2,328 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.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import json

with open("expected-results.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

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