Skip to content
Novus Examples
csv368 B

Ember Lane Pizza — Intentionally invalid review import

Intentionally invalid review import for Ember Lane Pizza. 4 data rows, 5 columns and 0 expected accepted rows.

Preview, first 6 linescsv
Source,Date,Rating,Review,Location
,2026-08-15,5,Friendly service and a well prepared order.,Main kitchen
Website feedback,not-a-date,5,Friendly service and a well prepared order.,Main kitchen
Website feedback,2026-08-15,6,Friendly service and a well prepared order.,Main kitchen
Website feedback,2026-08-15,-1,Friendly service and a well prepared order.,Main kitchen

Specifications

Kit
restaurant-pizzeria
Industry
food-service
Schema Version
1
Synthetic
true
As Of
2026-09-08
Rows
4
Columns
5
Encoding
UTF-8

Testing contract

Expected to fail
Scenario
Use intentionally invalid review import in the Ember Lane Pizza purchasing, price-history, menu-costing, inventory, sales, reviews, modifiers, refunds, reservations, staffing, stock-movements, menu-pricing workflow.
Expected result
4 data rows, 5 columns and 0 expected accepted rows.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Ember Lane Pizza — Intentionally invalid review import” is a deterministic Novus Examples fixture for Data import, Error handling. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 4 rows · 5 columns · UTF-8. 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 pandas as pd

df = pd.read_csv("invalid-reviews.csv")
print(df.head())
print(df.dtypes)

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