csv
53 BSynth Batch 16 (CSV)
Deterministic synthetic CSV batch 16 for bulk-import smoke tests.
- File
- CSV · Synth · 5 rows
- Use case
- Data importCSV parsing· 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 46 of 53; 24 results per page.
json
345 BSynth Batch 16 (JSON)
Deterministic synthetic JSON batch 16 for bulk-import smoke tests.
- File
- JSON · Synth · 5 records
- Use case
- Data importJSON parsing· Conversion set
csv
53 BSynth Batch 17 (CSV)
Deterministic synthetic CSV batch 17 for bulk-import smoke tests.
- File
- CSV · Synth · 5 rows
- Use case
- Data importCSV parsing· Conversion set
json
345 BSynth Batch 17 (JSON)
Deterministic synthetic JSON batch 17 for bulk-import smoke tests.
- File
- JSON · Synth · 5 records
- Use case
- Data importJSON parsing· Conversion set
csv
53 BSynth Batch 18 (CSV)
Deterministic synthetic CSV batch 18 for bulk-import smoke tests.
- File
- CSV · Synth · 5 rows
- Use case
- Data importCSV parsing· Conversion set
json
345 BSynth Batch 18 (JSON)
Deterministic synthetic JSON batch 18 for bulk-import smoke tests.
- File
- JSON · Synth · 5 records
- Use case
- Data importJSON parsing· Conversion set
csv
53 BSynth Batch 19 (CSV)
Deterministic synthetic CSV batch 19 for bulk-import smoke tests.
- File
- CSV · Synth · 5 rows
- Use case
- Data importCSV parsing· Conversion set
json
345 BSynth Batch 19 (JSON)
Deterministic synthetic JSON batch 19 for bulk-import smoke tests.
- File
- JSON · Synth · 5 records
- Use case
- Data importJSON parsing· Conversion set
csv
54 BSynth Batch 20 (CSV)
Deterministic synthetic CSV batch 20 for bulk-import smoke tests.
- File
- CSV · Synth · 5 rows
- Use case
- Data importCSV parsing· Conversion set
json
346 BSynth Batch 20 (JSON)
Deterministic synthetic JSON batch 20 for bulk-import smoke tests.
- File
- JSON · Synth · 5 records
- Use case
- Data importJSON parsing· Conversion set
log
2.9 KBSyslog Messages: RFC 3164 (log)
A BSD-style syslog (RFC 3164) sample: timestamp, host, process and PID, then the message, across sshd, cron, kernel, nginx, and application entries. A fixture for testing syslog parsers and forwarders.
- File
- LOG · Logs
- Use case
- Log parsingObservability
json
827 BT bokeh warm: outpaint boundary record
Where the original view of abstract warm bokeh lights out of focus, dark background landed inside the expanded frame, as JSON: the rectangle 0,192 to 512,704 in a 512x704 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.
- File
- JSON · Outpaint Borders
- Use case
- Inpainting· Conversion set
json
826 BT tex brick: outpaint boundary record
Where the original view of flat red brick wall landed inside the expanded frame, as JSON: the rectangle 0,0 to 512,512 in a 512x704 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.
- File
- JSON · Outpaint Borders
- Use case
- Inpainting· Conversion set
json
830 BT tex linen: outpaint boundary record
Where the original view of close up woven linen fabric texture, natural fibres landed inside the expanded frame, as JSON: the rectangle 96,96 to 608,608 in a 704x704 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.
- File
- JSON · Outpaint Borders
- Use case
- Inpainting· Conversion set
tsv
473 BTab-Separated Values (TSV)
A tab-separated values file with a header and 20 rows, for testing TSV parsing and delimiter handling.
- File
- TSV · CSV · 20 rows
- Use case
- CSV parsing
csv
420 BTern Client Services: 1099-NEC shaped recipient list
1099-NEC shaped recipient list for Tern Client Services. 2 recipients with every box the slips print. box_1 sums to 2880.00 USD, which is the control_total_box_1 value carried on every row, and the box_6 column is empty on both rows because neither payee has a state identification number. The third contractor is absent by design: WRK-02 files a W-8BEN shaped certificate and is reported on the 1042-S shaped statement.
- File
- CSV · Tax Filings · 2 rows
- Use case
- Data importCSV parsing· Paired fixture
json
1.1 KBTern Client Services: 1099-NEC shaped recipient list JSON
1099-NEC shaped recipient list JSON for Tern Client Services. The same 2 recipients with the control total hoisted out of the rows and into the document, where it belongs, so the same check can be run against a single authoritative value rather than a value repeated on every row.
- File
- JSON · Tax Filings · 2 records
- Use case
- Data importJSON parsing· Paired fixture
csv
420 BTern Client Services: 1099-NEC shaped recipient list whose boxes do not reach the control total
1099-NEC shaped recipient list whose boxes do not reach the control total for Tern Client Services. The same 2 recipients with one number changed: WRK-03 box_1 reads 1820.00 instead of 1920.00. box_1 now sums to 2780.00 against the 2880.00 that both rows still carry as control_total_box_1, a shortfall of 100.00 USD. box_7 was moved with box_1 so the row stays internally consistent and only the control total catches it.
- File
- CSV · Tax Filings · 2 rows
- Use case
- Data importCSV parsing+1· Conversion set
csv
267 BTern Client Services: Amendment register
Amendment register for Tern Client Services. Two rows, one per varied clause, each carrying the previous value and the new one so a reader can reconstruct the agreement as it stood on any date. Clause 4.1 moves from 250.00 to 400.00 and clause 5.1 from ten to fifteen business days for one statement of work only.
- File
- CSV · Contracts Agreements · 2 rows
- Use case
- Data importCSV parsing
csv
2.2 KBTern Client Services: Clause index
Clause index for Tern Client Services. Every sub-clause of the three agreements in this set as one row: 57 rows across 3 documents, with the clause number, the heading it sits under, the clauses it refers to and its character count. 16 rows carry at least one cross-reference and every one of those resolves to a clause that exists in the same document.
- File
- CSV · Contracts Agreements · 57 rows
- Use case
- Data importCSV parsing· Conversion set
csv
2 KBTern Client Services: Contact export in the semicolon dialect
Contact export in the semicolon dialect for Tern Client Services. The same 8 contacts written with a semicolon delimiter. The billing_address field is still quoted because it contains newlines, but the tags field is now bare: "billing,renewals" needs no quotes when the delimiter is a semicolon, so the same value is quoted in contacts-export.csv and unquoted here. The file has 33 physical lines.
- File
- CSV · Professional Services Billing · 8 rows
- Use case
- Data import· Conversion set
csv
2 KBTern Client Services: Contact export with quoted fields
Contact export with quoted fields for Tern Client Services. 8 contacts in 33 physical lines, because every billing_address is a four-line address held in one quoted field. The addresses also contain commas, the notes contain doubled double-quote characters where a quotation appears, and the tags field holds the comma-separated value "billing,renewals" inside quotes. Every one of those is correctly escaped RFC 4180.
- File
- CSV · Professional Services Billing · 8 rows
- Use case
- Data import· Conversion set
json
2.8 KBTern Client Services: Contract reconciliation identities
Contract reconciliation identities for Tern Client Services. 6 named identities with the figures behind each one, including the two places this set deliberately holds different numbers for the same hours: 100.00 USD billed and 60.00 USD paid per hour, and accepted allocation against billed time on PROJECT-1. The deliberate defect and its measured shortfall of 50.00 USD are listed separately.
- File
- JSON · Contracts Agreements
- Use case
- Data importJSON parsing
csv
1.7 KBTern Client Services: Contract register
Contract register for Tern Client Services. 11 agreements across five document types with their effective dates, terms, expiry dates, notice deadlines and values. The three rows whose value_basis is "not to exceed" sum to 9,000.00 USD, the liability cap the master agreement states at clause 10.2. 2 rows carry an empty value because the document has no monetary value, and 2 carry an empty file because no rendering of that contractor agreement ships in this set.
- File
- CSV · Contracts Agreements · 11 rows
- Use case
- Data importCSV parsing· Paired fixture