Skip to content
Novus Examples

How to use Novus Examples

A practical tour of finding, inspecting, collecting, editing, and creating test files.

Updated Applies to Novus Examples 2026.08

  1. 1

    Browse the library#

    Start from Browse and filter files, visual templates, and live targets by type, category, subcategory, purpose, format, or target. The URL records the active view, so a filtered result can be shared without changing any permanent catalog URL.

  2. 2

    Read the spec sheet#

    Open any file to see its exact properties — dimensions, noise seed, silence timestamps, form fields, encoding, formulas, or container details. You are testing against a documented input, not a mystery file.

  3. 3

    Use the published testing contract#

    Fixture families state the scenario, expected result, and validity role directly on the file page. Use those outcomes with grouped controls for metadata preservation, schema compatibility, calendar/contact import, graph algorithms, and ONNX inference.

  4. 4

    Preview and inspect safely#

    Use the real thumbnail, waveform, poster, table fragment, source excerpt, or model preview before downloading. Text and binary summaries are bounded, and downloadable fixtures are served with an attachment policy so a labelled malformed sample does not execute as a page.

  5. 5

    Download the file#

    Every file page has one primary download action. Files use stable, permanent URLs, so you can link to one from a README or fetch it in CI. Downloads do not open an advertising tab and do not require an account.

  6. 6

    Use pairs for before and after#

    Many files have a 1:1 pair — a clean image and its noisy version, a source document and its scanned twin, or content with and without metadata. Use one as input and the other as the reference you score against.

  7. 7

    Build a local test collection#

    Add files from Browse to the local collection. The selection stays on this device, is capped at 100 files and 200 MiB, and exports as a deterministic ZIP with a manifest and SHA-256 values. No account or upload is involved.

  8. 8

    Choose a creation workspace#

    Open Create to compare six local-first workspaces: text/data, forms, documents, visuals, audio, and video. Each keeps the data model honest rather than pretending a CSV cell, PDF field, document block, and canvas node are interchangeable.

  9. 9

    Edit text and data files#

    Text-based files open in the editor with syntax highlighting, previews, and format-aware exports. Start with a blank buffer or grouped starter. Eligible file pages also provide an Open in editor link; imported text stays in the browser.

  10. 10

    Edit every form contract honestly#

    Form Studio exposes all 243 form fixtures. HTML and PDF use layout definitions; JSON, CSV, TXT, FDF, and XFDF use field-value definitions. Import, edit, export in the original format, and re-import to verify quoting, escaping, newlines, PDF field names, and protected SAMPLE or legal markings. FDF and XFDF keep companion PDF context without inventing a page layout.

  11. 11

    Build and resize a document#

    Document Studio starts with a blank block document or a curated family. Switch templates, choose a page shape, and reflow editable content before exporting DOCX, XLSX, HTML, Markdown, CSV where unambiguous, or print-ready PDF. Dirty-work warnings prevent an accidental template replacement.

  12. 12

    Build and resize a visual#

    Open a validated visual template or the blank canvas. Switch scenes, choose an aspect ratio, and either resize the canvas or scale all unlocked nodes. Locked SAMPLE/legal nodes and safe areas stay protected, and one resize is one undo operation.

  13. 13

    Generate synthetic audio#

    In the audio workspace, choose a bounded tone, sweep, seeded noise, or silence recipe. Generate only after reviewing the estimate, then retain the recipe, source hash, output hash, and reproducibility tier with the downloaded fixture. No microphone or upload exists.

  14. 14

    Generate capability-gated video#

    In the video workspace, choose a short synthetic pattern and a codec/container combination the current browser reports as available. WebCodecs output has content reproducibility, not hardware-independent byte reproducibility. Unsupported legacy formats link to catalog fixtures instead of producing a fake file with the requested extension.

Was this page helpful?

Found an error? Send a correction.