Skip to content
Testaroo
md6.1 KB

Juniper Workspace Cloud: corporate document set README

Document set README for Juniper Workspace Cloud. 30 files, 1 of them intentionally invalid, with the reconciliation identities, the declared parameters and the measured size of each deliberate defect named in full.

Preview, first 50 linesmd
# Juniper Workspace Cloud: incorporation, share register, board minutes and annual return documents

The statutory record of a small private company: its constitution and certificate of incorporation, the share certificates in issue, the registers of members, directors, charges and persons with significant control, the minutes and resolutions that moved the share capital, and the annual return that confirms all of it in three formats.

All parties, amounts and identifiers are fictional. Fixed snapshot: 2026-09-08. Records are derived from the shared operating model `saas-subscriptions`, so identifiers join across this set, across the other commercial document sets, and across every fixture built on the same model.

## Reconciliation identities this set asserts

- Member holdings sum to 600,000 shares, the issued total every file states, and the four percentages sum to exactly 100.0000.
- Amounts paid sum to 20,400.00 USD, which is 6,000.00 of called-up capital plus 14,400.00 of share premium.
- On the priced allotment, 60,000 shares at 0.25 is 15,000.00 USD, and that equals 600.00 nominal plus 14,400.00 premium.
- The 18,000 share transfer leaves the issued total and the total paid unchanged and only moves 180.00 USD of paid-up capital between two members.
- The members written resolution passed on 462,000 of the 540,000 shares in issue at circulation, 85.5556 percent, not on today 600,000.
- The annual return reproduces every register: 4 members, 4 officers, 2 controllers and 2 charges, in PDF, JSON and XML.
- The September board minutes quote the saas-subscriptions ledger unchanged: 668.00 invoiced, 649.00 received, 19.00 outstanding and 235.00 USD of active recurring revenue.

## Parameters this set introduces

These are properties of the document class, not of the operating model. They are declared once and every file in the set agrees with them.

- The company itself: Juniper Workspace Cloud Limited, number FC-00847213, incorporated 2024-02-14 in the fictional Sample City companies registry.
- Share capital: 1,000,000 authorised ordinary shares of 0.01 USD, and the two allotments and one transfer that produced the 600,000 in issue.
- The officers, the persons with significant control and the two charges. None of them exists in the operating model, which carries accounts, invoices and usage only.
- The activity code SC-6201 belongs to a fictional registry classification and is not a real industrial classification code.

## Files

| File | Format | Validity | What it is |
| --- | --- | --- | --- |
| `articles-of-incorporation.pdf` | pdf | valid | Articles of incorporation (PDF) |
| `articles-of-incorporation.docx` | docx | valid | Articles of incorporation (DOCX) |
| `certificate-of-incorporation.pdf` | pdf | valid | Certificate of incorporation |
| `share-certificate-SC-001.pdf` | pdf | valid | Share certificate SC-001 |
| `share-certificate-SC-004.pdf` | pdf | valid | Share certificate SC-004 (PDF) |
| `share-certificate-SC-004.docx` | docx | valid | Share certificate SC-004 (DOCX) |
| `share-certificate-SC-005.pdf` | pdf | valid | Share certificate SC-005 |
| `share-certificate-SC-006.pdf` | pdf | valid | Share certificate SC-006 |
| `register-of-members.csv` | csv | valid | Register of members |
| `register-of-members-share-total-mismatch.csv` | csv | invalid | Register of members whose holdings do not add up to the issued capital |
| `register-of-members.json` | json | valid | Register of members JSON |
| `cap-table.csv` | csv | valid | Capitalisation table |
| `register-of-members.xlsx` | xlsx | valid | Register of members workbook |
| `share-allotment-return.csv` | csv | valid | Share allotment return |
| `shareholding-history.csv` | csv | valid | Shareholding movement history |
| `register-of-directors.csv` | csv | valid | Register of directors and secretaries |
| `psc-register.csv` | csv | valid | Register of persons with significant control |
| `register-of-charges.csv` | csv | valid | Register of charges |
| `statutory-registers-index.csv` | csv | valid | Statutory registers index |
| `board-minutes-2026-05-18.pdf` | pdf | valid | Board minutes, allotment meeting (PDF) |
| `board-minutes-2026-05-18.docx` | docx | valid | Board minutes, allotment meeting (DOCX) |
… 73 lines total: download for the full file.

Specifications

Document Set
corporate
Industry
software
Source Kit
saas-subscriptions
Entity
Juniper Workspace Cloud
Synthetic
true
As Of
2026-09-08
Documented Files
30
Documented Defects
1

Testing contract

Reference control
Scenario
Read the README before using the set, then check that every filename it lists exists in the same directory and that the defect list matches the files marked invalid.
Expected result
The file table lists 30 entries including this README, and the deliberate-defect section names 1 file(s) with the measured size of each discrepancy.

What is a .md file?

Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.

How to use this file

Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.

How to use this file for testing

“Juniper Workspace Cloud: corporate document set README” is a deterministic Testaroo fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: MD · 6,228 bytes. 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.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import markdown  # pip install markdown

html = markdown.markdown(open("README.md").read())
print(html[:200])

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