Novus Examples
Test forms with HTML and AcroForm fixtures
The Forms category holds 94 fixtures — live HTML forms and AcroForm PDFs with known field inventories — for testing form fillers, validators, scrapers, and PDF editors.
Forms are where automated tools most often fail quietly. A field is missed, a checkbox is read as text, a date is parsed in the wrong locale — and nothing errors, so nothing gets noticed until someone downstream is confused by the data.
The Forms category holds 94 fixtures for exactly this: live HTML forms and AcroForm PDFs whose field inventories are stated up front, so a missed field is a discrepancy rather than a guess.
Contents
Two ways to finish
HTML forms
Live pages for fillers, scrapers, and validators.
AcroForm PDFs
Real PDF form fields for editors and extractors.
- 1
1. Start from the stated field inventory
Each fixture ships with its field inventory on the spec sheet: how many fields, of what types, with what names. That is the expected answer, which means testing a form tool becomes a diff rather than an inspection.
Without a stated inventory you are checking whether a tool found what you think is there, which is a much weaker test than checking whether it found what is definitely there.
- Field count, types, and names are stated, not inferred.
- Testing becomes a diff against a known answer.
- 94 fixtures spanning HTML and AcroForm PDF.
- 2
2. Exercise the awkward field types
Text inputs are easy. The fixtures that matter carry checkboxes, radio groups, selects, date inputs, and multi-page forms, because those are where detection and extraction go wrong.
Radio groups are a particularly good stress test: a tool that treats each option as an independent field rather than as one field with several options will produce plausible-looking output that is structurally wrong.
- 3
3. Use the AcroForm PDFs for editors and extractors
AcroForm PDFs carry real, machine-readable form fields rather than lines drawn on a page. They are the right fixture for testing whether a PDF editor detects existing fields instead of overlaying new ones on top of them.
They pair naturally with Novus PDF Studio at pdf.novusstreamsolutions.com, whose AI field scan is designed to detect fillable areas and skip things like table headers and amount cells that are not fields at all.
- 4
4. Check false positives, not just misses
Two failure modes matter and only one gets tested. A tool that misses a field is obviously broken; a tool that invents fields where none exist is subtly broken, and it produces forms that look filled and are not.
Because the inventory is exact, both directions are measurable. Count what was found against what exists and read the difference in both signs.
- 5
5. Test the live forms with automation
The live HTML forms work as browser-automation targets. Fill them, submit them, and verify your tooling handled validation states, required fields, and error rendering correctly.
They sit alongside the twelve live targets at /targets, which cover the surrounding page behaviours — consent banners, slow loads, nested iframes — that a form flow usually has to survive as well.
- 6
6. Keep a small form suite in regression
Pick a handful that span the difficulty range: one simple text form, one with a radio group and checkboxes, one multi-page AcroForm PDF. Because the fixtures are generated deterministically, they stay stable and a newly failing test means your code changed.
Three well-chosen form fixtures catch more regressions than a large pile of near-identical ones.
A stated inventory turns inspection into a diff
Every form fixture states its field count, types, and names, so testing is a comparison against a known answer. Exercise radio groups, selects, dates, and multi-page forms rather than plain text inputs, and measure false positives as carefully as misses — an invented field produces a form that looks filled and is not.
Frequently asked questions
Quick answers to common questions about this topic.
How many form fixtures are there?
94, spanning live HTML forms and AcroForm PDFs. Each ships with its field inventory — count, types, and names — on the spec sheet.
What is an AcroForm PDF?
A PDF carrying real, machine-readable form fields rather than lines drawn on the page. It is the right fixture for testing whether an editor detects existing fields instead of overlaying new ones.
Why test for false positives?
Because a tool that invents fields produces forms that look filled and are not — a subtler and more damaging failure than simply missing one. The exact inventory lets you measure both directions.
Which field types break tools most often?
Radio groups, selects, date inputs, and multi-page layouts. Radio groups in particular expose tools that treat each option as an independent field rather than one field with several options.