The short answer
Test pages answer different questions. A page printed from the printer's own controls tests its basic engine; an operating-system test exercises the computer-to-printer path.
Where this applies
Use only test functions supported by the model. The operating-system test-page option may be located differently across Windows releases and macOS; a simple text document is a useful cross-platform comparison.
Identify the right device and prepare
Check consumables, paper and panel errors first. Record whether the issue is no page, blank page, wrong color, wrong layout or missing scan function; each points to a different part of the workflow.
Work through the checks in order
A clean internal page but blank pages from one PDF points away from basic paper feed and toward the document, settings or rendering path. Blank internal pages suggest consumables or hardware before a PC driver.
- If the device offers a built-in information or configuration page, print it using its official manual and note whether the output is clean.
- Print the OS test page if available, or a one-line document from a basic editor; watch the queue and the printer.
- Print the original troublesome document from its application and compare it to the simple output.
- Record which test first fails, along with exact error text and whether the job stays queued, vanishes or produces incorrect pages.
Expected result and next branch
The first failing stage gives a useful next action: investigate hardware or consumables for a failed internal page; connection or queue for a failed computer test; application settings for a document-only failure.
Not every printer offers a self-test accessible without its manual. If no such feature exists, compare two simple documents or ask official support for a model-specific diagnostic.
Safety and limits
Keep sensitive documents out of shared test queues. Stop printing if the device reports overheating, repeated jams or a mechanical fault.