Convert v2 Protobuf Missing-Schema Controlled Failure
Valid wire bytes intentionally supplied without a matching schema so tools must preserve unknown field 15. Stable P8 artifact p8-convert-protobuf-missing-schema.
| property | expected |
|---|---|
| fields | 1 |
| validity | recoverable |
Specifications
- Fields
- 1
- Wire Format
- protobuf
- Delivery Mode
- download-only
- Controlled Failure
- true
- Provider
- converter-v2
- Provenance
- Synthetic deterministic P8 fixture generated by generation/p8_content.py; seed namespace 2026082300
- Fixture Reserve
- convert-v2
Testing contract
Expected to recover- Scenario
- Parse the wire stream without guessing a message type and preserve its unknown field.
- Expected result
- One length-delimited field 15 containing P8RAW is reported; no semantic name is invented.
What is a .pb file?
A .pb file holds Protocol Buffers binary data: Google's compact, schema-driven serialization where field numbers and wire types encode the message. Without the matching .proto schema the bytes are opaque, which makes it efficient but not self-describing.
How to use this file
Use an example .pb file to test protobuf decoders (with the matching schema), wire-format parsing, and protobuf tooling.
How to use this file for testing
“Convert v2 Protobuf Missing-Schema Controlled Failure” 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: 1 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.
Generated by generation/p8_content.py. Free for any use, no attribution required, license.
Related files
- orcConvert v2 ORC Employee Table SourceBinary orc source for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-source.
- csvConvert v2 ORC Expected CSVCsv semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-csv.
- jsonConvert v2 ORC Expected JSONJson semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-json.
- jsonAvro Schema Evolution - Backward-CompatibleThe compatible Avro record schema for reader/writer compatibility tests. Backward compatible for old records: nullable email is added with a null default.
- jsonAvro Schema Evolution - BaselineThe baseline Avro record schema for reader/writer compatibility tests. Reference writer schema: id and name are strings.
- jsonAvro Schema Evolution - BreakingThe breaking Avro record schema for reader/writer compatibility tests. Breaking relative to baseline: id changes to long and tenantId has no default.
