Skip to content
Novus Examples
csv415 B

Juniper Workspace Cloud: Capitalisation table

Capitalisation table for Juniper Workspace Cloud. The 4 holdings split into nominal and premium with a total row. Only MEM-04 carries premium, 14,400.00 USD, because only the 2026-05-18 allotment was priced above nominal, at 0.25 against 0.01. The percentages are apportioned by largest remainder and sum to exactly 100.0000.

csv

text/csv

415 B
Document Set
corporate
Industry
software
Source Kit
saas-subscriptions
Entity
Juniper Workspace Cloud
Synthetic
true
As Of
2026-09-08

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
corporate
Industry
software
Source Kit
saas-subscriptions
Entity
Juniper Workspace Cloud
Synthetic
true
As Of
2026-09-08
Rows
5
Members With Premium
1
Percent Total
100.0000

Testing contract

Expected to pass
Scenario
Check that nominal plus premium equals amount paid on every row and in the total.
Expected result
Every row balances, three rows have zero premium, and the total row reads 6000.00 nominal plus 14400.00 premium equals 20400.00 paid.

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

“Juniper Workspace Cloud: Capitalisation table” is a deterministic Novus Examples fixture for Data import, CSV parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 5 rows. 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("cap-table.csv")
print(df.head())
print(df.dtypes)

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