json87 B

Convert v2 Protobuf Expected JSON

Expected JSON semantic result for the schema-guided Protobuf decode. Stable P8 artifact p8-convert-protobuf-expected.

Conversion testing Serialization testing Schema / OpenAPI testing

Preview, first 6 linesjson

{
  "assetCount": 42,
  "contact": "creator@example.test",
  "id": "p8-convert-user"
}

Specifications

Fields: 3
Wire Format: protobuf
Delivery Mode: download-only
Controlled Failure: false
Provider: converter-v2
Provenance: Synthetic deterministic P8 fixture generated by generation/p8_content.py; seed namespace 2026082300
Fixture Reserve: convert-v2

Testing contract

Reference control

Scenario: Compare a decoded CreatorRecord with this JSON after applying lowerCamelCase field naming.
Expected result: All three values match exactly and no unknown field appears.

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

“Convert v2 Protobuf Expected JSON” is a deterministic Testaroo fixture for Conversion testing, Serialization testing, Schema / OpenAPI 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: 3 fields. 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("creator-record-expected.json") as f:
    data = json.load(f)
print(type(data), len(data))

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