How Docuivo tests its tools
The checks focus on reproducible examples and specific user workflows. Passing those checks is not a guarantee that every input, device or country's document requirements are covered.
Shared document calculations and PDF examples
The automated suite checks line totals, discounts, shipping, tax, payments, remaining balances and overpayments against explicit examples. It compares the six connected PDF examples with the shared document model and renderer, and exercises long text with a 150-item pagination case.
Browser tests follow quote → invoice → received-payment receipt, including confirmation, draft replacement cancellation, local backup, preserved source drafts, actual PDF download events and a simulated export failure. This is a defined workflow test, not exhaustive coverage of every document type and input.
Calculator boundaries
Tests distinguish margin from markup, check the entered-cost basis, preserve negative results and reject nonfinite or overflowing values. Zero revenue produces an undefined margin, zero cost an undefined markup, and zero billable time an undefined hourly rate. Valid break-even results remain zero rather than being treated as errors.
Guides and internal references
Checks cover the guide catalog, worked-table structure, copyable examples, internal destinations and selected independent arithmetic. Server-rendered page tests cover the 32 guide routes, 12 tool routes and supporting pages. Official source links identify the jurisdiction of legal and tax details; automated structure checks do not replace professional advice.
Desktop and mobile browser emulation
The browser suite uses Chromium at desktop and mobile widths and WebKit at a mobile width. It checks readable layouts, horizontal overflow, rendered headings, metadata, copy controls, calculator results and document workflows. These are automated browser configurations, not certification on every physical Android phone or iPhone.
Privacy and measurement limits
Browser tests block external analytics and advertising requests. Custom event payload checks ensure the tested export events do not include the example customer's fields or invoice identifier. A download request is not proof that a file was saved to the user's disk. Account-level analytics, consent and enhanced-measurement settings need their own review and are not certified by these tests.
Production checks after release
A release check requests the live HTML pages, verifies the expected revised guide headings, checks that the existing example PDFs are served and requests the health endpoint. This confirms the expected content is being served; it does not establish search-engine indexing, advertising approval or legal suitability.
See Docuivo Lab for the connected document examples, and the editorial policy for the publishing approach.