Product Instance: Invalid (JSON)
A product object that deliberately violates the product JSON Schema in five ways (out-of-range id, empty name, non-positive price, wrong boolean type, an extra property): the negative case for testing validator error reporting.
{
"product_id": 0,
"name": "",
"price": -5,
"in_stock": "yes",
"colour": "red"
}
Specifications
- Conforms To
- product.schema.json
- Valid
- false
- Violations
- product_id<1, empty name, price<=0, in_stock not boolean, extra property
Testing contract
Expected to fail- Scenario
- Exercise Product Instance: Invalid (JSON) in its schema workflow. A product object that deliberately violates the product JSON Schema in five ways (out-of-range id, empty name, non-positive price, wrong boolean type, an extra property): the negative case for testing validator error reporting.
- Expected result
- Report the intended validation failure (product_id<1, empty name, price<=0, in_stock not boolean, extra property); never silently treat it as a conforming input. top-level keys are product_id, name, price, in_stock, colour; selected values: {"product_id": 0, "price": -5}. Declared feature checks: conformsTo=product.schema.json; valid=False; violations=product_id<1, empty name, price<=0, in_stock not boolean, extra property. The declared comparison counterpart is data-rw-schema-valid; preserve the stated difference instead of expecting the container bytes to match.
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
“Product Instance: Invalid (JSON)” is a deterministic Testaroo fixture for Schema validation, Error handling. JSON Schema documents describing a data shape, for testing validators and schema-aware tooling.
Documented properties for this file: intentionally invalid. 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("product-invalid.json") as f:
data = json.load(f)
print(type(data), len(data))Generated by generation/data_realworld.py. Free for any use, no attribution required, license.
Related files
- ediJuniper Fitness and Clinic Administration: X12 837 claim whose service lines do not add up to the claim totalX12 837 claim whose service lines do not add up to the claim total for Juniper Fitness and Clinic Administration. The same single-claim interchange with one element changed: CLM02 reads 225.00 instead of 205.00. The two SV102 amounts are untouched at 120.00 and 85.00, so they still sum to 205.00 and disagree with the claim total by 20.00 USD. Segment counts, envelope control numbers and every other element are correct, so a structural validator passes the file and only the balance rule catches it.
- ymlAzure Pipelines, Intentionally InvalidAn intentionally invalid Azure Pipelines file: valid YAML that mixes top-level steps with a stages block, depends on an undeclared stage, and gives `pool` a bare string. For testing that a validator rejects it and reports all three faults.
- ymlCircleCI Config, Intentionally InvalidAn intentionally invalid CircleCI config: an unquoted `version: 2.10` that YAML loads as the float 2.1, a workflow referencing an undefined job, and a job with no execution environment. For testing that a validator rejects it and explains each fault.
- cwlCWL Workflow, Intentionally InvalidAn intentionally invalid CWL document: a nonexistent cwlVersion, an unknown class, a step consuming an output no step produces, and outputs given as a bare string. Four documented faults for a CWL validator to report.
- jsonCycloneDX 1.6 Minimal SBOM (One Component)The smallest CycloneDX document that is still valid: required metadata, one fictional component, and no dependencies array, for testing that a reader handles an SBOM with nothing optional present. Every package, version, hash and licence is fictional: the tree describes nothing real.
- jsonCycloneDX SBOM With Schema Violations: Intentionally InvalidAn intentionally invalid CycloneDX SBOM: the JSON parses, but bomFormat is missing, one component has no name, and a dependency references a bom-ref that no component declares. Every package, version, hash and licence is fictional: the tree describes nothing real.
