json
155 BConfig: Cors Origins (JSON)
Tiny SAMPLE JSON config fixture (cors-origins) for parser and twin tests.
- File
- JSON · Config
- Use case
- Config parsingEditor testing· Conversion set
Explore the test library
Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.
1255 results
Page 11 of 53; 24 results per page.
env
73 BConfig: Database Pool (ENV)
Tiny SAMPLE ENV config fixture (database-pool) for parser and twin tests.
- File
- ENV · Config
- Use case
- Config parsingEditor testing· Conversion set
ini
81 BConfig: Database Pool (INI)
Tiny SAMPLE INI config fixture (database-pool) for parser and twin tests.
- File
- INI · Config
- Use case
- Config parsingEditor testing· Conversion set
yaml
100 BConfig: K8S Resource Snippet (YAML)
Tiny SAMPLE YAML config fixture (k8s-resource-snippet) for parser and twin tests.
- File
- YAML · Config
- Use case
- Config parsingEditor testing· Conversion set
ini
59 BConfig: Logging Levels (INI)
Tiny SAMPLE INI config fixture (logging-levels) for parser and twin tests.
- File
- INI · Config
- Use case
- Config parsingEditor testing· Conversion set
yaml
65 BConfig: Rate Limit (YAML)
Tiny SAMPLE YAML config fixture (rate-limit) for parser and twin tests.
- File
- YAML · Config
- Use case
- Config parsingEditor testing· Conversion set
toml
73 BConfig: Redis Cache (TOML)
Tiny SAMPLE TOML config fixture (redis-cache) for parser and twin tests.
- File
- TOML · Config
- Use case
- Config parsingEditor testing· Conversion set
yaml
72 BConfig: Redis Cache (YAML)
Tiny SAMPLE YAML config fixture (redis-cache) for parser and twin tests.
- File
- YAML · Config
- Use case
- Config parsingEditor testing· Conversion set
env
99 BConfig: Smtp Relay (ENV)
Tiny SAMPLE ENV config fixture (smtp-relay) for parser and twin tests.
- File
- ENV · Config
- Use case
- Config parsingEditor testing· Conversion set
orc
1.5 KBConvert v2 ORC Employee Table Source
Binary orc source for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-source.
- File
- ORC · P8 Convert · 5 rows
- Use case
- Conversion testingData engineering+1· Conversion set
csv
434 BConvert v2 ORC Expected CSV
Csv semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-csv.
- File
- CSV · P8 Convert · 5 rows
- Use case
- Conversion testingData engineering+1· Conversion set
json
977 BConvert v2 ORC Expected JSON
Json semantic reference for the five-row P8 employee conversion table, preserving ids, names, departments, booleans, and scores. Stable P8 artifact p8-convert-orc-json.
- File
- JSON · P8 Convert · 5 rows
- Use case
- Conversion testingData engineering+1· Conversion set
pb
41 BConvert v2 Protobuf Creator Record
Valid Protobuf wire record with string, uint32, and string fields for schema-guided decoding. Stable P8 artifact p8-convert-protobuf-source.
- File
- PB · P8 Convert · 3 fields
- Use case
- Conversion testingSerialization testing+1· Conversion set
json
87 BConvert v2 Protobuf Expected JSON
Expected JSON semantic result for the schema-guided Protobuf decode. Stable P8 artifact p8-convert-protobuf-expected.
- File
- JSON · P8 Convert · 3 fields
- Use case
- Conversion testingSerialization testing+1· Conversion set
pb
7 BConvert 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.
- File
- PB · P8 Convert · 1 field
- Use case
- Conversion testingSerialization testing+1· Conversion set
proto
128 BConvert v2 Protobuf Schema Companion
Proto3 schema companion declaring the three fields used by the binary creator record. Stable P8 artifact p8-convert-protobuf-schema.
- File
- PROTO · P8 Convert · 3 fields
- Use case
- Conversion testingSerialization testing+1· Conversion set
csv
560 BCopper Oven Bakery: Allergen matrix
Allergen matrix for Copper Oven Bakery. 4 menu items across 18 columns: the fourteen listed allergens plus a count and a sources column naming the ingredient behind every Y. Derived from the recipe lines, so a dish whose recipe contains a dairy ingredient reads Y under milk. 4 of 4 dishes declare at least one allergen.
- File
- CSV · Restaurant Costing · 4 rows
- Use case
- Data importCSV parsing· Paired fixture
csv
462 BCopper Oven Bakery: Allergen matrix missing a menu item
Allergen matrix missing a menu item for Copper Oven Bakery. Intentionally incomplete. 3 rows where the recipes cost 4 menu items. MENU-04 (Sweet butter roll) has no row, although it has costed recipe lines in plate-costs.csv and sales in sales-mix-pmix.csv. Its correct row would declare: cereals_gluten: Bread Flour; milk: Butter.
- File
- CSV · Restaurant Costing · 3 rows
- Use case
- Data importError handling+1· Paired fixture
csv
719 BCopper Oven Bakery: Allergen menu as data
Allergen menu as data for Copper Oven Bakery. 4 rows and 21 columns: the menu item id, the printed section, the menu price, the 14 allergen columns, the declared count and the ingredient sources. 4 of 4 dishes declare at least one allergen. Joins to printed-menu.pdf and to plate-costs.csv on menu_item_id.
- File
- CSV · Restaurant Menus · 4 rows
- Use case
- Data importCSV parsing· Paired fixture
csv
619 BCopper Oven Bakery: Allergen menu missing a dish on the menu
Allergen menu missing a dish on the menu for Copper Oven Bakery. Intentionally incomplete. 3 rows where allergen-menu.csv has 4. MENU-01 Yeasted loaf is printed on printed-menu.pdf at 7.50 CAD and declares 1 allergen in the costing folder, and it has no row here. The remaining rows are correct.
- File
- CSV · Restaurant Menus · 3 rows
- Use case
- Data importError handling+1· Paired fixture
csv
2.4 KBCopper Oven Bakery: Cleaning schedule
Cleaning schedule for Copper Oven Bakery. 18 tasks across 6 areas and 11 columns, with frequency in days, the responsible role, the chemical and its contact time, the last completion date and a next-due date that is exactly last_completed plus frequency_days. 4 task(s) are overdue at the period end.
- File
- CSV · Restaurant Costing · 18 rows
- Use case
- Data importCSV parsing
json
5.5 KBCopper Oven Bakery: Cost of goods sold document
Cost of goods sold document for Copper Oven Bakery. The same statement as JSON, listing all 24 purchase ids it consumed so the total can be checked against the shared purchases table by id. Totals: opening 1479.58, purchases 2420.01, closing 3276.15, cost of goods sold 623.44 CAD.
- File
- JSON · Restaurant Costing · UTF-8
- Use case
- Data importJSON parsing+1· Conversion set
csv
671 BCopper Oven Bakery: Cost of goods sold that contradicts the count sheet
Cost of goods sold that contradicts the count sheet for Copper Oven Bakery. Intentionally inconsistent. Row 3 reports a closing count of 102.00 each for ING-03 (Eggs), the counted figure with the last two whole digits transposed, where inventory-count-sheet.csv, inventory-variance.xlsx and cogs-report.json all count 120.00 each. Every derived value follows the wrong count, so the file is internally consistent and its total of 629.74 CAD differs from the correct 623.44 CAD by 6.30 CAD.
- File
- CSV · Restaurant Costing · 7 rows
- Use case
- Data importError handling+1· Conversion set
csv
746 BCopper Oven Bakery: Credit note lines CSV
Credit note lines CSV for Copper Oven Bakery. 2 credit lines, one per note. CN-BAK-7001 credits 4 units for the short delivery and agrees with the goods-received note. CN-BAK-7002 credits 5 units where GRN-BAK-2004 records only 3 returned, an overstatement of 9.88 CAD net.
- File
- CSV · Procure To Pay · 2 rows
- Use case
- Data importCSV parsing